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/
Home Products Support Community News


[Xen-users] block-attach on dom0 missing

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] block-attach on dom0 missing
From: Tanuj Bansal <bansal.tanuj83@xxxxxxxxx>
Date: Fri, 18 Dec 2009 12:33:37 +0530
Delivery-date: Thu, 17 Dec 2009 23:04:29 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=PkQnBN59dqbwB1KdVys9nCFewA4j3dxJ5MEsv6JeFsU=; b=KFwvBu6WQKXepVq8+8I/YLHogEMfSQEe69N4t10aLV9Tg+iQeUFaFZc2rrjVPZpG3N m0G1Ui/k98oALLpDgUkBsLzsyRjUP9P2IN5OUgcQwPXiwnAqJpo0eVF1gcN35AxGj/yN 59Do822o+OfhDcc8Fk9/5AygC4XD9i7XZA2k8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PYvwAn7jP8AHO4ndI52uTknfcRpwulRwXTN+PnRx/n3D1OKdxlndNNcNRXSg6KdVGq AqGdePgSr5dY88DsPc2NgAu0ZA1FMyOcd5OHusIb0VGPyBkKlmeeATw6xH1pOlHZcYW8 0jZKFwbt1Pncs03F5OSsr9ZowtVRU11KYYSNM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have one domU using the disk file tanuj.dsk

[root@tanuj-xen-new virtual]# cat /etc/xen/tanuj
name = "tanuj"
uuid = "3d9ab75d-e08f-bac9-b56c-1cd6a43d1e35"
maxmem = 300
memory = 300
vcpus = 4
bootloader = "/usr/bin/pygrub"
>>>vfb = [  ]
disk = [ "tap:aio:/virtual/tanuj.dsk,xvda,w", "phy:/dev/sda11,xvdb,w" ]
vif = [ "mac=00:16:3e:32:e9:5f,bridge=xenbr0" ]
[root@tanuj-xen-new virtual]#                       

and this domU has disk /dev/xvda1 mounted at /boot

[root@tanuj ~]# df -h /boot
Filesystem            Size  Used Avail Use% Mounted on
/dev/xvda1             99M   13M   81M  14% /boot
[root@tanuj ~]#                                       

now I am trying to attach that /dev/xvda1 on my dom0

#  xm block-attach 0 tanuj.dsk /dev/xvda1 w 0

Now I can see the attached device in xm list --long

[root@tanuj-xen-new virtual]# xm list --long
    (domid 0)
    (uuid 00000000-0000-0000-0000-000000000000)
    (vcpus 4)
    (cpu_weight 1.0)
    (memory 1594)
    (shadow_memory 0)
    (maxmem 1776)
    (features )
    (name Domain-0)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
    (device (vbd (backend 0) (dev /dev/xvda1:disk) (mode w)))
    (state r-----)
    (shutdown_reason poweroff)
    (cpu_time 509.951158471)
    (online_vcpus 4)
    (domid 2)
    (uuid 3d9ab75d-e08f-bac9-b56c-1cd6a43d1e35)
    (vcpus 4)
    (cpu_weight 1.0)
    (memory 300)
    (shadow_memory 0)
    (maxmem 300)
    (bootloader /usr/bin/pygrub)
    (features )
    (name tanuj)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
            (ramdisk /var/lib/xen/boot_ramdisk.X6ua5E)
            (kernel /var/lib/xen/boot_kernel.5FFIR6)
            (args 'ro root=/dev/VolGroup00/LogVol00 console=xvc0 rhgb quiet')
            (backend 0)
            (script vif-bridge)
            (bridge xenbr0)
            (mac 00:16:3e:32:e9:5f)
    (device (vbd (backend 0) (dev xvdb:disk) (uname phy:/dev/sda11) (mode w)))
            (backend 0)
            (dev xvda:disk)
            (uname tap:aio:/virtual/tanuj.dsk)
            (mode w)
    (state -b----)
    (shutdown_reason poweroff)
    (cpu_time 29.647193284)
    (online_vcpus 4)
    (up_time 83.3499569893)
    (start_time 1261119399.57)
    (store_mfn 191144)
    (console_mfn 191143)
[root@tanuj-xen-new virtual]#         

and in block-list too

[root@tanuj-xen-new virtual]# xm block-list 0 --long
    ((backend-id 0)
        (virtual-device 51713)
        (device-type disk)
        (state 1)
        (backend /local/domain/0/backend/vbd/0/51713)
[root@tanuj-xen-new virtual]#          

But I am not able to locate that disk /dev/xvda1 on my dom0 and how can i mount it even if my domU is down

I know that the /dev/xvda1 data can be taken by using losetup and kpartx but need to know about this


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>