[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER

From: Dor Laor
Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER
Date: Sun, 31 May 2009 17:35:58 +0300
User-agent: Thunderbird (X11/20090105)

Mark McLoughlin wrote:
On Fri, 2009-05-29 at 00:45 +0300, Dor Laor wrote:

Nevertheless, as Anthony states, guest ABI should be rock stable.
We should have mechanism (machine conf format++) that will enable us
to configure pci addresses, cpuid entries, memory layout, device existence (hpet, virtio-console,..), etc.

Anyhow, I did sent a patch to allow virtio block to parametrized class value -
There wasn't a perfect match with finding the right interface to change it, happy to hear
other alternatives if you're not happy with it.

As I said, it's pointless to add something like this if, realistically,
it will never be used.

So, taking the example of '-drive class=foo' ... a user who runs qemu
directly would have to know that when she updates from qemu-0.10.x to
qemu-0.11.x, she needs to use '-drive class=384' for ever more. I find
it hard to believe anyone will ever do that.
'She' is not a user, she is a developer.
Users use management tools like libvirt below.
Running qemu directly is complicated and error prone for
manual/human users.
I just wanted to stress this out, more feedback in the next email.
Perhaps management tools can hide this complexity? In order to do this
in libvirt, we'd need to do the following:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]