From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Kernel bug from 3.0 (was phy disks and vifs timing out in DomU) Date: Fri, 26 Aug 2011 14:23:32 +0300 Message-ID: <20110826112331.GC32373@reaktio.net> References: <24093349.14.1311837878822.JavaMail.root@zimbra.overnetdata.com> <4E31820C.5030200@overnetdata.com> <1311870512.24408.153.camel@cthulhu.hellion.org.uk> <4E3266DE.9000606@overnetdata.com> <20110803152841.GA2860@dumpdata.com> <4E4E3957.1040007@overnetdata.com> <20110819125615.GA26558@dumpdata.com> <4E56BA90.3050907@overnetdata.com> <1598888077.20110826091056@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1598888077.20110826091056@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sander Eikelenboom Cc: Ian Campbell , Todd Deshane , "xen-devel@lists.xensource.com" , Anthony Wright , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Fri, Aug 26, 2011 at 09:10:55AM +0200, Sander Eikelenboom wrote: > Hello Anthony, > > Perhaps you could try running with xend instead of the xl toolstack ? > Since you have also changed the hypervisor version to 4.1.1, i think you were previously using xend instead of xl ? > > So in theory it could also be a problem in the xl toolstack causing the extra qemu processes when building the domain. > Are you using pvfb for the domU? If yes, pvfb needs qemu-dm for the VNC server.. -- Pasi > > Sander > > Thursday, August 25, 2011, 11:11:44 PM, you wrote: > > > On 19/08/2011 13:56, Konrad Rzeszutek Wilk wrote: > >> On Fri, Aug 19, 2011 at 11:22:15AM +0100, Anthony Wright wrote: > >>> On 03/08/2011 16:28, Konrad Rzeszutek Wilk wrote: > >>>> On Fri, Jul 29, 2011 at 08:53:02AM +0100, Anthony Wright wrote: > >>>>> I've just upgraded to xen 4.1.1 with a stock 3.0 kernel on dom0 (with > >>>>> the vga-support patch backported). I can't get my DomU's to work due to > >>>>> the phy disks and vifs timing out in DomU and looking through my logs > >>>>> this morning I'm getting a consistent kernel bug report with xen > >>>>> mentioned at the top of the stack trace and vifdisconnect mentioned on > >>>> Yikes! Ian any ideas what to try? > >>>> > >>>> Anthony, can you compile the kernel with debug=y and when this happens > >>>> see what 'xl dmesg' gives? Also there is also the 'xl debug-keys g' which > >>>> should dump the grants in use.. that might help a bit. > >>> I've compiled a 3.0.1 kernel with CONFIG_DEBUG=Y (a number of other > >>> config values appeared at this point, and I took defaults for them). > >>> > >>> The output from /var/log/messages & 'xl dmesg' is attached. There was no > >>> output from 'xl debug-keys g'. > >> Ok, so I am hitting this too - I was hoping that the patch from Stefano > >> would have fixed the issue, but sadly it did not. > >> > >> Let me (I am traveling right now) see if I can come up with an internim > >> solution until Ian comes with the right fix. > >> > > On different hardware with the same software I'm also getting problems > > starting DomUs, but this time the error is different. I've attached a > > copy of the xl console output, but basically the server hang at > > "Mount-cache hash table entries: 512". Again the VM is paravirtualised, > > and again I get a qemu-dm process for it. > > > The references to this message are normally related to memory issues, > > but the server has only 1000M of ram, so can't see it causing too much > > of a problem. > > > Is this related to the other problems I'm seeing or completely separate? > > > thanks, > > > Anthony > > > > > > -- > Best regards, > Sander mailto:linux@eikelenboom.it > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel