Re: [Xen-devel] Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

I've got the same issue with CentOS 5.2 PV DomU (same /dev/sdb5)
under Suse's 2.6.27 xen-ified kernel & Xen Unstable ( the most recent).
I believe Xen is broken in some way. It's not about the kernel.

Boris.

--- On Wed, 3/11/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Date: Wednesday, March 11, 2009, 3:26 AM

disk= [ phy:/dev/sdb5] seems not to be released after PV DomU shutdown.
Hence , second attempt to load DomU gets paused waiting for particular
device. When i reboot xen host, DomU can be loaded again.

--- On Tue, 3/10/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it
To: bderzhavets@xxxxxxxxx
Cc: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, March 10, 2009, 8:29 PM

Boris Derzhavets wrote:
> 
>   Seems like new kernel brought up back some old issues with ubuntu 8.10
> devices.
 It never happened before patching 2.6.29-rc7 kernel on C2D boxes
with the same ubuntu 8.10 server release and 2.6.29-rc5.
>   In particular, CentOS 5.2 PV DomU's xen-hotplug.log looks like:-
> 
> xenstore-read: couldn't read path /local/domain/2/vm
> xenstore-read: couldn't read path /local/domain/9/vm
> xenstore-read: couldn't read path /local/domain/3/vm
> xenstore-read: couldn't read path /local/domain/4/vm
>   Either xen-tools (or whatever else in xen unstable) requires correlation
> with patched kernel.
> 

Ah, I noticed that too, but I don't see any obvious changes which might
have caused this.  Time to pull out "git bisect" I think.

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

second boot up
under Novell's 2.6.27 & Xen Unstable ( the most recent).
I believe it's not about kernel, it's about Xen Unstable.
It's broken in some way.

Boris.


--- On Wed, 3/11/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Date: Wednesday, March 11, 2009, 3:26 AM

disk= [ phy:/dev/sdb5] seems not to be released after PV DomU shutdown.
Hence , second attempt to load DomU gets paused waiting for particular
device. When i reboot xen host, DomU can be loaded again.

--- On Tue, 3/10/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it
To: bderzhavets@xxxxxxxxx
Cc: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, March 10, 2009, 8:29 PM

Boris Derzhavets wrote:
> 
>   Seems like new kernel brought up back some old issues with ubuntu 8.10
> devices.
 It never happened before patching 2.6.29-rc7 kernel on C2D boxes
with the same ubuntu 8.10 server release and 2.6.29-rc5.
>   In particular, CentOS 5.2 PV DomU's xen-hotplug.log looks like:-
> 
> xenstore-read: couldn't read path /local/domain/2/vm
> xenstore-read: couldn't read path /local/domain/9/vm
> xenstore-read: couldn't read path /local/domain/3/vm
> xenstore-read: couldn't read path /local/domain/4/vm
>   Either xen-tools (or whatever else in xen unstable) requires correlation
> with patched kernel.
> 

Ah, I noticed that too, but I don't see any obvious changes which might
have caused this.  Time to pull out "git bisect" I think.

  
 J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel