This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] xen 4.1 rc2 test report ( 5new issues found)

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] xen 4.1 rc2 test report ( 5new issues found)
From: "Zheng, Shaohui" <shaohui.zheng@xxxxxxxxx>
Date: Sun, 30 Jan 2011 10:27:53 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 29 Jan 2011 18:28:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1101281646000.7277@kaball-desktop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A24AE1FFE7AEC5489F83450EE98351BF2C5A81CA40@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1101281646000.7277@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acu/C+1NuIamw5qDQhen09WsO11w0wBE4y8w
Thread-topic: [Xen-devel] xen 4.1 rc2 test report ( 5new issues found)

Thanks & Regards,

> -----Original Message-----
> From: Stefano Stabellini [mailto:stefano.stabellini@xxxxxxxxxxxxx]
> Sent: Saturday, January 29, 2011 12:55 AM
> To: Zheng, Shaohui
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] xen 4.1 rc2 test report ( 5new issues found)
> On Fri, 28 Jan 2011, Zheng, Shaohui wrote:
> > Save/Restore(1 bug)
> > 1. RHEL6 guest fail to do save/restore (Community)
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1716
> the bug has been filed on red hat's bugzilla
Let 's track it in xen's bugzilla, too.

> >
> > xl command(5 bugs)
> > 1. xl does not check the duplicated configure file and image file 
> > (Community)
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1711
> patches are coming to fix this
> > 2. Guest network broken after do SAVE/RESTOR with xl (Community)
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1703
> cannot reproduce this bug
After save/restore guest OS, We can not ping any address, we need to run 
dhclient to re-fetch an IP address, and the network works again.
The expected result is that guest network still working after restore it.

> > 3. xl does not check the memory size of guest(Community)
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1729
> I am not entirely sure we should try to solve this bug, after all we
> should always try to do what the user asks us to do, even if it doesn't
> make sense :)

It is a critical issue in fact. the request to create a very large guest will 
fail obviously, but the system status already becomes abnormal. It prints a lot 
error information continuously. 

(XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 
(XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 

And We cannot create any guest any more except reboot the system.

> > 4. "xl vcpu-set" causes dom0 crash or panic (Community)
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
> The repro steps say: "xl vcpu-set 0 16" but the vcpu-set commands
> actually takes 3 arguments:
> Usage: xl [-v] vcpu-pin <Domain> <VCPU|all> <CPUs|all>
> In any case the bug looks like a dom0 kernel bug more than anything
> else...

You are showing the Usage of "xl vcpu-pin", not "xl vcpu-set",  "xl vcpu-set" 
takes 2 arguments.

[root@vt-nhm7 ~]# xl help vcpu-set
Usage: xl [-v] vcpu-set <Domain> <vCPUs>

Set the number of active VCPUs allowed for the domain.

> > 5. "xl vcpu-list" does not response after run vcpu-pin(Community)
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1731
> Are use sure this is not just because the system has become very very
> slow because 5 vcpus are running in a single pcpu?
> Because I tried the very same steps reported above and it seems to work
> for me.

It is NOT because we bind too much vcpu to the a single pcpu.  "xm vcpu-list" 
can list the vcpus which does not do the binding only, but for the binded vcpu, 
even though we bind only one vcpu to a pcpu, "xl vcpu-list" command does not 
return, either. We need to type "CTRL-C" to terminate it.

Xen-devel mailing list