Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Cannot start xend: ERROR Internal error: Could not lock memory for Xen hypercall (35 = Resource temporarily unavailabl)



On Sun, May 31, 2009 at 10:24:18PM +0200, Stephane Bortzmeyer wrote:
> First experience with NetBSD as a Dom0. The Dom0 starts but no DomU
> works.
> 
> I bvelieve I followed exactly
> <http://www.netbsd.org/ports/xen/howto.html>. The NetBSD Dom0 boots
> and runs fine. But xend cannot start:
> 
> golgoth:pkg/etc/rc.d % sudo sh -x ./xend start
> ...
> + mkdir -p /var/run/xend
> + mkdir -p /var/run/xend/boot
> + mkdir -p /var/run/xenstored
> + eval echo Starting xend. && 
> PATH=/home/stephane/bin:/local/sbin:/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/sbin:/usr/sbin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/sbin
>  /usr/pkg/sbin/xend start
> + echo Starting xend.
> Starting xend.
> + 
> PATH=/home/stephane/bin:/local/sbin:/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/sbin:/usr/sbin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/sbin
>  /usr/pkg/sbin/xend start
> ERROR Internal error: Could not lock memory for Xen hypercall (35 = Resource 
> temporarily unavailabl)
> + [ -z  ]
> + return 1
> 
> The machine is a noname PC (32bits) with NetBSD 5. uname -a reports:
> 
> NetBSD golgoth 5.0 NetBSD 5.0 (XEN3_DOM0) #0: Sun Apr 26 19:06:57 UTC 2009  
> builds%b6.netbsd.org@localhost:/home/builds/ab/netbsd-5-0-RELEASE/i386/200904260229Z-obj/home/builds/ab/netbsd-5-0-RELEASE/src/sys/arch/i386/compile/XEN3_DOM0
>  i386
> 
> Xen comes from a package. pkg_info reports:
> 
> xentools3-3.1.4nb4  Userland Tools for Xen
> xenkernel3-3.1.4nb3 Xen3 Kernel

How much RAM did you give to your dom0 ?

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index