Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?

Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?

[Avi Kivity]

On 11/13/2011 02:41 PM, Alon Levy wrote:
> On Sun, Nov 13, 2011 at 12:29:01PM +0200, Avi Kivity wrote:
> > On 11/12/2011 07:19 PM, Alon Levy wrote:
> > > On Sat, Nov 12, 2011 at 09:22:27AM -0500, Tom Horsley wrote:
> > > > I just submitted this bug:
> > > > 
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=753437
> > > > 
> > > > Apparently Windows XP thinks the video hardware has changed
> > > > on fedora 16 host (I was using qxl and spice on fedora 15 host).
> > > > 
> > > > If this is expected rather than a bug, which drivers do I
> > > > install to made XP happy when hosted on fedora 16?
> > > > 
> > > > The Windows XP machine on fedora 15 currently has the
> > > > Red Hat QXL GPU version 1.4.1.0 (9/29/2010) video
> > > > driver.
> > >
> > > That's because it has. We changed the revision from 2 to 3, I need to
> > > fix that I guess - make sure it doesn't change if you use -M something.
> > >
> > 
> > This needs to be done real quick.
>
> So I want all machines < pc-1.0 to use rev=2 by default, and pc-1.0 to
> have rev=3 by default?

Yes.  But what about all guests already created with 0.15?  If it's just
Fedora, then there's a small number of them hopefully.  But we can't be
sure of it.

-- 
error compiling committee.c: too many arguments to function

Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?

[Alon Levy]

On Sun, Nov 13, 2011 at 02:48:32PM +0200, Avi Kivity wrote:
> On 11/13/2011 02:41 PM, Alon Levy wrote:
> > On Sun, Nov 13, 2011 at 12:29:01PM +0200, Avi Kivity wrote:
> > > On 11/12/2011 07:19 PM, Alon Levy wrote:
> > > > On Sat, Nov 12, 2011 at 09:22:27AM -0500, Tom Horsley wrote:
> > > > > I just submitted this bug:
> > > > > 
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=753437
> > > > > 
> > > > > Apparently Windows XP thinks the video hardware has changed
> > > > > on fedora 16 host (I was using qxl and spice on fedora 15 host).
> > > > > 
> > > > > If this is expected rather than a bug, which drivers do I
> > > > > install to made XP happy when hosted on fedora 16?
> > > > > 
> > > > > The Windows XP machine on fedora 15 currently has the
> > > > > Red Hat QXL GPU version 1.4.1.0 (9/29/2010) video
> > > > > driver.
> > > >
> > > > That's because it has. We changed the revision from 2 to 3, I need to
> > > > fix that I guess - make sure it doesn't change if you use -M something.
> > > >
> > > 
> > > This needs to be done real quick.
> >
> > So I want all machines < pc-1.0 to use rev=2 by default, and pc-1.0 to
> > have rev=3 by default?
> 
> Yes.  But what about all guests already created with 0.15?  If it's just
> Fedora, then there's a small number of them hopefully.  But we can't be
> sure of it.

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.

> 
> -- 
> error compiling committee.c: too many arguments to function
> 

Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?

[Avi Kivity]

On 11/13/2011 04:00 PM, Alon Levy wrote:
> On Sun, Nov 13, 2011 at 02:48:32PM +0200, Avi Kivity wrote:
> > On 11/13/2011 02:41 PM, Alon Levy wrote:
> > > On Sun, Nov 13, 2011 at 12:29:01PM +0200, Avi Kivity wrote:
> > > > On 11/12/2011 07:19 PM, Alon Levy wrote:
> > > > > On Sat, Nov 12, 2011 at 09:22:27AM -0500, Tom Horsley wrote:
> > > > > > I just submitted this bug:
> > > > > > 
> > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=753437
> > > > > > 
> > > > > > Apparently Windows XP thinks the video hardware has changed
> > > > > > on fedora 16 host (I was using qxl and spice on fedora 15 host).
> > > > > > 
> > > > > > If this is expected rather than a bug, which drivers do I
> > > > > > install to made XP happy when hosted on fedora 16?
> > > > > > 
> > > > > > The Windows XP machine on fedora 15 currently has the
> > > > > > Red Hat QXL GPU version 1.4.1.0 (9/29/2010) video
> > > > > > driver.
> > > > >
> > > > > That's because it has. We changed the revision from 2 to 3, I need to
> > > > > fix that I guess - make sure it doesn't change if you use -M something.
> > > > >
> > > > 
> > > > This needs to be done real quick.
> > >
> > > So I want all machines < pc-1.0 to use rev=2 by default, and pc-1.0 to
> > > have rev=3 by default?
> > 
> > Yes.  But what about all guests already created with 0.15?  If it's just
> > Fedora, then there's a small number of them hopefully.  But we can't be
> > sure of it.
>
> 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.

-- 
error compiling committee.c: too many arguments to function

Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?

[Alon Levy]

On Sun, Nov 13, 2011 at 04:03:56PM +0200, Avi Kivity wrote:
> On 11/13/2011 04:00 PM, Alon Levy wrote:
> > On Sun, Nov 13, 2011 at 02:48:32PM +0200, Avi Kivity wrote:
> > > On 11/13/2011 02:41 PM, Alon Levy wrote:
> > > > On Sun, Nov 13, 2011 at 12:29:01PM +0200, Avi Kivity wrote:
> > > > > On 11/12/2011 07:19 PM, Alon Levy wrote:
> > > > > > On Sat, Nov 12, 2011 at 09:22:27AM -0500, Tom Horsley wrote:
> > > > > > > I just submitted this bug:
> > > > > > > 
> > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=753437
> > > > > > > 
> > > > > > > Apparently Windows XP thinks the video hardware has changed
> > > > > > > on fedora 16 host (I was using qxl and spice on fedora 15 host).
> > > > > > > 
> > > > > > > If this is expected rather than a bug, which drivers do I
> > > > > > > install to made XP happy when hosted on fedora 16?
> > > > > > > 
> > > > > > > The Windows XP machine on fedora 15 currently has the
> > > > > > > Red Hat QXL GPU version 1.4.1.0 (9/29/2010) video
> > > > > > > driver.
> > > > > >
> > > > > > That's because it has. We changed the revision from 2 to 3, I need to
> > > > > > fix that I guess - make sure it doesn't change if you use -M something.
> > > > > >
> > > > > 
> > > > > This needs to be done real quick.
> > > >
> > > > So I want all machines < pc-1.0 to use rev=2 by default, and pc-1.0 to
> > > > have rev=3 by default?
> > > 
> > > Yes.  But what about all guests already created with 0.15?  If it's just
> > > Fedora, then there's a small number of them hopefully.  But we can't be
> > > sure of it.
> >
> > 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?

> -- 
> error compiling committee.c: too many arguments to function
> 
> _______________________________________________
> virt mailing list
> virt@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/virt

Re: [Qemu-devel] [fedora-virt] Windows KVM thinks hardware changed when ported to f16?

[Avi Kivity]

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