Date: Thu, 17 Jan 2013 12:53:43 -0600 From: Mark Felder <feld@feld.me> To: Steven Chamberlain <steven@pyro.eu.org> Cc: freebsd-xen@freebsd.org, Christoph Egger <Christoph_Egger@gmx.de>, xen-devel@lists.xen.org Subject: Re: [Xen-devel] Fwd: xenbusb_nop_confighook_cb timeout and cd issue Message-ID: <op.wq2j3t1234t2sn@markf.office.supranet.net> In-Reply-To: <50F81F31.3070103@pyro.eu.org> References: <4AD92DFA-7153-4E79-B906-1CBEAAC6B6A3@sarenet.es> <CACAFB0D-0EA1-44FB-8622-0C547B5F0FCE@sarenet.es> <50F3A8F8.7050809@pyro.eu.org> <50F7A9E8.4030007@gmx.de> <50F7DE55.8060101@pyro.eu.org> <op.wq18zu1d34t2sn@markf.office.supranet.net> <50F813CB.7050801@pyro.eu.org> <7ba7ddf7-3034-4422-8eed-5299318454a9@email.android.com> <50F81F31.3070103@pyro.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 Jan 2013 09:56:33 -0600, Steven Chamberlain <steven@pyro.eu.org> wrote: > On 17/01/13 15:24, Mark Felder wrote: >> I no longer have that environment that I was using to test the >> viability of upgrading to XCP 1.6 but it was reproducible every boot. > > Just to clarify - you rebooted the dom0/hypervisor also? > > I know the bug is reproducible on every FreeBSD domU boot, at least. > We did reboot the dom0 more than once but I didn't test that specifically to see if the problem would subside after a few reboots.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wq2j3t1234t2sn>