Date: Thu, 24 Jan 2013 15:16:21 +0100 From: Jeroen van der Ham <jeroen@dckd.nl> To: Mark Felder <feld@feld.me> Cc: freebsd-xen@freebsd.org Subject: Re: Upgrading XENHVM 9.0 to 9.1 Message-ID: <FDEBD15D-C641-4E26-9F11-C5E8E6A97EC4@dckd.nl> In-Reply-To: <op.wre4bpu734t2sn@markf.office.supranet.net> References: <C20E2886-F631-4A64-B351-3763BB8AE8A3@dckd.nl> <op.wre4bpu734t2sn@markf.office.supranet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 24 Jan 2013, at 14:41, Mark Felder <feld@feld.me> wrote: >> - I manually downloaded and extracted the 9.1 GENERIC kernel. Booting = from that results in a rootmount mismatch (ada0 vs ad0). Just renaming = it in /etc/fstab does not seem to be enough, what else would I need to = do? >=20 > Yes, the GENERIC kernel uses adaX and the XENHVM kernel uses adX. It = shouldn't be a problem to just change it in the fstab though. I've not = yet had problems running 9.1 with XENHVM yet. I tried this both using the mountroot prompt when booting with an old = fstab and a corrected fstab. In both cases the kernel is not able to = mount the UFS volume. >> - I manually built a new 9.1 XENHVM kernel. Booting from that results = in the message: "pudna: fpcurthread =3D=3D curthread xx times" scrolling = by. What can I do to fix that? >>=20 >=20 > I've not seen this message yet either.=20 I've seen this message also previously when I was toying around with my = 9.0 system. I forget what exactly I did though. There are some references to it in earlier cases, dating back to 2005: http://marc.info/?l=3Dfreebsd-amd64&m=3D112231842214570 Another in 2010: http://forums.freebsd.org/showthread.php?t=3D17979 (I did not try those options yet though) > Can you provide more details of the Xen environment you're hosted on? AMD Opteron system, with kernel 2.6.32 on Dom0, using 4.0.1-2. My VPS is run using Xen qemu. >> Is there a problem in continuing to run the 9.0 XENHVM kernel with = the 9.1 system? >>=20 >=20 > This would not be advised. It *may* work, but be warned that you may = run into strange issues. I noticed that freebsd-update started complaining during its cron-job. = I've since performed a freebsd-update rollback. Jeroen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FDEBD15D-C641-4E26-9F11-C5E8E6A97EC4>