Date: Tue, 26 Mar 2013 11:10:15 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> To: Colin Percival <cperciva@freebsd.org> Cc: xen-users <xen-users@lists.xen.org>, "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Re: [Xen-users] Trouble booting FreeBSD i386 PV DomU Message-ID: <51517407.8040406@citrix.com> In-Reply-To: <51516CAA.3040802@freebsd.org> References: <CAMCOOJuzLvw=X2M8=6bwKvseGt2h9FgA49L7mtQZwAVEmJ6Ahg@mail.gmail.com> <51516B06.8080704@citrix.com> <51516CAA.3040802@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26/03/13 10:38, Colin Percival wrote: > On 03/26/13 02:31, Roger Pau Monné wrote: >> Is Xen i386 PV broken? > > Not completely broken, but it's certainly not in a good state. I believe > it's broken with SMP, for example -- if the "crashed on cpu#7" in your > output means cpu#7 from the guest, it would certainly explain things. My guest only has one vcpu (vcpu#0): Domain 12 (vcpu#0) crashed on cpu#7 That is running on physical CPU 7 > HVM is the way to go with FreeBSD/Xen. Yes, I'm already working on that, and got vector callbacks working on both i386 and amd64 HVM guests, thanks to Justin T. Gibbs patch. Now I was trying to boot a PV guest to see how much breakage this change introduced to PV, but I'm not able to make it work, even without my patches. I've replied to this xen-users thread because the author seem to have a working FreeBSD DomU PV guest, and I was wondering how he did it. From my POV it seems like PV guests hasn't been working for a long time, since Xen 3.3 dropped support for non-PAE guests, and the FreeBSD kernel is detected as non-PAE.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51517407.8040406>