On Fri, Aug 26, 2011 at 09:08:02AM +0300, Sasha Levin wrote: > You're thinking about trying to expose all interfaces during boot and > seeing which ones the kernel bites? No, that's a bad idea. A current guest would register that as two disks. It might even try to write to them independently. You need an IDE device which can be promoted to virtio at the request of the guest (so you know the guest understands this type of device). > Another thing that comes to mind is that we could start this project > with a script that given a kernel, it would find the optimal hardware > configuration for it (and the matching QEMU command line). It would be better if the guest could communicate what it needs. But no current guest works that way. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
