Problems with virtual disks in DomU

Problems with virtual disks in DomU

[Stephen Childs]

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

Hi,

I am trying to move from Xen 1.2 to the latest revision of Xen and I'm 
having problems accessing virtual block devices from DomU. The machine is a 
Dell PowerEdge 1750 (I had to compile Fusion MPT support into Dom0, but it 
all seems to work fine now).

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!

If I export the root and swap partitions explicitly (i.e. /dev/sdb1 and 
/dev/sdb3) then things get a bit further but then fsck of the root 
filesystem fails. (The filesystem is a RH7.2 image which fscks and mounts 
fine in Dom0).

I have attached my domain config file and the bootlogs for both cases. I 
have trawled through the docs and the list archive but can't seem to find 
anything relevant. It's quite likely that I'm missing something about the 
transition to Xen 2.0 but I can't quite see what!

Stephen

-- 
Dr. Stephen Childs,
Researcher, EGEE Project,         phone:                    +353-1-6081720
Computer Architecture Group,      email:       Stephen.Childs at cs.tcd.ie
Trinity College Dublin, Ireland   web: http://www.cs.tcd.ie/Stephen.Childs

[-- Attachment #2: bootlog_with_partitions --]
[-- Type: text/plain, Size: 3635 bytes --]

Linux version 2.4.27-xenU (childss@frascati.cs.tcd.ie) (gcc version 3.3.3 200404
12 (Red Hat Linux 3.3.3-7)) #1 Wed Aug 25 11:13:40 IST 2004
On node 0 totalpages: 16384
zone(0): 4096 pages.
zone(1): 12288 pages.
zone(2): 0 pages.
Kernel command line:  ip=192.168.0.144:1.2.3.4:192.168.0.254:::eth0: root=/dev/s
db1 ro  4
Initializing CPU#0
Xen reported: 2387.144 MHz processor.
Calibrating delay loop... 2510.02 BogoMIPS
Memory: 62840k/65536k available (1304k kernel code, 2696k reserved, 234k data, 5
6k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
CPU: L1 I cache: 12K, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Intel(R) Xeon(TM) CPU 2.40GHz stepping 09
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Event-channel device installed.
Xen virtual console successfully installed as tty
Starting Xen Balloon driver
pty: 256 Unix98 ptys configured
Initialising Xen virtual block device
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Initialising Xen virtual ethernet frontend driver.
Netfront recovered tx=0 rxfree=0
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.0.144, mask=255.255.255.0, gw=192.168.0.254,
     host=192.168.0.144, domain=, nis-domain=(none),
     bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath=
ip_conntrack version 2.1 (512 buckets, 4096 max) - 288 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 56k freed
modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.27-xenU/module
s.dep (No such file or directory)
INIT: version 2.78 booting
                        Welcome to Red Hat Linux
                Press 'I' to enter interactive startup.
Mounting proc filesystem:  [  OK  ]
Configuring kernel parameters:  [  OK  ]
Setting clock : Wed Aug 25 07:31:19 EDT 2004 [  OK  ]
Activating swap partitions:  [  OK  ]
Setting hostname redhat72.goober.org:  [  OK  ]
modprobe: Can't open dependencies file /lib/modules/2.4.27-xenU/modules.dep (No 
such file or directory)
Checking root filesystem
fsck.ext2/: 
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

[/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a / 
: Is a directory while trying to open /
[FAILED]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup): 


[-- Attachment #3: bootlog_with_wholedisk --]
[-- Type: text/plain, Size: 2204 bytes --]

Linux version 2.4.27-xenU (childss@frascati.cs.tcd.ie) (gcc version 3.3.3 200404
12 (Red Hat Linux 3.3.3-7)) #1 Wed Aug 25 11:13:40 IST 2004
On node 0 totalpages: 16384
zone(0): 4096 pages.
zone(1): 12288 pages.
zone(2): 0 pages.
Kernel command line:  ip=192.168.0.144:1.2.3.4:192.168.0.254:::eth0: root=/dev/s
db1 ro  4
Initializing CPU#0
Xen reported: 2387.144 MHz processor.
Calibrating delay loop... 4757.91 BogoMIPS
Memory: 62840k/65536k available (1304k kernel code, 2696k reserved, 234k data, 5
6k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
CPU: L1 I cache: 12K, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Intel(R) Xeon(TM) CPU 2.40GHz stepping 09
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Event-channel device installed.
Xen virtual console successfully installed as tty
Starting Xen Balloon driver
pty: 256 Unix98 ptys configured
Initialising Xen virtual block device
Partition check:
 sdb:<6>Timeout connecting block device driver!
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Initialising Xen virtual ethernet frontend driver.
[XEN] Failed to connect all virtual interfaces: err=-100
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
IP-Config: Device `eth0' not found.
ip_conntrack version 2.1 (512 buckets, 4096 max) - 288 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.


[-- Attachment #4: xen2_domain_config --]
[-- Type: text/plain, Size: 399 bytes --]

# Kernel image file.
kernel = "/boot/vmlinuz-2.4.27-xenU"

# Initial memory allocation (in megabytes) for the new domain.
memory = 64

dhcp=""
ip="192.168.0.144"
gateway="192.168.0.254"

# A name for your domain. All domains must have different names.
name = "Xen1"

disk = [ 'phy:sdb,sdb,w' ]
#disk = [ 'phy:sdb1,sdb1,w', 'phy:sdb3,sdb3,w' ]

# Set root device.
root = "/dev/sdb1 ro"
extra = " 4"

Re: Problems with virtual disks in DomU

[Ian Pratt]

> I am trying to move from Xen 1.2 to the latest revision of Xen and I'm 
> having problems accessing virtual block devices from DomU. The machine is a 
> Dell PowerEdge 1750 (I had to compile Fusion MPT support into Dom0, but it 
> all seems to work fine now).
> 
> 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!

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')

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

Ian


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

Re: Problems with virtual disks in DomU

[Stephen Childs]

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

Re: Problems with virtual disks in DomU

[Ian Pratt]

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

This all looks fine: the blkback driver seems happy with
exporting sdb.


> 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!
 
The very first message that the blkfront driver sends to blkback
is a probe to find out what devices it has. 

It doesn't seem to be getting any response, which is very odd
indeed. 

Are you using an up to date repository? Are you 100% sure that
the version of the tools, xen and kernels are all built from this
repository?

Can you try exporting sda (or sda1) readonly and see if that
works? (I can't think why there'd be a problem with sdb, but I
haven't got a system I can easily test this on.)

The next thing to do would be to add some tracing to the
interrupt handler in blkback to see if you ever see the request
from blkfront. 

Ian



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

Re: Problems with virtual disks in DomU

[Mark Williamson]

You could try booting your Xen1 domain using dom0's kernel - that should 
eliminate the problem of kernel build inconsistencies, at least.

Cheers,
Mark



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

Re: Problems with virtual disks in DomU

[Stephen Childs]

Mark Williamson wrote:
> You could try booting your Xen1 domain using dom0's kernel - that should 
> eliminate the problem of kernel build inconsistencies, at least.

I have tried that already. Also have tried deleting everything Xen-related I 
could find and doing a complete update/rebuild. I have tried using sda 
instead of sdb, and also exporting it as hda. And also with 2.6.7 for good 
measure. I seem to get the same result whatever I do. I will try and stick 
in some more debug code tomorrow.

Stephen

-- 
Dr. Stephen Childs,
Researcher, EGEE Project,         phone:                    +353-1-6081720
Computer Architecture Group,      email:        Stephen.Childs @ cs.tcd.ie
Trinity College Dublin, Ireland   web: http://www.cs.tcd.ie/Stephen.Childs


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

Re: Problems with virtual disks in DomU

[Mark Williamson]

:-(((  Doesn't sound like fun.  Thanks for trying those things, tho - more 
information at least narrows things down.

The frontend driver should wait up to 10 seconds before timing out - can you 
confirm that it is waiting that long?

Cheers,
Mark



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

Re: Problems with virtual disks in DomU

[Stephen Childs]

Mark Williamson wrote:
> :-(((  Doesn't sound like fun.  Thanks for trying those things, tho - more 
> information at least narrows things down.
> 
> The frontend driver should wait up to 10 seconds before timing out - can you 
> confirm that it is waiting that long?

Yes it does wait for 10 seconds.

I have now also tried running it on my desktop machine (which has IDE disks) 
with the same results and have also tried running last night's build from 
Cambridge -- also with the same results. I'm beginning to think I'm missing 
something obvious!

Any ideas why there are different results exporting sdb and sdb1? Is it 
something to do with the probe?

Here's some more debug output from xen0 console:

(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
(file=main.c, line=296) do_block_io_op: got probe request
(file=main.c, line=334) dispatch_probe: calling vbd_probe
(file=main.c, line=337) dispatch_probe: vbd_probe returned 1
(file=main.c, line=340) dispatch_probe: making response
(file=main.c, line=541) make_response: calling wmb
(file=main.c, line=547) make_response: notifying domain



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

Re: Problems with virtual disks in DomU

[Ian Pratt]

> I have now also tried running it on my desktop machine (which has IDE disks) 
> with the same results and have also tried running last night's build from 
> Cambridge -- also with the same results. I'm beginning to think I'm missing 
> something obvious!

This is truly bizarre. Are you sure you're re-installing (and
restarting) xend when you upgrade? I could imagine that an old
xend version might conceivably have this effect.

Have you tried doing a 'make uninstall' to clear out old
versions. (This script is actually *really* dumb, so read what it
does and modify appropriately --- copy back your config files
when you're done.)

> Any ideas why there are different results exporting sdb and sdb1? Is it 
> something to do with the probe?

I'd certainly stick to using sdb1 as exporting whole disks is
probably used by far fewer people (but certainly believed to
work). I'd also try having the target device as 'sda1' or 'hda1'
as this is more normal than using sdb1. e.g.

  disk = [ 'phy:sdb1,sda1,w' ]


Ian


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

Re: Problems with virtual disks in DomU

[Mark Williamson]

Could you send the Xend output from the separate partitions case (i.e. when 
the connection works).

We've certainly not seen this anywhere else but we'll work to help you fix 
it...  Making sure you obliterate all the installed Xen unstable libraries, 
etc.

HTH,
Mark



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

Re: Problems with virtual disks in DomU

[Stephen Childs]

Mark Williamson wrote:
> Could you send the Xend output from the separate partitions case (i.e. when 
> the connection works).

This is for [phys:sdb1,sda1,w] --

domU bootlog

fsck.ext2/:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
     e2fsck -b 8193 <device>

[/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a /
: Is a directory while trying to open /
[FAILED]


xend output


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/sda1 ro') 
(args ' 4'
))) (device (vbd (uname phy:sdb1) (dev sda1) (mode w))) (device (vif (mac 
aa:00:00:
67:48:81))))
[xend] DEBUG (XendDomainInfo:726) init_domain> Created domain=8 name=Xen1 
memory=64
[xend] INFO (console:93) Created console id=12 domain=8 port=9608
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 8 0>
CtrlMsgRcvr>writeRequest> message: type= blkif_be_create_t 1:0 id=172
payload= {'status': 1953460050, 'blkif_handle': 0, 'domid': 8}
EVENT> xend.console.create [12, 8, 9608]
responseReceived> message: type= blkif_be_create_t 1:0 id=172
payload= {'status': 0, 'blkif_handle': 0, 'domid': 8}
respond_be_create> {'status': 0, 'blkif_handle': 0, 'domid': 8}
[xend] DEBUG (XendDomainInfo:1083) Creating vbd dom=8 uname=phy:sdb1 dev=sda1
[xend] DEBUG (blkif:52) Connecting blkif <BlkifBackendController 8 0>
CtrlMsgRcvr>writeRequest> message: type= blkif_be_vbd_create_t 1:4 id=173
payload= {'status': 1702130785, 'blkif_handle': 0, 'readonly': 0, 'vdevice': 
2049,
'domid': 8}
[xend] DEBUG (XendDomainInfo:1057) Creating vif dom=8 vif=0 
mac=aa:00:00:67:48:81
attach>
CtrlMsgRcvr>writeRequest> message: type= netif_be_create_t 3:0 id=174
payload= {'status': 1852383346, 'netif_handle': 0, 'domid': 8}
responseReceived> message: type= blkif_be_vbd_create_t 1:4 id=173
payload= {'status': 0, 'blkif_handle': 0, 'readonly': 0, 'vdevice': 2049, 
'domid':
8}
CtrlMsgRcvr>writeRequest> message: type= blkif_be_vbd_grow_t 1:6 id=175
payload= {'status': 544173600, 'blkif_handle': 0, 'extent.device': 2065, 
'extent.se
ctor_start': 0L, 'vdevice': 2049, 'domid': 8, 'extent.sector_length': 
9223372036854
775808L}
responseReceived> message: type= netif_be_create_t 3:0 id=174
payload= {'status': 0, 'netif_handle': 0, 'domid': 8}
respond_be_create> {'status': 0, 'netif_handle': 0, 'domid': 8}
sh: /etc/xen/scripts/vif-bridge: No such file or directory
responseReceived> message: type= blkif_be_vbd_grow_t 1:6 id=175
payload= {'status': 0, 'blkif_handle': 0, 'extent.device': 2065, 
'extent.sector_sta
rt': 0L, 'vdevice': 2049, 'domid': 8, 'extent.sector_length': 
9223372036854775808L}
EVENT> xend.domain.created ['Xen1', '8']
EVENT> xend.domain.unpause ['Xen1', '8']
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
=176
payload= {'status': 1, 'handle': 0, 'evtchn': 0}
requestReceived> message: type= blkif_fe_interface_connect_t 2:33 id=255
payload= {'shmem_frame': 96481, 'handle': 0}
[xend] DEBUG (blkif:100) Connecting blkif to event channel 
<BlkifBackendController
8 0> ports=32:4
CtrlMsgRcvr>writeRequest> message: type= blkif_be_connect_t 1:2 id=177
payload= {'status': 1635021678, 'blkif_handle': 0, 'evtchn': 32, 'domid': 8, 
'shmem
_frame': 96481}
responseReceived> message: type= blkif_fe_interface_status_changed_t 2:0 id=176
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 0x8505a3c>
responseReceived> message: type= blkif_be_connect_t 1:2 id=177
payload= {'status': 0, 'blkif_handle': 0, 'evtchn': 32, 'domid': 8, 
'shmem_frame':
96481}
respond_be_connect> <BlkifBackendController 8 0> {'status': 0, 
'blkif_handle': 0, '
evtchn': 32, 'domid': 8, 'shmem_frame': 96481}
CtrlMsgRcvr>writeRequest> message: type= blkif_fe_interface_status_changed_t 
2:0 id
=178
payload= {'status': 2, 'handle': 0, 'evtchn': 4}
responseReceived> message: type= blkif_fe_interface_status_changed_t 2:0 id=178
payload= {'status': 2, 'handle': 0, 'evtchn': 4}
responseReceived> No handler: Message type 
blkif_fe_interface_status_changed_t 2:0
<xen.xend.server.blkif.BlkifController instance at 0x8505a3c>
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=1
79
payload= {'status': 1, 'nr_interfaces': 1}
CtrlMsgRcvr>writeRequest> message: type= netif_fe_interface_status_changed_t 
4:0 id
=180
payload= {'status': 1, 'mac[1]': 0, 'mac[0]': 170, 'handle': 0, 'mac[2]': 0, 
'mac[3
]': 103, 'mac[5]': 129, 'evtchn': 0, 'mac[4]': 72}
requestReceived> message: type= netif_fe_interface_connect_t 4:33 id=255
payload= {'tx_shmem_frame': 62401, 'rx_shmem_frame': 62402, 'handle': 0}
CtrlMsgRcvr>writeRequest> message: type= netif_be_connect_t 3:2 id=181
payload= {'status': -1071870768, 'tx_shmem_frame': 62401, 'netif_handle': 0, 
'evtch
n': 33, 'rx_shmem_frame': 62402, 'domid': 8}
responseReceived> message: type= netif_fe_driver_status_changed_t 4:32 id=179
payload= {'status': 1, 'nr_interfaces': 1}
responseReceived> message: type= netif_fe_interface_status_changed_t 4:0 id=180
payload= {'status': 1, 'mac[1]': 0, 'mac[0]': 170, 'handle': 0, 'mac[2]': 0, 
'mac[3
]': 103, 'mac[5]': 129, 'evtchn': 0, 'mac[4]': 72}
responseReceived> No handler: Message type 
netif_fe_interface_status_changed_t 4:0
<xen.xend.server.netif.NetifController instance at 0x8505b64>
responseReceived> message: type= netif_be_connect_t 3:2 id=181
payload= {'status': 0, 'tx_shmem_frame': 62401, 'netif_handle': 0, 'evtchn': 
33, 'r
x_shmem_frame': 62402, 'domid': 8}
CtrlMsgRcvr>writeRequest> message: type= netif_fe_interface_status_changed_t 
4:0 id
=182
payload= {'status': 2, 'mac[1]': 0, 'mac[0]': 170, 'handle': 0, 'mac[2]': 0, 
'mac[3
]': 103, 'mac[5]': 129, 'evtchn': 5, 'mac[4]': 72}
responseReceived> message: type= netif_fe_interface_status_changed_t 4:0 id=182
payload= {'status': 2, 'mac[1]': 0, 'mac[0]': 170, 'handle': 0, 'mac[2]': 0, 
'mac[3
]': 103, 'mac[5]': 129, 'evtchn': 5, 'mac[4]': 72}
responseReceived> No handler: Message type 
netif_fe_interface_status_changed_t 4:0
<xen.xend.server.netif.NetifController instance at 0x8505b64>
[xend] INFO (console:42) Console connected 12 127.0.0.1 1093
EVENT> xend.console.connect [12, '127.0.0.1', 1093]



-- 
Dr. Stephen Childs,
Research Fellow, EGEE Project,    phone:                    +353-1-6081720
Computer Architecture Group,      email:        Stephen.Childs @ cs.tcd.ie
Trinity College Dublin, Ireland   web: http://www.cs.tcd.ie/Stephen.Childs


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

Re: Problems with virtual disks in DomU

[Ian Pratt]

Are you getting a prompt after the fsck fails? I believe you
should if its the normal init scripts.

The fact that you ran all the init scripts means that the file
system must be accessible in the new domain and in reasonable
shape.

What does your /etc/fstab look like? Does it contain proper /dev/
entries or a LABEL= style? (It must contain the former as the
default kernel is not built with devfs).

What happens if you start prodding around the file system?
e.g. do a "find -type f | xargs cat >/dev/null". Do you get
errors or does it look OK? What happens if you run fsck manually?
(use the -N flag if you're chicken ;-)

BTW: what distro on what file system are you using?

Ian


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

Re: Problems with virtual disks in DomU

[Stephen Childs]

OK I rebuilt the domain's filesystem and it does seem to have been corrupt. 
I can get DomainU to boot from it now when I pass in the partitions 
explicitly. It still hangs when I export the whole disk though. It would be 
nice to be able to see the whole disk as I am trying to set up an LCFGng 
install which would want to do things like partitioning the "disk" it's 
passed in.

Thanks for your help,

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

Re: Problems with virtual disks in DomU

[Keir Fraser]

Do you have any more luck with a 2.4-xenU rather than 2.6?

The blkdev setup code is very different between the two, and
specifying whole devices probably hasn't been tested very much with
2.6. 

 -- Keir

> OK I rebuilt the domain's filesystem and it does seem to have been corrupt. 
> I can get DomainU to boot from it now when I pass in the partitions 
> explicitly. It still hangs when I export the whole disk though. It would be 
> nice to be able to see the whole disk as I am trying to set up an LCFGng 
> install which would want to do things like partitioning the "disk" it's 
> passed in.
> 
> Thanks for your help,
> 
> 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@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



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

Re: Problems with virtual disks in DomU

[Ian Pratt]

> OK I rebuilt the domain's filesystem and it does seem to have been corrupt. 
> I can get DomainU to boot from it now when I pass in the partitions 
> explicitly. It still hangs when I export the whole disk though. It would be 
> nice to be able to see the whole disk as I am trying to set up an LCFGng 
> install which would want to do things like partitioning the "disk" it's 
> passed in.

Exporting of whole disks should now be fixed. 

Best,
Ian


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

Re: Problems with virtual disks in DomU

[Mark Williamson]

Interestingly, these lines show Xend sending a "Front end you are connected" 
message to the domain, even though the output you connected is for the case 
where the domain thinks connection failed...  Something funny must be going on!

> CtrlMsgRcvr>writeRequest> message: type= blkif_fe_interface_status_changed_t 
> 2:0 id=21
> payload= {'status': 2, 'handle': 0, 'evtchn': 4}

I'll have a poke around for clues in the source...

Mark



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