From: Avi Kivity <avi@redhat.com>
To: Tom Horsley <horsley1953@gmail.com>,
Fedora Virt <virt@lists.fedoraproject.org>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?
Date: Sun, 13 Nov 2011 16:33:57 +0200 [thread overview]
Message-ID: <4EBFD555.6020208@redhat.com> (raw)
In-Reply-To: <20111113141704.GH3624@garlic.redhat.com>
On 11/13/2011 04:17 PM, Alon Levy wrote:
> > > Going after each distribution that packages qemu? No way to do this, I
> > > can just hope any packager who encounters this problem comes to
> > > spice-devel/qemu-devel.
> > >
> > >
> >
> > I'm talking about guests. Images created with 0.15 know that rev=3,
> > with 1.0 (or 0.15.next) they'll be back to rev=2.
> >
>
> Ok, my mistake. So yes, there will now be both pc-0.14 with rev 3 and
> 2. For migrations there is no problem since the revision is migrated
> (since it could be set from the command line anyway). Otherwise, doing
> a shutdown, upgrading qemu, and starting the vm again - yes. Other then
> "this should never have happened" any suggestions?
>
No. Clever ideas welcome. Also about "this will never happen again".
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-11-13 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111112092227.54142a7a@zooty>
[not found] ` <20111112171935.GU16972@garlic.redhat.com>
[not found] ` <4EBF9BED.1090308@redhat.com>
[not found] ` <20111113124133.GF3624@garlic.redhat.com>
2011-11-13 12:48 ` [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16? Avi Kivity
2011-11-13 14:00 ` Alon Levy
2011-11-13 14:03 ` Avi Kivity
2011-11-13 14:17 ` Alon Levy
2011-11-13 14:33 ` Avi Kivity [this message]
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=4EBFD555.6020208@redhat.com \
--to=avi@redhat.com \
--cc=horsley1953@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virt@lists.fedoraproject.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).