XEN3 DOMU troubles

I've also noticed that in my dmesg output, these lines
appear when I
and create a guest domain and it fails:

xvif3.0: Ethernet address 00:16:3e:01:00:11
vnd0: dos partition I/O error
xbd backend: attach device vnd0d (size 4194306) for domain 3

Anybody know what that "dos partition I/O error"
is?

On 11/4/06, Mike Sun <msunbluespot.org> wrote:
> I'm having similiar issues to what Steve had reported
in his thread
> (http://mail-index.netbsd.org/port-xen/2006/10/08/0004.
html) except
> even after I include "vif = [ 'bridge=bridge0'
]" in my config file, I
> still get the "Error: Device 0 (vif) could not be
connected.  Hotplut
> scripts not working." error.
>
> brconfig -a shows the bridge0 interface is up and
running:
> bridge0: flags=41<UP,RUNNING>
>             Configuration:
>                         priority 32768 hellotime 2
fwddelay 15 maxage 20
>                         ipfilter disabled flags 0x0
>             Interfaces:
>                         ex0
flags=3<LEARNING,DISCOVER>
>                                     port 1 priority 128
>             Address cache (max cache: 100, timeout:
1200):
>                          00:0a:95:d6:1c:8a ex0
4294967143 flags=0<>
>
> Here is my guest domain file contents:
> name = "nbsdu"
> kernel =
"/home/msun/netbsd-INSTALL_XEN3_DOMU"
> memory = 96
> vif = [ 'bridge=bridge0' ]
> disk = [ 'file:/home/msun/nbsd-disk,0x01,w' ]
> root = "/dev/wd0a"
>
> I'm running off the binaries from
"NetBSD-daily/HEAD/200610250000Z/",
> anybody have any ideas what's going on?
>
> Thanks,
> Mike

On Sat, Nov 04, 2006 at 11:52:03PM -0500, Mike Sun wrote:
> I've also noticed that in my dmesg output, these lines
appear when I
> and create a guest domain and it fails:
> 
> xvif3.0: Ethernet address 00:16:3e:01:00:11
> vnd0: dos partition I/O error
> xbd backend: attach device vnd0d (size 4194306) for
domain 3
> 
> Anybody know what that "dos partition I/O
error" is?

It's because the kernel tries to read a i386-style DOS
partitition table,
and a disklabel and can't find them on a virgin disklabel.
This should not
be an issue. Hum, this message could also be because the
file is sparse;
make sure your file doesn't have holes (if you created it
with dd,
it should not be the case).

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--