Re: [Xen-devel] VMX test report for Xen 4.4-unstable-C/S 27314

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 08.08.13 at 09:13, "Ren, Yongjie" <yongjie.ren@xxxxxxxxx> wrote:
> Hi All,
> This is a report based on our testing for Xen 4.4-unstable on Intel 
> platforms.
> Test environment:
> Xen: Xen 4.4-unstable with qemu-upstream-unstable.git
> Changeset: 27314:e6ca87e13937
> Dom0: Linux kernel 3.10.5
> Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems
> 
> New bugs (3): 
> 1. Large file remote copy in Windows guest (no GPL PV driver) cause 
> networking broken
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1862 
> 2. device pass-through works even if VT-d is disabled in BIOS
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1866 

Are you sure this was seen with 27314:e6ca87e13937? I ask
because 27204:06c2f6031aff is supposed to be taking care of
this (and it did in my and - I think - also in others' testing). To
make things even less clear, the bug itself mentions 27203 and
27214...

> 3. "xl list" shows no guest vcpu status when setting maxcpus=1 in hypervisor 
> grub line
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1867 

What would you expect to see? If the guest is runnable, none
of the flags would be set (not running, not blocked, not paused,
not shut down, no shutdown reason, not dying). There simply
is no "runnable" indicator, and on an overcommitted system with
more than 1 pCPU you ought to be able to observe the same.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel