NetBSD Problem Report #29856
From juan@xtraeme.nopcode.org Fri Apr 1 10:01:11 2005
Return-Path: <juan@xtraeme.nopcode.org>
Received: from xtraeme.nopcode.org (91.Red-80-32-6.pooles.rima-tde.net [80.32.6.91])
by narn.netbsd.org (Postfix) with ESMTP id 0646663B11A
for <gnats-bugs@gnats.NetBSD.org>; Fri, 1 Apr 2005 10:01:10 +0000 (UTC)
Message-Id: <20050401100059.F36895994@xtraeme.nopcode.org>
Date: Fri, 1 Apr 2005 12:00:59 +0200 (CEST)
From: juan@xtraeme.nopcode.org
Reply-To: juan@xtraeme.nopcode.org
To: gnats-bugs@netbsd.org
Subject: Cannot add vnd files in domU when it's already running
X-Send-Pr-Version: 3.95
>Number: 29856
>Category: port-xen
>Synopsis: Cannot add vnd files in domU when it's already running
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bouyer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Apr 01 10:02:00 +0000 2005
>Closed-Date: Wed Apr 20 18:26:23 +0000 2005
>Last-Modified: Wed Apr 20 18:26:23 +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
domU:
XenU# disklabel xbd1d
disklabel: Can't read master boot record 0: Input/output error
# /dev/rxbd1d:
type: ESDI
disk: Xen Virtual ESDI
label: default label
flags:
bytes/sector: 512
sectors/track: 2048
tracks/cylinder: 1
l. 0 - 781*)
d: 1600000 0 4.2BSD 0 0 0 # (Cyl. 0 - 781*)
disklabel: boot block size 0
disklabel: super block size 0
disklabel: partitions a and d overlap
XenU#
You cannot disklabel or newfs it, when the vnd files
are specified in the config file and they are started
at boot time, it works.
>How-To-Repeat:
See above.
>Fix:
As a workaround, specify the vnd files when the domU
is created (at boot time), that way works.
>Release-Note:
>Audit-Trail:
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
--
From: Juan RP <juan@xtraeme.nopcode.org>
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-xen/29856: Cannot add vnd files in domU when it's already
running
Date: Wed, 6 Apr 2005 18:52:14 +0200
On Fri, 1 Apr 2005 18:35:18 +0200
Manuel Bouyer <bouyer@antioche.lip6.fr> 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?
Thanks.
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
--
Responsible-Changed-From-To: port-xen-maintainer->bouyer
Responsible-Changed-By: bouyer@netbsd.org
Responsible-Changed-When: Sun, 17 Apr 2005 23:00:53 +0000
Responsible-Changed-Why:
I commited support for dynamic attach/detach to xbd.
State-Changed-From-To: open->feedback
State-Changed-By: bouyer@netbsd.org
State-Changed-When: Sun, 17 Apr 2005 23:00:53 +0000
State-Changed-Why:
Hi,
Can you try the latest current ? I just commited code that makes dynamic
attach/detach work in xbd.
From: Juan RP <juan@xtrarom.org>
To: gnats-bugs@netbsd.org
Cc: bouyer@netbsd.org
Subject: Re: port-xen/29856: Cannot add vnd files in domU when it's already
Date: Wed, 20 Apr 2005 07:17:41 +0200
I just tried to attach another xbd, and it worked fine, this PR can be
closed now, thanks for your work.
State-Changed-From-To: feedback->closed
State-Changed-By: bouyer@netbsd.org
State-Changed-When: Wed, 20 Apr 2005 18:26:23 +0000
State-Changed-Why:
Juan confirmed that the problem is fixed.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.