qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
	ajax@redhat.com, Paul Brook <paul@codesourcery.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to	PCI_CLASS_SERIAL_OTHER
Date: Fri, 29 May 2009 00:45:02 +0300	[thread overview]
Message-ID: <4A1F05DE.6060806@redhat.com> (raw)
In-Reply-To: <4A1E91AF.9050907@us.ibm.com>

Anthony Liguori wrote:
> Paul Brook wrote:
>   
>>>>>   - the device model cannot change or the guest OS will get confused
>>>>>         
>>>>>           
>>>> IMHO think the only sane response is "don't do that". Trying to support
>>>> migration between different qemu versions just isn't worth the pain.
>>>>       
>>>>         
>>> It is very worth the pain.  I consider it a core requirement.
>>>     
>>>       
>> We disagree then. You're effectively requiring bug-compatibility.
>>   
>>     
>
> You can take it to an extreme and require bug-compatibility, but I don't
> think that's necessary.  I think there's room for being reasonable.
>
>   
>> This may be reasonable for a stable branch, but is not something I have any 
>> interest in across different release cycles. IMHO major VM upgrades should be 
>> considered the same as real hardware or firmware upgrades.
>>   
>>     
>
> I think major VM upgrades is something that can be considered
> occasionally but every 6 months would be pretty painful to most users. 
> I think we ought to make a best effort to maintain compatibility with
> older versions as long as it's reasonable.
>
>   
Supporting live migration between different versions of qemu is a 
stretch goal. In the past
2 month we fixed about 10 basic live migration issues and mainline keeps 
breaking ;(

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 -
http://lists.gnu.org/archive/html/qemu-devel/2009-05/msg01189.html
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.

Thanks,
Dor

> Regards,
>
> Anthony Liguori
>
>   
>> Paul
>>   
>>     
>
>
>
>   

  reply	other threads:[~2009-05-28 21:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 17:14 [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER Mark McLoughlin
2009-05-24  9:11 ` Avi Kivity
2009-05-27 14:21 ` Anthony Liguori
2009-05-27 17:42   ` Mark McLoughlin
2009-05-27 22:37     ` Anthony Liguori
2009-05-28  9:33       ` Mark McLoughlin
2009-05-28  9:44         ` Anthony Liguori
2009-05-28 12:53     ` Paul Brook
2009-05-28 12:56       ` Anthony Liguori
2009-05-28 13:22         ` Paul Brook
2009-05-28 13:29           ` Anthony Liguori
2009-05-28 21:45             ` Dor Laor [this message]
2009-05-29  9:43               ` Mark McLoughlin
2009-05-29  9:50                 ` Anthony Liguori
2009-05-31 14:32                   ` Avi Kivity
2009-05-29  9:55                 ` Anthony Liguori
2009-05-29 10:09                 ` Mark McLoughlin
2009-05-31 14:47                   ` Dor Laor
2009-06-02  8:49                     ` Mark McLoughlin
2009-06-02 13:08                       ` Dor Laor
2009-06-02 13:39                         ` Mark McLoughlin
2009-05-31 14:35                 ` Dor Laor
2009-06-02  8:49                   ` Mark McLoughlin
2009-05-28 13:04       ` Daniel P. Berrange
2009-05-28 13:19         ` Anthony Liguori
2009-05-31 18:48           ` Jamie Lokier
2009-05-28 13:20         ` Paul Brook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A1F05DE.6060806@redhat.com \
    --to=dlaor@redhat.com \
    --cc=ajax@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=markmc@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).