Cannot create domU's on current: sysctl_createv: sysctl_create(xvif1.0) returned 22

[Hugo Silva-2]

After issuing 'xm create domU.conf':

/netbsd: xvif1.0: Ethernet address xx:xx:xx:xx:xx:xx
/netbsd: sysctl_createv: sysctl_create(xvif1.0) returned 22
/netbsd: xvif1.0: could not attach sysctl nodes



Commenting out the vif line allows the domU to boot.

System: NetBSD 5.99.21  (XEN3_DOM0) #0: Sat Nov  7 22:43:31 WET 2009  
root@dom0:/usr/obj/sys/arch/amd64/compile/XEN3_DOM0 amd64




domU config:
kernel = "/usr/pkg/xen/kern/vmlinuz-xen-install"
ramdisk = "/usr/pkg/xen/kern/initrd-xen-install"
#bootloader = "/usr/pkg/bin/pygrub"

memory = 1024
name   = "linux-pv"

#vcpus = 4
vif = [ 'mac=xx:xx:xx:xx:xx:xx, bridge=bridge0' ]

disk = [ 'phy:/dev/mapper/volgroup001-lv0,xvda,w' ]
#root = "xbd0"

# use to boot to single user (-s), etc
extra=""



Not sure if I should post this to current-users instead, let me know if
that's a better option..

[Hugo Silva-2]

Hugo Silva wrote:

> After issuing 'xm create domU.conf':
>
> /netbsd: xvif1.0: Ethernet address xx:xx:xx:xx:xx:xx
> /netbsd: sysctl_createv: sysctl_create(xvif1.0) returned 22
> /netbsd: xvif1.0: could not attach sysctl nodes
>
>
>
> Commenting out the vif line allows the domU to boot.
>
> System: NetBSD 5.99.21  (XEN3_DOM0) #0: Sat Nov  7 22:43:31 WET 2009  
> root@dom0:/usr/obj/sys/arch/amd64/compile/XEN3_DOM0 amd64
>
>
>
>
> domU config:
> kernel = "/usr/pkg/xen/kern/vmlinuz-xen-install"
> ramdisk = "/usr/pkg/xen/kern/initrd-xen-install"
> #bootloader = "/usr/pkg/bin/pygrub"
>
> memory = 1024
> name   = "linux-pv"
>
> #vcpus = 4
> vif = [ 'mac=xx:xx:xx:xx:xx:xx, bridge=bridge0' ]
>
> disk = [ 'phy:/dev/mapper/volgroup001-lv0,xvda,w' ]
> #root = "xbd0"
>
> # use to boot to single user (-s), etc
> extra=""
>
>
>
> Not sure if I should post this to current-users instead, let me know
> if that's a better option..

The problem ended up being LVM related, sorry for the noise. I saw these
new messages and jumped to the conclusion.

 I still get the sysctl messages though, while in another dom0 running
5.0.1 I don't. Are they safe to ignore?

[Manuel Bouyer]

On Sun, Nov 08, 2009 at 01:04:52PM +0000, Hugo Silva wrote:
> >Not sure if I should post this to current-users instead, let me know
> >if that's a better option..
>
> The problem ended up being LVM related, sorry for the noise. I saw these
> new messages and jumped to the conclusion.
>
> I still get the sysctl messages though, while in another dom0 running
> 5.0.1 I don't. Are they safe to ignore?

it's probably going to be a problem at some point, but I don't know what's
using these sysctls right  now.

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--