Re: [Xen-devel] Problem exporting enbd device from Dom0 to DomU

["Sven Kretzschmar" <sven.kretzschmar@xxxxxx>]

Here are the requested outputs.
HTH ?!  ;-)

 Sven

[root@testy1 root]# sfdisk -s /dev/nda
9775520

[root@testy1 root]# ls -al /dev/nda
brw-r--r--  1 root root 43, 0 Aug  1 13:15 /dev/nda

[root@testy1 root]# dmesg
Linux version 2.6.7-xen0 (root@xxxxxxxxxxxx) (gcc version 3.3.3 20040412 (Red 
Hat Linux 3.3.3-7)) #7 Fri Aug 6 15:06:44 CEST 2004
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000008000000 (usable)
128MB LOWMEM available.
On node 0 totalpages: 32768
  DMA zone: 0 pages, LIFO batch:1
  Normal zone: 32768 pages, LIFO batch:8
  HighMem zone: 0 pages, LIFO batch:1
DMI not present.
Built 1 zonelists
Kernel command line: /boot/vmlinuz-2.6.7-xen0 root=/dev/hda1 ro console=vga
Unknown boot option `/boot/vmlinuz-2.6.7-xen0': ignoring
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Xen reported: 2792.137 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 126528k/131072k available (1879k kernel code, 4352k reserved, 571k 
data, 340k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 5570.56 BogoMIPS
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU:     After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU:     After all inits, caps: bfebfbff 00000000 00000000 00000080
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
NET: Registered protocol family 16
PCI: Using configuration type Xen
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Probing PCI hardware (bus 01)
PCI: Probing PCI hardware
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NTFS driver 2.1.14 [Flags: R/O].
udf: registering filesystem
Real Time Clock Driver v1.12
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 0000:00:1f.1
PCI: Obtained IRQ 16 for device 0000:00:1f.1
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:DMA
hda: Maxtor 6Y060L0, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdd: CD-RW 48X16, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 120103200 sectors (61492 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 hda: hda1 hda2 hda3 hda4 < hda5 >
hdd: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
Xen virtual console successfully installed as ttyS
Event-channel device installed.
Initialising Xen netif backend
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 340k freed
Warning: unable to open an initial console.
EXT3 FS on hda1, internal journal
Adding 1024120k swap on /dev/hda2.  Priority:-1 extents:1
e100: Intel(R) PRO/100 Network Driver, 3.0.18
e100: Copyright(c) 1999-2004 Intel Corporation
PCI: Obtained IRQ 22 for device 0000:01:0a.0
e100: eth0: e100_probe: addr 0xe8080000, irq 22, MAC addr 00:30:1B:AE:F0:D1
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e1000: Ignoring new-style parameters in presence of obsolete ones
Intel(R) PRO/1000 Network Driver - version 5.2.52-k4
Copyright (c) 1999-2004 Intel Corporation.
PCI: Obtained IRQ 21 for device 0000:01:09.0
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
e1000: eth1: e1000_watchdog: NIC Link is Down
e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
ENBD #5150[0]: enbd_init Network Block Device originally by pavel@xxxxxxxxxxxxx
ENBD #5151[0]: enbd_init Network Block Device port to 2.0 by ptb@xxxxxxxxxx
ENBD #5153[0]: enbd_init Network Block Device move networking to user space by 
amarin@xxxxxxxxxx
ENBD #5155[0]: enbd_init Enhanced Network Block Device 2.4.30 $Date: 2002/09/17 
16:33:22 $ by ptb@xxxxxxxxxx
ENBD #5195[0]: enbd_init registered device at major 43
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
ENBD #3754[0]: fixup_slot failed to find slot for pid 1541 ioctl 4004ab10 arg 
bfffe120 (74736574)
ENBD #2738[0]: enbd_set_sock increased socket count to 2
ENBD #2533[0]: enbd_enable set VALID on nda
ENBD #823[0]: enbd_open DISK CHECK wanted in open on device nda
ENBD #4398[0]: enbd_media_changed MEDIA CHANGED called
ENBD #4454[0]: enbd_media_changed REMOTE CHECK still has REMOTE VALID on nda
ENBD #823[1]: enbd_open DISK CHECK wanted in open on device nda
ENBD #4398[1]: enbd_media_changed MEDIA CHANGED called
ENBD #4454[1]: enbd_media_changed REMOTE CHECK still has REMOTE VALID on nda
ENBD #2738[1]: enbd_set_sock increased socket count to 4
ENBD #823[2]: enbd_open DISK CHECK wanted in open on device nda
ENBD #4398[2]: enbd_media_changed MEDIA CHANGED called
ENBD #4454[2]: enbd_media_changed REMOTE CHECK still has REMOTE VALID on nda
ENBD #823[3]: enbd_open DISK CHECK wanted in open on device nda
ENBD #4398[3]: enbd_media_changed MEDIA CHANGED called
ENBD #4454[3]: enbd_media_changed REMOTE CHECK still has REMOTE VALID on nda
ENBD #823[4]: enbd_open DISK CHECK wanted in open on device nda
ENBD #4398[4]: enbd_media_changed MEDIA CHANGED called
ENBD #4454[4]: enbd_media_changed REMOTE CHECK still has REMOTE VALID on nda



*********** REPLY SEPARATOR  ***********

On 06.08.2004 at 15:31 Ian Pratt wrote:

>> When I try to export the enbd device ("dev/nda") from Dom0
>> to another unprivileged domain (with kernel 2.4.26) then it does not
>work.
>> The interesting part of my xmdefaults file looks like that:
>>
>> disk = ['phy:nda,sdb,w','phy:hda3,sda1,w]
>
>> [2004-08-06 16:35:52 xend] DEBUG (__init__:988) Error: Adding extent to
>vbd failed! (device 2b00)
>> [2004-08-06 16:35:52 xend] DEBUG (__init__:988) Connecting blkif to
>event channel dom=3 ports=14:4
>>
>> I think the line starting with "Error:..." is the important one. What
>does device 2b00 mean ?
>
>Please can you post the output of dmesg from dom0, also 'ls -l /dev/nda'
>'sfdisk -s /dev/nda'.
>
>
>Ian





-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel