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

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

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

> 
> 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


> 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 :)


> 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...


> 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.

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