Hi all, This is the test report of xen-unstable tree. There is 2 issues found and no issue got fixed. Version Info: ================================================================xen-changeset: 25605:9950f2dc2ee6 Dom0: linux.git 3.4.4 ================================================================ New issues(2) =============1. parameter ''maxvcpus'' causes hvm guest boots up with wrong vcpu number http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1825 2. Dom0 cannot be shutdown before PCI detachment from guest and when pci assignment conflicts http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826 Fixed issue(0) ============= Old issues(10) =============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. RHEL6.2/6.1 guest runs quite slow http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811 6. after detaching a VF from a guest, shutdown the guest is very slow http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812 7. Poor performance when do guest save/restore and migration with linux 3.1 dom0 http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1784 8. long stop during the guest boot process with qcow image http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821 9. vcpu-set doesn''t take effect on guest http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822 10.Fail to probe NIC driver in domu http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1824 Thanks, Wu Ronghui(Gabriel)
Ian Campbell
2012-Jul-23 10:34 UTC
parameter ''maxvcpus'' causes hvm guest boots up with wrong vcpu number (Was: Re: VMX status report. Xen:25605 & Dom0:3.4.4)
On Wed, 2012-07-18 at 08:12 +0100, Wu, GabrielX wrote:> Hi all, > > This is the test report of xen-unstable tree. > There is 2 issues found and no issue got fixed. > > Version Info: > ================================================================> xen-changeset: 25605:9950f2dc2ee6 > Dom0: linux.git 3.4.4 > ================================================================> > New issues(2) > =============> 1. parameter ''maxvcpus'' causes hvm guest boots up with wrong vcpu number > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1825Zhang, I''m afraid your "libxl: allow setting more than 31 vcpus" change looks suspicious in relation to this bug falls in the range 25517:c6c9d20963d7 (last VMX status report) and 25605:9950f2dc2ee6 (this one). Are you able to take a look? Ian.
Ian Campbell
2012-Jul-23 10:38 UTC
xl allows multiple PCI attach of same device + triggers pciback bug(Was: Re: VMX status report. Xen:25605 & Dom0:3.4.4)
On Wed, 2012-07-18 at 08:12 +0100, Wu, GabrielX wrote:> Hi all, > > This is the test report of xen-unstable tree. > There is 2 issues found and no issue got fixed. > > Version Info: > ================================================================> xen-changeset: 25605:9950f2dc2ee6 > Dom0: linux.git 3.4.4 > ================================================================> > New issues(2) > =============[...] > 2. Dom0 cannot be shutdown before PCI detachment from guest and when pci assignment conflicts > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826I think there are two issues here. The first is that xl even allows you to assign the same device twice (I have included this as a BUG on this weeks TODO posting) and the second sounds like a kernel side / pciback bug). Konrad does that sound plausible? Ian.
Zhang, Yang Z
2012-Jul-23 12:20 UTC
Re: parameter ''maxvcpus'' causes hvm guest boots up with wrong vcpu number (Was: Re: VMX status report. Xen:25605 & Dom0:3.4.4)
Ian Campbell wrote on 2012-07-23:> On Wed, 2012-07-18 at 08:12 +0100, Wu, GabrielX wrote: >> Hi all, >> >> This is the test report of xen-unstable tree. >> There is 2 issues found and no issue got fixed. >> >> Version Info: >> > ============================================================> ===>> xen-changeset: 25605:9950f2dc2ee6 >> Dom0: linux.git 3.4.4 >> > ============================================================> ===>> >> New issues(2) >> =============>> 1. parameter ''maxvcpus'' causes hvm guest boots up with wrong vcpu number >> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1825 > > Zhang, > > I''m afraid your "libxl: allow setting more than 31 vcpus" change looks > suspicious in relation to this bug falls in the range 25517:c6c9d20963d7 > (last VMX status report) and 25605:9950f2dc2ee6 (this one). > > Are you able to take a look?Sure. I will look into it. Best regards, Yang
Konrad Rzeszutek Wilk
2012-Jul-23 14:31 UTC
Re: xl allows multiple PCI attach of same device + triggers pciback bug(Was: Re: VMX status report. Xen:25605 & Dom0:3.4.4)
On Mon, Jul 23, 2012 at 11:38:02AM +0100, Ian Campbell wrote:> On Wed, 2012-07-18 at 08:12 +0100, Wu, GabrielX wrote: > > Hi all, > > > > This is the test report of xen-unstable tree. > > There is 2 issues found and no issue got fixed. > > > > Version Info: > > ================================================================> > xen-changeset: 25605:9950f2dc2ee6 > > Dom0: linux.git 3.4.4 > > ================================================================> > > > New issues(2) > > =============> [...] > > 2. Dom0 cannot be shutdown before PCI detachment from guest and when pci assignment conflicts > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826 > > I think there are two issues here. The first is that xl even allows you > to assign the same device twice (I have included this as a BUG on this > weeks TODO posting) and the second sounds like a kernel side / pciback > bug). Konrad does that sound plausible?The pciback has logic to call this: 1666 /* Check whether the IRQ line is shared with other guests. */ 1667 int xen_test_irq_shared(int irq) 1668 { 1669 struct irq_info *info = info_for_irq(irq); 1670 struct physdev_irq_status_query irq_status = { .irq = info->u.pirq.pirq }; 1671 1672 if (HYPERVISOR_physdev_op(PHYSDEVOP_irq_status_query, &irq_status)) 1673 return 0; 1674 return !(irq_status.flags & XENIRQSTAT_shared); 1675 } 1676 EXPORT_SYMBOL_GPL(xen_test_irq_shared); to figure out whether it needs to Ack the interrupt line in dom0 - to avoid those ''nobody cared'' errors. Could it be that the XENIRQSTAT_shared is not being stampted anymore?> > Ian. > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel