VMX test report for Xen 4.5-unstable-git commit:8cfc8e520679e029bed51ccc2540a136fc0fbd9b

VMX test report for Xen 4.5-unstable-git commit:8cfc8e520679e029bed51ccc2540a136fc0fbd9b

[Hu, Robert]

Hi All,
This is a report based on our testing for Xen 4.5-unstable on Intel platforms.

Test environment:
Xen: Xen 4.5-unstable with qemu-upstream-unstable.git
git commit:8cfc8e520679e029bed51ccc2540a136fc0fbd9b
Dom0: Linux kernel 3.14.1
Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell Bridge

New bugs (2): 
1. Dumping the ept p2m table leads dom0 call trace
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1885
2. Failed to create a nested L2 guest based XEN on XEN
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1887

Verified bug(1):
1. After live migration, guest console continuously prints "Clocksource tsc unstable"
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854

Old bugs (5):
1. [XL]"xl vcpu-set" causes dom0 crash or panic
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1730
2. Dom0 cannot be shutdown before PCI device detachment from guest
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1826
3. [upstream qemu] Guest free memory with upstream qemu is 14MB lower than that with qemu-xen-unstable.git
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1836
4. sometimes failed to online cpu in Dom0
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
5. Booting multiple guests will lead Dom0 call trace
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853

Re: VMX test report for Xen 4.5-unstable-git commit:8cfc8e520679e029bed51ccc2540a136fc0fbd9b

[Jan Beulich]

>>> On 02.05.14 at 10:44, <robert.hu@intel.com> wrote:
> 1. Dumping the ept p2m table leads dom0 call trace
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1885 

This is very clearly not a bug - dumping the entire page tables for
perhaps multiple domains _is going to take long_. As a general
rule for debug keys - if use of them causes problems in production
environments, _just don't use them_ (as their name implies, they're
for debugging after all).

Jan

Re: VMX test report for Xen 4.5-unstable-git commit:8cfc8e520679e029bed51ccc2540a136fc0fbd9b

[Andrew Cooper]

On 02/05/14 09:44, Hu, Robert wrote:
> Hi All,
> This is a report based on our testing for Xen 4.5-unstable on Intel platforms.
>
> Test environment:
> Xen: Xen 4.5-unstable with qemu-upstream-unstable.git
> git commit:8cfc8e520679e029bed51ccc2540a136fc0fbd9b
> Dom0: Linux kernel 3.14.1
> Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell Bridge
>
> New bugs (2): 
> 1. Dumping the ept p2m table leads dom0 call trace
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1885

Dont Do That Then.

xl debug-key $FOO will hog a dom0 vcpu and Xen pcpu in a hypercall until
$FOO has completed.

If you need this information, use $FOO on a serial console which at
least wont monopolise dom0.

~Andrew

> 2. Failed to create a nested L2 guest based XEN on XEN
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1887
>
> Verified bug(1):
> 1. After live migration, guest console continuously prints "Clocksource tsc unstable"
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854
>
> Old bugs (5):
> 1. [XL]"xl vcpu-set" causes dom0 crash or panic
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1730
> 2. Dom0 cannot be shutdown before PCI device detachment from guest
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1826
> 3. [upstream qemu] Guest free memory with upstream qemu is 14MB lower than that with qemu-xen-unstable.git
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1836
> 4. sometimes failed to online cpu in Dom0
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
> 5. Booting multiple guests will lead Dom0 call trace
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel