Re: fun with xen caps

[Michael Litchard <michael%schmong.org@localhost>]

I've updated to latest working -current, using a i386 PAE domU.
Here's the error
lucius# xm create ./domU1 -c
Using config file "././domU1".
Xend has probably crashed!  Invalid or missing HTTP status code.

running tail -f on the various log files didn't turn anything up.
Could I get some help troubleshooting this?
Also, here's uname

NetBSD lucius.nexus.org 5.99.18 NetBSD 5.99.18 (XEN3_DOM0) #0: Sun Sep
20 18:45:23 UTC 2009
builds%b7.netbsd.org@localhost:/home/builds/ab/HEAD/amd64/200909210000Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/XEN3_DOM0
amd64

On Thu, Sep 24, 2009 at 5:11 PM, Sarton O'Brien 
<bsd-xen%roguewrt.org@localhost> wrote:
> On 25/09/2009 7:15 AM, Michael Litchard wrote:
>>
>> right now this is what xen caps looks like
>> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
>>
>> Do I need pae support for a x86 domU when the domO is amd64?
>> If not, how do I re-compile xen to allow the non-pae x86 xen?
>
> Yes, you do ... and from my understanding, you can't ...
>
> With an amd64 dom0 and a PV guest you will need either an amd64 domU or an
> i386-PAE domU. I don't believe these limitations apply to HVM though but I
> don't use HVM so don't quote me :) ... the i386-PAE kernel is a drop-in
> replacement for the old 1386 kernels.
>
> All distro linux xen kernels tend to be PAE enabled. Actually, this is why I
> switched to an amd64 dom0, out-of-the-box functionality with linux.
>
> If you already have a NetBSD PV guest OS that is i386, your best bet would
> be to use an i386-PAE kernel and upgrade your userland.
>
> Unfortunately when it comes to PAE and PV guests, it's all or nothing. I
> managed to convert all my old i386 guests to amd64 with very little trouble
> (vnd->domu, extract sets, replace kernel, etcupdate), so it's not all bad