VMX status report. Xen:25334 & Dom0:568b445...

VMX status report. Xen:25334 & Dom0:568b445...

[Wu, GabrielX]

Hi all,

This is the test report of xen-unstable tree. 
There are two issues found and one issue got fixed.

Version Info:
=================================================================
xen-changeset:   25334:f8279258e3c9
Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...) 
=================================================================

New issues(2)
==============
1. long stop during the guest boot process with qcow image
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
2. vcpu-set doesn't take effect on guest
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822

Fixed issue(1)
==============
1. when detaching a VF from hvm guest, "xl dmesg" will show some warning information
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809

Old issues(9)
==============
1. [ACPI] System cann't resume after do suspend
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
2. [XL]"xl vcpu-set" causes dom0 crash or panic
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
3. [VT-D]fail to detach NIC from guest  
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
5. [VT-D] device reset fail when create/destroy guest
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
6. RHEL6.2/6.1 guest runs quite slow
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811
7. after detaching a VF from a guest, shutdown the guest is very slow
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
8. cpu weight out of range error when create hvm domU
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818
9. Poor performance when do guest save/restore and migration with linux 3.1 dom0
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1784

Thanks,
Wu Ronghui(Gabriel)

Re: VMX status report. Xen:25334 & Dom0:568b445...

[Konrad Rzeszutek Wilk]

On Mon, May 21, 2012 at 03:05:28AM +0000, Wu, GabrielX wrote:
> Hi all,
> 
> This is the test report of xen-unstable tree. 
> There are two issues found and one issue got fixed.
> 
> Version Info:
> =================================================================
> xen-changeset:   25334:f8279258e3c9
> Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...) 
> =================================================================
> 
> New issues(2)
> ==============
> 1. long stop during the guest boot process with qcow image
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> 2. vcpu-set doesn't take effect on guest
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822

Does it work if you (in the guest) do
echo 1 > /sys/../cpu9/online ?

There is a race in the generic hotplug code.

Re: VMX status report. Xen:25334 & Dom0:568b445...

[Ren, Yongjie]

> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Monday, May 21, 2012 10:22 PM
> To: Wu, GabrielX
> Cc: 'xen-devel@lists.xen.org'; Ren, Yongjie; Liu, SongtaoX; Zhou, Chao
> Subject: Re: [Xen-devel] VMX status report. Xen:25334 & Dom0:568b445...
> 
> On Mon, May 21, 2012 at 03:05:28AM +0000, Wu, GabrielX wrote:
> > Hi all,
> >
> > This is the test report of xen-unstable tree.
> > There are two issues found and one issue got fixed.
> >
> > Version Info:
> >
> ============================================================
> =====
> > xen-changeset:   25334:f8279258e3c9
> > Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...)
> >
> ============================================================
> =====
> >
> > New issues(2)
> > ==============
> > 1. long stop during the guest boot process with qcow image
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> > 2. vcpu-set doesn't take effect on guest
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> 
> Does it work if you (in the guest) do
> echo 1 > /sys/../cpu9/online ?
> 
The problem is there's no hot-add vCPU in /sys/devices/system/cpu directory.
e.g. I start a guest with 2 vCPU, then I run command 'xl vcpu-set $domID 4'. 
    There are only 2 CPUs(cpu0 and cpu1) listed in /sys/devices/system/cpu directory.

> There is a race in the generic hotplug code.

Re: VMX status report. Xen:25334 & Dom0:568b445...

[Ian Campbell]

On Tue, 2012-05-22 at 08:19 +0100, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Monday, May 21, 2012 10:22 PM
> > To: Wu, GabrielX
> > Cc: 'xen-devel@lists.xen.org'; Ren, Yongjie; Liu, SongtaoX; Zhou, Chao
> > Subject: Re: [Xen-devel] VMX status report. Xen:25334 & Dom0:568b445...
> > 
> > On Mon, May 21, 2012 at 03:05:28AM +0000, Wu, GabrielX wrote:
> > > Hi all,
> > >
> > > This is the test report of xen-unstable tree.
> > > There are two issues found and one issue got fixed.
> > >
> > > Version Info:
> > >
> > ============================================================
> > =====
> > > xen-changeset:   25334:f8279258e3c9
> > > Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...)
> > >
> > ============================================================
> > =====
> > >
> > > New issues(2)
> > > ==============
> > > 1. long stop during the guest boot process with qcow image
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> > > 2. vcpu-set doesn't take effect on guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > 
> > Does it work if you (in the guest) do
> > echo 1 > /sys/../cpu9/online ?
> > 
> The problem is there's no hot-add vCPU in /sys/devices/system/cpu directory.
> e.g. I start a guest with 2 vCPU,

Do you mean with maxvcpu=4 vcpus=2 in your config?

>  then I run command 'xl vcpu-set $domID 4'. 

>     There are only 2 CPUs(cpu0 and cpu1) listed in /sys/devices/system/cpu directory.

The bugzilla says "But it'll effect to dom0.", does this mean that
	xl vcpu-set domU 4
will actually set dom0 to 12 vcpus? Or does it just mean that
	xl vcpu-set 0 4
works where
	xl vcpu-set domU 4
does not?

There's quite a bit of potentially useful info missing from the bug
report, like guest config details, xenstore content etc,
http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has a list of
various log files which are often useful to help solve bugs, please do
consider including those which seem relevant on future bug reports.

Ian.

> 
> > There is a race in the generic hotplug code.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: VMX status report. Xen:25334 & Dom0:568b445...

[Ren, Yongjie]

> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> Sent: Tuesday, May 22, 2012 4:32 PM
> To: Ren, Yongjie
> Cc: Konrad Rzeszutek Wilk; Wu, GabrielX; Liu, SongtaoX; Zhou, Chao;
> 'xen-devel@lists.xen.org'
> Subject: Re: [Xen-devel] VMX status report. Xen:25334 & Dom0:568b445...
> 
> On Tue, 2012-05-22 at 08:19 +0100, Ren, Yongjie wrote:
> > > -----Original Message-----
> > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > Sent: Monday, May 21, 2012 10:22 PM
> > > To: Wu, GabrielX
> > > Cc: 'xen-devel@lists.xen.org'; Ren, Yongjie; Liu, SongtaoX; Zhou, Chao
> > > Subject: Re: [Xen-devel] VMX status report. Xen:25334 &
> Dom0:568b445...
> > >
> > > On Mon, May 21, 2012 at 03:05:28AM +0000, Wu, GabrielX wrote:
> > > > Hi all,
> > > >
> > > > This is the test report of xen-unstable tree.
> > > > There are two issues found and one issue got fixed.
> > > >
> > > > Version Info:
> > > >
> > >
> ============================================================
> > > =====
> > > > xen-changeset:   25334:f8279258e3c9
> > > > Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...)
> > > >
> > >
> ============================================================
> > > =====
> > > >
> > > > New issues(2)
> > > > ==============
> > > > 1. long stop during the guest boot process with qcow image
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> > > > 2. vcpu-set doesn't take effect on guest
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > >
> > > Does it work if you (in the guest) do
> > > echo 1 > /sys/../cpu9/online ?
> > >
> > The problem is there's no hot-add vCPU in /sys/devices/system/cpu
> directory.
> > e.g. I start a guest with 2 vCPU,
> 
> Do you mean with maxvcpu=4 vcpus=2 in your config?
> 
> >  then I run command 'xl vcpu-set $domID 4'.
> 
> >     There are only 2 CPUs(cpu0 and cpu1) listed in
> /sys/devices/system/cpu directory.
> 
> The bugzilla says "But it'll effect to dom0.", does this mean that
> 	xl vcpu-set domU 4
> will actually set dom0 to 12 vcpus? Or does it just mean that
> 	xl vcpu-set 0 4
> works where
> 	xl vcpu-set domU 4
> does not?
> 
'xl vcpu-set 0 4' works well for dom0 in some circumstances.
'xl vcpu-set domU 4' doesn't work for dumU at all.

'xl vcpu-set' for dom0 also has a bug. 
You can use 'xl vcpu-set' command to decrease vCPU number for dom0;
but when you try to increase its number you might meet dom0 panic.
Please look at my comment #2 in the following BZ.
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730

> There's quite a bit of potentially useful info missing from the bug
> report, like guest config details, xenstore content etc,
> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has a list of
> various log files which are often useful to help solve bugs, please do
> consider including those which seem relevant on future bug reports.
> 
Thanks for your advice. We'll pay more attention to this.

-Jay

> Ian.
> 
> >
> > > There is a race in the generic hotplug code.
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> 

Re: VMX status report. Xen:25334 & Dom0:568b445...

[Konrad Rzeszutek Wilk]

On Wed, May 23, 2012 at 08:21:24AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> > Sent: Tuesday, May 22, 2012 4:32 PM
> > To: Ren, Yongjie
> > Cc: Konrad Rzeszutek Wilk; Wu, GabrielX; Liu, SongtaoX; Zhou, Chao;
> > 'xen-devel@lists.xen.org'
> > Subject: Re: [Xen-devel] VMX status report. Xen:25334 & Dom0:568b445...
> > 
> > On Tue, 2012-05-22 at 08:19 +0100, Ren, Yongjie wrote:
> > > > -----Original Message-----
> > > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > > Sent: Monday, May 21, 2012 10:22 PM
> > > > To: Wu, GabrielX
> > > > Cc: 'xen-devel@lists.xen.org'; Ren, Yongjie; Liu, SongtaoX; Zhou, Chao
> > > > Subject: Re: [Xen-devel] VMX status report. Xen:25334 &
> > Dom0:568b445...
> > > >
> > > > On Mon, May 21, 2012 at 03:05:28AM +0000, Wu, GabrielX wrote:
> > > > > Hi all,
> > > > >
> > > > > This is the test report of xen-unstable tree.
> > > > > There are two issues found and one issue got fixed.
> > > > >
> > > > > Version Info:
> > > > >
> > > >
> > ============================================================
> > > > =====
> > > > > xen-changeset:   25334:f8279258e3c9
> > > > > Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...)
> > > > >
> > > >
> > ============================================================
> > > > =====
> > > > >
> > > > > New issues(2)
> > > > > ==============
> > > > > 1. long stop during the guest boot process with qcow image
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> > > > > 2. vcpu-set doesn't take effect on guest
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > >
> > > > Does it work if you (in the guest) do
> > > > echo 1 > /sys/../cpu9/online ?
> > > >
> > > The problem is there's no hot-add vCPU in /sys/devices/system/cpu
> > directory.
> > > e.g. I start a guest with 2 vCPU,
> > 
> > Do you mean with maxvcpu=4 vcpus=2 in your config?
> > 
> > >  then I run command 'xl vcpu-set $domID 4'.
> > 
> > >     There are only 2 CPUs(cpu0 and cpu1) listed in
> > /sys/devices/system/cpu directory.
> > 
> > The bugzilla says "But it'll effect to dom0.", does this mean that
> > 	xl vcpu-set domU 4
> > will actually set dom0 to 12 vcpus? Or does it just mean that
> > 	xl vcpu-set 0 4
> > works where
> > 	xl vcpu-set domU 4
> > does not?
> > 
> 'xl vcpu-set 0 4' works well for dom0 in some circumstances.
> 'xl vcpu-set domU 4' doesn't work for dumU at all.
> 
> 'xl vcpu-set' for dom0 also has a bug. 
> You can use 'xl vcpu-set' command to decrease vCPU number for dom0;
> but when you try to increase its number you might meet dom0 panic.
> Please look at my comment #2 in the following BZ.
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730

That should have been fixed in 3.4 by cf405ae612b0f7e2358db7ff594c0e94846137aa
"xen/smp: Fix crash when booting with ACPI hotplug CPUs."

Re: VMX status report. Xen:25334 & Dom0:568b445...

[Ren, Yongjie]

> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Wednesday, May 23, 2012 11:44 PM
> To: Ren, Yongjie
> Cc: Ian Campbell; Wu, GabrielX; Liu, SongtaoX; Zhou, Chao;
> 'xen-devel@lists.xen.org'
> Subject: Re: [Xen-devel] VMX status report. Xen:25334 & Dom0:568b445...
> 
> On Wed, May 23, 2012 at 08:21:24AM +0000, Ren, Yongjie wrote:
> > > -----Original Message-----
> > > From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> > > Sent: Tuesday, May 22, 2012 4:32 PM
> > > To: Ren, Yongjie
> > > Cc: Konrad Rzeszutek Wilk; Wu, GabrielX; Liu, SongtaoX; Zhou, Chao;
> > > 'xen-devel@lists.xen.org'
> > > Subject: Re: [Xen-devel] VMX status report. Xen:25334 &
> Dom0:568b445...
> > >
> > > On Tue, 2012-05-22 at 08:19 +0100, Ren, Yongjie wrote:
> > > > > -----Original Message-----
> > > > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > > > Sent: Monday, May 21, 2012 10:22 PM
> > > > > To: Wu, GabrielX
> > > > > Cc: 'xen-devel@lists.xen.org'; Ren, Yongjie; Liu, SongtaoX; Zhou,
> Chao
> > > > > Subject: Re: [Xen-devel] VMX status report. Xen:25334 &
> > > Dom0:568b445...
> > > > >
> > > > > On Mon, May 21, 2012 at 03:05:28AM +0000, Wu, GabrielX wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > This is the test report of xen-unstable tree.
> > > > > > There are two issues found and one issue got fixed.
> > > > > >
> > > > > > Version Info:
> > > > > >
> > > > >
> > >
> ============================================================
> > > > > =====
> > > > > > xen-changeset:   25334:f8279258e3c9
> > > > > > Dom0:          linux.git  3.4.0-rc7+ (commit: 568b445...)
> > > > > >
> > > > >
> > >
> ============================================================
> > > > > =====
> > > > > >
> > > > > > New issues(2)
> > > > > > ==============
> > > > > > 1. long stop during the guest boot process with qcow image
> > > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> > > > > > 2. vcpu-set doesn't take effect on guest
> > > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > > > >
> > > > > Does it work if you (in the guest) do
> > > > > echo 1 > /sys/../cpu9/online ?
> > > > >
> > > > The problem is there's no hot-add vCPU in /sys/devices/system/cpu
> > > directory.
> > > > e.g. I start a guest with 2 vCPU,
> > >
> > > Do you mean with maxvcpu=4 vcpus=2 in your config?
> > >
> > > >  then I run command 'xl vcpu-set $domID 4'.
> > >
> > > >     There are only 2 CPUs(cpu0 and cpu1) listed in
> > > /sys/devices/system/cpu directory.
> > >
> > > The bugzilla says "But it'll effect to dom0.", does this mean that
> > > 	xl vcpu-set domU 4
> > > will actually set dom0 to 12 vcpus? Or does it just mean that
> > > 	xl vcpu-set 0 4
> > > works where
> > > 	xl vcpu-set domU 4
> > > does not?
> > >
> > 'xl vcpu-set 0 4' works well for dom0 in some circumstances.
> > 'xl vcpu-set domU 4' doesn't work for dumU at all.
> >
> > 'xl vcpu-set' for dom0 also has a bug.
> > You can use 'xl vcpu-set' command to decrease vCPU number for dom0;
> > but when you try to increase its number you might meet dom0 panic.
> > Please look at my comment #2 in the following BZ.
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> 
> That should have been fixed in 3.4 by
> cf405ae612b0f7e2358db7ff594c0e94846137aa
> "xen/smp: Fix crash when booting with ACPI hotplug CPUs."
No, not yet. We tested against latest linux.git (already including that commit) as dom0, 
but found that bug #1730 still exist.