[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Xen 4.1 rc5 outstanding bugs



I used rhel5u5 as guest and cannot reproduce this issue in my westmere-EP. Can 
you have a try with rhel5u5 guest?

Host: westmere-ep

Software:
Xen 4.1-rc6-pre
Pvops dom0: rhel5u5 with 2.6.32.27
Guest: rhel5u5

best regards
yang


> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Anthony
> PERARD
> Sent: Tuesday, February 22, 2011 1:30 AM
> To: Stefano Stabellini
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Jan Beulich
> Subject: Re: [Xen-devel] Xen 4.1 rc5 outstanding bugs
> 
> On Mon, Feb 21, 2011 at 11:05, Stefano Stabellini
> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
> > On Mon, 21 Feb 2011, Jan Beulich wrote:
> >> >>> On 18.02.11 at 19:59, Stefano Stabellini
> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
> >> > Â* ÂXen panic on guest shutdown with PCI Passthrough
> >> >
> http://xen.1045712.n5.nabble.com/Xen-panic-on-guest-shutdown-with-PCI-Pas
> sthrough-tt
> >> > 3371337.html#none
> >> > When the guest with a passthrough pci device is shut down, Xen panic
> >> > on a NMI - MEMORY ERROR.
> >> > (XEN) Xen call trace:
> >> > (XEN) Â Â[<ffff82c48015f032>] msi_set_mask_bit+0xea/0x121
> >> > (XEN) Â Â[<ffff82c48015f087>] mask_msi_irq+0xe/0x10
> >> > (XEN) Â Â[<ffff82c480162fb1>] __pirq_guest_unbind+0x298/0x2aa
> >> > (XEN) Â Â[<ffff82c48016315c>] unmap_domain_pirq+0x199/0x307
> >> > (XEN) Â Â[<ffff82c480163321>] free_domain_pirqs+0x57/0x83
> >> > (XEN) Â Â[<ffff82c48015642a>] arch_domain_destroy+0x30/0x2e3
> >> > (XEN) Â Â[<ffff82c480104c59>] complete_domain_destroy+0x6e/0x12a
> >> > (XEN) Â Â[<ffff82c48012adfd>] rcu_process_callbacks+0x173/0x1e1
> >> > (XEN) Â Â[<ffff82c480123327>] __do_softirq+0x88/0x99
> >> > (XEN) Â Â[<ffff82c4801233a2>] do_softirq+0x6a/0x7a
> >>
> >> Are you sure you want to consider this one severe? Xen by itself
> >> can't cause NMIs (unless sending IPIs as such, which certainly isn't
> >> the case here), and iirc from the mailing list post corresponding to
> >> this it's being observed only on a single (with the above presumably
> >> buggy) system.
> >
> > Good point. We should have another identical machine, we'll try to
> > reproduce it there.
> 
> I have the same issue on another identical machine.
> 
> Host: Dell System PowerEdge R310
> 
> Dom0: Debian Squeeze with Kernel dom0 2.6.32.27
> Xen 4.1-rc6-pre
> Guest: Debian lenny with default kernel.
> 
> pci devices:
> Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet
> 02:00.0 -> passthrough to guest
> 02:00.1 -> keep as network card for dom0
> 
> A bug report have been filled here:
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1744
> 
> --
> Anthony PERARD
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.