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-devel

Re: [Xen-devel] Problems with virtual disks in DomU

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Problems with virtual disks in DomU
From: Stephen Childs <Stephen.Childs@xxxxxxxxx>
Date: Wed, 25 Aug 2004 15:28:12 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 25 Aug 2004 15:46:40 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1Bzx0E-0005fJ-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1Bzx0E-0005fJ-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803

>>If I export /dev/sdb to domain U as /dev/sdb read-write (i.e. disk = [
>>'phy:sdb,sdb,w' ]), then DomU doesn't seem to see the disk at all; I get the
>>following error:
>>
>>Initialising Xen virtual block device
>>Partition check:
>>  sdb:<6>Timeout connecting block device driver!

Having enabled some more debugging I get:

Partition check:
 sdb:<1>Entered do_blkif_request
do_blkif_request c11ac980: cmd 0, sec 0, (2/8) bh:c11a91e0
Timeout connecting block device driver!

> This suggests that xend hasn't created the appropriate object for
> configuring your block device.
>
> Seeing the messages coming out of xend would be very interesting,
> as would enabling the debug flags in blkback/common.h (messages
> will come out on the dom 0 console; you can capture them with
> 'dmesg')

debug info:

(file=control.c, line=13) Received blkif backend message, subtype=0
(file=interface.c, line=107) Successfully created blkif
(file=control.c, line=13) Received blkif backend message, subtype=4
(file=vbd.c, line=74) Successful creation of vdev=0810 (dom=1)
(file=control.c, line=13) Received blkif backend message, subtype=6
(file=vbd.c, line=190) vbd_grow: requested_len 286749480 actual_len 286749480
(file=vbd.c, line=198) Successful grow of vdev=0810 (dom=1)
device vif1.0 entered promiscuous mode
(file=control.c, line=13) Received blkif backend message, subtype=2


xend o/p:

Using config file "/root/xen/xen2_domain_config".
config: (vm (name Xen1) (memory 64) (image (linux (kernel /boot/vmlinuz-2.4.27-xenU) (ip 192.168.0.144:1.2.3.4:192.168.0.254:::eth0:) (root '/dev/sdb1 ro') (args ' 4'))) (device (vbd (uname phy:sdb) (dev sdb) (mode w))) (device (vif (mac aa:00:00:75:fa:ba)))) [xend] DEBUG (XendDomainInfo:726) init_domain> Created domain=2 name=Xen1 memory=64
[xend] INFO (console:93) Created console id=12 domain=2 port=9602
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c02cc24c
 Init. ramdisk: c02cd000->c02cd000
 Phys-Mach map: c02cd000->c02dd000
 Page tables:   c02dd000->c02df000
 Start info:    c02df000->c02e0000
 Boot stack:    c02e0000->c02e1000
 TOTAL:         c0000000->c0400000
 ENTRY ADDRESS: c0100000
[xend] DEBUG (blkif:52) Connecting blkif <BlkifBackendController 2 0>
CtrlMsgRcvr>writeRequest> message: type= blkif_be_create_t 1:0 id=15
payload= {'status': 1852731203, 'blkif_handle': 0, 'domid': 2}
EVENT> xend.console.create [12, 2, 9602]
responseReceived> message: type= blkif_be_create_t 1:0 id=15
payload= {'status': 0, 'blkif_handle': 0, 'domid': 2}
respond_be_create> {'status': 0, 'blkif_handle': 0, 'domid': 2}
[xend] DEBUG (XendDomainInfo:1083) Creating vbd dom=2 uname=phy:sdb dev=sdb
[xend] DEBUG (blkif:52) Connecting blkif <BlkifBackendController 2 0>
CtrlMsgRcvr>writeRequest> message: type= blkif_be_vbd_create_t 1:4 id=16
payload= {'status': 1734831948, 'blkif_handle': 0, 'readonly': 0, 'vdevice': 2064, 'domid': 2} [xend] DEBUG (XendDomainInfo:1057) Creating vif dom=2 vif=0 mac=aa:00:00:75:fa:ba
attach>
CtrlMsgRcvr>writeRequest> message: type= netif_be_create_t 3:0 id=17
payload= {'status': 32, 'netif_handle': 0, 'domid': 2}
responseReceived> message: type= blkif_be_vbd_create_t 1:4 id=16
payload= {'status': 0, 'blkif_handle': 0, 'readonly': 0, 'vdevice': 2064, 'domid': 2}
CtrlMsgRcvr>writeRequest> message: type= blkif_be_vbd_grow_t 1:6 id=18
payload= {'status': 544173600, 'blkif_handle': 0, 'extent.device': 2064, 'extent.sector_start': 0L, 'vdevice': 2064, 'domid': 2, 'extent.sector_length': 9223372036854775808L}
responseReceived> message: type= netif_be_create_t 3:0 id=17
payload= {'status': 0, 'netif_handle': 0, 'domid': 2}
respond_be_create> {'status': 0, 'netif_handle': 0, 'domid': 2}
vif-bridge up vif=vif2.0 domain=Xen1 mac=aa:00:00:75:fa:ba bridge=xen-br0
responseReceived> message: type= blkif_be_vbd_grow_t 1:6 id=18
payload= {'status': 0, 'blkif_handle': 0, 'extent.device': 2064, 'extent.sector_start': 0L, 'vdevice': 2064, 'domid': 2, 'extent.sector_length': 9223372036854775808L}
EVENT> xend.domain.created ['Xen1', '2']
EVENT> xend.domain.unpause ['Xen1', '2']
Started domain Xen1, console on port 9602
requestReceived> message: type= blkif_fe_driver_status_changed_t 2:32 id=255
payload= {'status': 1}
recv_fe_driver_status_changed> {'status': 1}
CtrlMsgRcvr>writeRequest> message: type= blkif_fe_interface_status_changed_t 2:0 id=19
payload= {'status': 1, 'handle': 0, 'evtchn': 0}
responseReceived> message: type= blkif_fe_interface_status_changed_t 2:0 id=19
payload= {'status': 1, 'handle': 0, 'evtchn': 0}
responseReceived> No handler: Message type blkif_fe_interface_status_changed_t 2:0 <xen.xend.server.blkif.BlkifController instance at 0x84def3c>
requestReceived> message: type= blkif_fe_interface_connect_t 2:33 id=255
payload= {'shmem_frame': 61677, 'handle': 0}
[xend] DEBUG (blkif:100) Connecting blkif to event channel <BlkifBackendController 2 0> ports=14:4
CtrlMsgRcvr>writeRequest> message: type= blkif_be_connect_t 1:2 id=20
payload= {'status': 1851880563, 'blkif_handle': 0, 'evtchn': 14, 'domid': 2, 'shmem_frame': 61677}
responseReceived> message: type= blkif_be_connect_t 1:2 id=20
payload= {'status': 0, 'blkif_handle': 0, 'evtchn': 14, 'domid': 2, 'shmem_frame': 61677} respond_be_connect> <BlkifBackendController 2 0> {'status': 0, 'blkif_handle': 0, 'evtchn': 14, 'domid': 2, 'shmem_frame': 61677} CtrlMsgRcvr>writeRequest> message: type= blkif_fe_interface_status_changed_t 2:0 id=21
payload= {'status': 2, 'handle': 0, 'evtchn': 4}
[xend] INFO (console:42) Console connected 12 127.0.0.1 1044
EVENT> xend.console.connect [12, '127.0.0.1', 1044]
requestReceived> message: type= netif_fe_driver_status_changed_t 4:32 id=255
payload= {'status': 1, 'nr_interfaces': 0}
CtrlMsgRcvr>writeRequest> message: type= netif_fe_driver_status_changed_t 4:32 id=22
payload= {'status': 1, 'nr_interfaces': 1}
CtrlMsgRcvr>writeRequest> message: type= netif_fe_interface_status_changed_t 4:0 id=23 payload= {'status': 1, 'mac[1]': 0, 'mac[0]': 170, 'handle': 0, 'mac[2]': 0, 'mac[3]': 117, 'mac[5]': 186, 'evtchn': 0, 'mac[4]': 250}

> Also, at the point where it's failed trying to fsck, trying doing
> an '/sbin/sfdisk -s /dev/sdb1'.

It seems to report the correct size for the partition.

Stephen



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel