Re: Guest kernel device compatability auto-detection

[Anthony Liguori <anthony@codemonkey.ws>]

On 08/25/2011 12:21 AM, Sasha Levin wrote:
> Hi,
>
> Currently when we run the guest we treat it as a black box, we're not
> quite sure what it's going to start and whether it supports the same
> features we expect it to support when running it from the host.
>
> This forces us to start the guest with the safest defaults possible, for
> example: '-drive file=my_image.qcow2' will be started with slow IDE
> emulation even though the guest is capable of virtio.
>
> I'm currently working on a method to try and detect whether the guest
> kernel has specific configurations enabled and either warn the user if
> we know the kernel is not going to properly work or use better defaults
> if we know some advanced features are going to work.
>
> How am I planning to do it? First, we'll try finding which kernel the
> guest is going to boot (easy when user does '-kernel', less easy when
> the user boots an image). For simplicity sake I'll stick with the
> '-kernel' option for now.

Is the problem you're trying to solve determine whether the guest kernel 
is going to work well under kvm tool or trying to choose the right 
hardware profile to expose to the guest?

If it's the former, I think the path you're heading down is the most 
likely to succeed (trying to guess based on what you can infer about the 
kernel).

If it's the later, there's some interesting possibilities we never fully 
explored in QEMU.

One would be exposing a well supported device (like IDE emulation) and 
having a magic mode that allowed you to basically promote the device 
from IDE emulation to virtio-blk.  Likewise, you could do something like 
that to promote from the e1000 to virtio-net.

It might require some special support in the guest kernel and would 
likely be impossible to do in Windows, but if you primarily care about 
Linux guests, it ought to be possible.

Regards,

Anthony Liguori