Bug 2408

Summary:	atom-pc images should work on Fedora virt-manager out of the box
Product:	[Build System, Metadata & Runtime] Meta-yocto	Reporter:	Ross Burton <ross.burton>
Component:	meta-yocto	Assignee:	Dexuan Cui <dexuan.cui>
Status:	VERIFIED WONTFIX	QA Contact:
Severity:	normal
Priority:	Medium	CC:	dvhart, laurentiu.serban, poky.bs.watcher, poky.watcher, sgw, shane.wang
Version:	1.1.1
Target Milestone:	1.3 M3
Hardware:	x86
OS:	Multiple
Whiteboard:	(P2)
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Ross Burton 2012-05-03 12:33:16 UTC

My build machine is running Fedora 16 so it makes sense to use the existing virtualisation system (kvm, virt-manager, and gnome-boxes in the F17) to develop when the final target is an atom-pc netbook or similar.

For some reason when the .hddimg the boot hangs at "Waiting for removable media...".  When using the .iso the image boots but by default virt-manager is configuring the virtual network device to use virtio which isn't supported in the atom-pc kernel.  This can be worked around by changing the machine type to "generic 2.6 kernel" which doesn't use virtio, but this isn't the default and this reduces performance.

Comment 1 Ross Burton 2012-05-06 09:31:44 UTC

I guess a better solution would be a kvm machine type, with all the virtio drivers and relevant tuning.

Comment 2 Ross Burton 2012-05-06 09:32:52 UTC

Oh, that comment comes from the realisation that atom-pc is missing many drivers.   virtio networking for example, and the majority of the sound drivers.

Comment 3 Darren Hart 2012-05-08 15:06:01 UTC

Have you considered building for the qemux86 machine when you want to run under emulation? We have added pcnet32 as it was required for vmware (iirc) and was also supported by qemux86. If you have a missing feature that qemux86 does support, we should be able to add it to that machine, and it would likely be more appropriate.

This would allow us to keep atom-pc more minimal.

Would this work for you?

Comment 4 Darren Hart 2012-06-05 20:26:23 UTC

The waiting for removable media part will have something to do with udev and how devices appear when run under virt-manager. This might be something to investigate.

As for virt-io, the atom-pc machine is intended to be run on virtual hardware, and is optimized (minimized) to do so. Not running in emulation is not intentional, but also not surprising. Unlike a generic distribution, each image we build with Yocto is customized for it's specific target. As such, the solution to this problem is to create a linux-yocto bbappend that adds the config options you want in a config fragment "virtio.cfg" for example, and build that.

I plan to mark this as RESOLVED-WILL_NOT_FIX, and suggest the issue with Waiting for removable media with virt-manager be opened as a separate bug. Will wait to here from Ross before doing so.

Comment 5 Ross Burton 2012-06-06 12:47:55 UTC

Agreed, a "kvm" machine with virtio drivers and guest tools for tighter integration is the best way forward.  I'll open another bug for the hang.

Comment 6 Ross Burton 2012-06-06 12:51:55 UTC

Filed #2549 (waiting...) and #2550 (kvm machine).

Comment 7 Laurentiu Serban 2012-08-17 09:58:28 UTC

Setting to verified after Ross latest comment