Date: Sun, 16 Nov 2014 13:19:51 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-virtualization@freebsd.org Subject: Re: Trying to run an older head in a recent Bhyve. Message-ID: <5468EAC7.3030601@freebsd.org> In-Reply-To: <5468E4B9.5090205@digiware.nl> References: <5467BC49.4080308@digiware.nl> <5467E8E6.1000509@freebsd.org> <5468E4B9.5090205@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-11-16 12:54, Willem Jan Withagen wrote: > On 16-11-2014 0:59, Peter Grehan wrote: >> Hi Willem, >> >>> I'm trying to run one of my older VM's and get the crash below in the= VM >>> when trying to boot... >>> >>> This happens both on an older BSD: >>> FreeBSD 11.0-CURRENT (FREETEST) #1 r273066M: Sun Oct 19 00:59:06 CEST= >>> 2014 >>> As well as on a very recent: >>> FreeBSD 11.0-CURRENT (BHYVE00) #0 r274490M: Fri Nov 14 02:42:43 CET 2= 014 >>> >>> The older 10.0 VM's do boot normally >>> >>> Any suggestions on what this might be, and/or how to debug this.. >> >> Did the disk image backing file change by any chance ? e.g. from file= >> to zvol ? >> >> What's the version of the VM that has the issue ? >=20 > Not sure what you mean by that exactely, but the VM runs a relatively > old HEAD: >=20 > FreeBSD 11.0-CURRENT #1 r262690: Sun Mar 2 21:28:19 CET 2014 > root@bhyve-head:/usr/obj/usr/src/sys/GENERIC amd64 >=20 > It boots in single mode. >=20 > I'tt try and manually assign an IP number and will see what that brings= =2E >=20 > --WjW >=20 >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 He is asking how the virtual disk is setup, specifically, if it is a zvol= Judging by the backtrace, the VM is panicing when trying to write to the disk and it fails =46rom my experience, the two most likely causes are: 1) The disk is a zvol, and does not have the volmode set, and GEOM on the host is grabbing the disk and locking it, preventing writes 2) The VM was shutdown ungracefully and the file system needs a fsck. Since you can get into single user mode, this should be doable. --=20 Allan Jude --3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUaOrKAAoJEJrBFpNRJZKfy7YP/RliVOqMVMNQHzNleJzgeyGV J2OTuLWytjyM3Y0F9iBhC0cbG6cQBAYF3L39kj4aXi8D/faW+ZNISqJuA8UcBiv2 WfZUo+t7ROfH3eWO/RYkS2n0d3fiOShrjY0G3PFX3qeuWYcAJx6MtPthWVY0lFpb 9izIMDlT+iwMobXrvkiOokaIcHZS73OyEBXBKrLT6TMV/K9SZzrcJVWPXPw3UhN7 WkfvTiLjK16OsgcezcASGmaO7ek53Wzm9ABSW49P9uAivJtzzBaUA2F941F5z1WL 1hud3z6UtIlcIbVleN/BGuOKlPfegb9vYIr9x6qaO+/CZPmQSjGqwzZcasaIukI2 HsSq7CtUOQxCY05oGf/kv/bzpUIP/b+FkUH5HZ7kPiNg59bA0v94l7gA8rfGAZSr GLDRsIuOTl3yh4LuityciPZ/nv3Z0UypwbYXZYITTpg9VKPI3tBjVReyrxT6n8mH wf3tyZoiAgKVYz4Ilp2x3qN8jmWsWKXLCUt1S2iQu28idAemiG4eB4mNGuqCEooX bnYyBh+jifqouYl8VWfLDWh8JMlIWSCf693CymlW/5+eRI38+zlDWv2K2xaU/F/6 bLXKtw0kqzinjBcCiYQ71SKBlp3P1kxwuBLqICLIGBzOwz8syYm+SAaeTyH07iL+ JkVmlUSFvsS2XPuZTb75 =TM9y -----END PGP SIGNATURE----- --3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5468EAC7.3030601>