Date: Thu, 29 Jun 2017 11:00:50 +0100 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com> To: Larry Rosenman <ler@lerctr.org> Cc: Allan Jude <allanjude@freebsd.org>, <freebsd-virtualization@freebsd.org> Subject: Re: Xen Dom0 Message-ID: <20170629100050.vn4hdtupn6hckcyh@dhcp-3-128.uk.xensource.com> In-Reply-To: <B64E8F54-4C0B-4B22-97CA-1AE942020E1C@lerctr.org> References: <20170624201125.d75fxtfauzclvtz6@lrosenman.lerctr.org> <e1af5269-8bba-4e9b-6677-efbc8b63f76f@freebsd.org> <20170625125025.x7rs5cofhhhq7ijs@lrosenman.local> <20170625132830.22ul25hdtd7qep22@lrosenman.lerctr.org> <B64E8F54-4C0B-4B22-97CA-1AE942020E1C@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Sorry for the delay, I don't read freebsd-virt as often as I should. There's also freebsd-xen@ for FreeBSD/Xen specific issues (although posting here is fine). On Wed, Jun 28, 2017 at 11:44:27PM -0500, Larry Rosenman wrote: > Any ideas? When was the last time that you updated world (or more specifically /boot/)? Could you please attempt the following and try again: cd sys/boot/ && make && make install I've just tested the port with the current loader code and seems to work fine. There was a brief period of time when HEAD couldn't boot a Xen kernel, IIRC it's ~3month ago or so. That was fixed, but you might just happen to have a loader from that time. Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170629100050.vn4hdtupn6hckcyh>