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

From: Manuel Bouyer <bouyer@antioche.lip6.fr>
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: Fri, 1 Apr 2005 18:35:18 +0200

 On Fri, Apr 01, 2005 at 10:02:00AM +0000, juan@xtraeme.nopcode.org wrote:
 > >Number:         29856
 > >Category:       port-xen
 > >Synopsis:       Cannot add vnd files in domU when it's already running
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    port-xen-maintainer
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Fri Apr 01 10:02:00 +0000 2005
 > >Originator:     Juan RP
 > >Release:        NetBSD 3.99.2
 > >Organization:
 > >Environment:
 > System: NetBSD Mandylion 3.99.2 NetBSD 3.99.2 (GATEWAY_) #1: Thu Mar 31 18:41:13 CEST 2005 juan@Nocturno:/home/juan/build/obj/sys/arch/i386/compile/GATEWAY_ i386
 > Architecture: i386
 > Machine: i386
 > >Description:
 > 
 > 	When there's a domU running, you might want to add
 > 	another vbd device, but it doesn't work:
 > 
 > 	dom0:
 > 
 > 	$ 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.
 
 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --