Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Is NetBSD domain0 ready for production server?
On Wed, Mar 30, 2005 at 10:05:27AM +0300, Martti Kuparinen wrote:
> >>[...]
> >># xm create -c /xen/conf/linux1
> >>Using config file "/xen/conf/linux1".
> >>Error: Adding extent to vbd failed: device (vbd (uname phys:/dev/wd0e)
> >>(dev sda1) (mode w)), error 8
> >>
> >>From the logs:
> >>
> >>xen.xend.XendError.XendError: Adding extent to vbd failed: device (vbd
> >>(uname phys:/dev/wd0f) (dev sda2) (mode w)), error 8
> >>/etc/xen/scripts/: not found
> >>/etc/xen/scripts/: not found
> >
> >
> >Does the kernel write something on console or dmesg ?
>
> xvif1.0: Ethernet address aa:00:00:4a:0c:48
> xbdback VBD grow domain 1: unknwon device 0x44e98
> xbdback VBD grow domain 1: unknwon device 0x44e98
This looks completely wrong, the device should be 0x0405 for /dev/wd0f.
It's not even a sign extention bug or an uninitalised field, is't completely
different.
What version of the xen kernel and the tools do you have ?
Can you try to ktrace xm and xend to see what it's doing with /dev/wd0f ?
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index