WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] [3.0.3] block-attach does not work

To: "Denny Schierz" <linuxmail@xxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] [3.0.3] block-attach does not work
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Thu, 31 May 2007 17:14:17 +0200
Delivery-date: Thu, 31 May 2007 08:13:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <465EE52C.6090704@xxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acejlf6fRH3Kc5jRTuSzQxxET6BeOAAADJPA
Thread-topic: [Xen-users] [3.0.3] block-attach does not work
 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Denny Schierz
> Sent: 31 May 2007 16:10
> To: 'xen-users@xxxxxxxxxxxxxxxxxxx'
> Subject: [Xen-users] [3.0.3] block-attach does not work
> 
> hi,
> 
> i tried to attach a LVM volume to a running guest:
> 
> xm block-attach vm01 phy:/dev/daten/vm01-daten /dev/sdb1 w
> 
> but in the guest nothing happens.
> 
> rohan:~# xm block-list vm01
> 
> Vdev  BE handle state evt-ch ring-ref BE-path
> 2049    0    0     4      7      9     
> /local/domain/0/backend/vbd/3/2049
> 
> 2050    0    0     4      8      10    
> /local/domain/0/backend/vbd/3/2050
> 
> 2065    0    0     4      10     597   
> /local/domain/0/backend/vbd/3/2065
> 
> 
> the log shows:
> 
> [2007-05-31 17:05:49 xend 2571] DEBUG (__init__:1072) DevController:
> writing {'backend-id': '0', 'virtual-device': '2065', 'device-type':
> 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/3/2065'}
> to /local/domain/3/device/vbd/2065.
> [2007-05-31 17:05:49 xend 2571] DEBUG (__init__:1072) DevController:
> writing {'domain': 'vm01', 'frontend':
> '/local/domain/3/device/vbd/2065', 'dev': '/dev/sdb1', 'state': '1',
> 'params': '/dev/daten/vm01-daten', 'mode': 'w', 'online': '1',
> 'frontend-id': '3', 'type': 'phy'} to 
> /local/domain/0/backend/vbd/3/2065.
> [2007-05-31 17:05:49 xend 2571] DEBUG (__init__:1072) Waiting 
> for 2065.
> [2007-05-31 17:05:49 xend 2571] DEBUG (__init__:1072)
> hotplugStatusCallback 
> /local/domain/0/backend/vbd/3/2065/hotplug-status.
> [2007-05-31 17:05:50 xend 2571] DEBUG (__init__:1072)
> hotplugStatusCallback 
> /local/domain/0/backend/vbd/3/2065/hotplug-status.
> [2007-05-31 17:05:50 xend 2571] DEBUG (__init__:1072)
> hotplugStatusCallback 1.
> 
> The guest and host are both Debian Etch.

If the guest is a HVM guest, then I would expect this behaviour. If it's
a para-virtual guest I expect it to work. 

The reason is that the HVM guest most likely doesn't have a para-virtual
driver that reads the xenstore to realize that there is a new device
there. 

--
Mats
> 
> cu denny
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>