The following reply was made to PR port-xen/29856; it has been noted by GNATS.

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: port-xen-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org
Subject: Re: port-xen/29856: Cannot add vnd files in domU when it's already running
Date: Wed, 6 Apr 2005 21:21:23 +0200

 On Wed, Apr 06, 2005 at 04:53:02PM +0000, Juan RP wrote:
 >  > > 	$ xm create /etc/xen/foo 
 >  > > 	$ dd if=/dev/zero of=mydisk.img count=512 bs=1m
 >  > > 	$ vnconfig vnd0 mydisk.img
 >  > > 	$ xm vbd-create nbsd1 phy:/dev/vnd0a wd1d w
 >  > 
 >  > You should use vnd0d, not vnd0a. Either use the raw partition, or a
 >  > partition not starting at offset 0. The first sectors of the vnd device are
 >  > read-only for normal partitions, to protect the disklabel.
 >  
 >  I tried with vnd0d, it failed. Which are the required steps to add a new vbd
 >  disk?
 
 Hum, it looks like it doesn't work as expected. It's properly created on
 the domain0 side, but the guest doesn't detect it. I suspect it's a problem
 in the xbd frontend.
 I have another PR to handle, which may help fixing this.
 
 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --