[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen4.2-rc3 test result
> -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] > Sent: Thursday, September 06, 2012 4:29 PM > To: Ren, Yongjie > Cc: Konrad Rzeszutek Wilk; 'xen-devel'; Keir (Xen.org); 'Jan Beulich'; > 'Konrad Rzeszutek Wilk' > Subject: Re: [Xen-devel] Xen4.2-rc3 test result > > On Thu, 2012-09-06 at 09:18 +0100, Ren, Yongjie wrote: > > > -----Original Message----- > > > From: Konrad Rzeszutek [mailto:ketuzsezr@xxxxxxxxx] On Behalf Of > > > Konrad Rzeszutek Wilk > > > Sent: Saturday, September 01, 2012 1:24 AM > > > To: Ren, Yongjie > > > Cc: 'xen-devel'; 'Keir Fraser'; 'Ian Campbell'; 'Jan Beulich'; 'Konrad > > > Rzeszutek Wilk' > > > Subject: Re: [Xen-devel] Xen4.2-rc3 test result > > > > > > 5. Dom0 cannot be shutdown before PCI detachment from guest and > > > when pci assignment conflicts > > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826 > > > > > > Um, so you are assigning the same VF to two guests. I am surprised > that > > > the tools even allowed you to do that. Was 'xm' allowing you to do > that? > > > > > No, 'xl' doesn't allow me to do that. We can't assignment a device to > different guests. > > Sorry, the description of this bug is not accurate. I changed its title to > "Dom0 cannot be shut down before PCI device detachment from a guest". > > If a guest (with a PCI device assigned) is running, Dom0 will panic when > shutting down. > > So this is a dom0 kernel issue and not something relating to 4.2? In > which case I shall remove it from the 4.2 TODO list. > I don't think so. In my testing, it should be a regression from Xen 4.1 to 4.2. Xen4.1(22972) + Dom0(kernel3.5.3) = good Xen4.2(25791) + Dom0(kernel3.5.3) = bad (it has this issue.) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |