| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Fwd: Re: [Xen-devel] Problem exporting enbd device from Dom0 to DomU
OK, with the new patch (CSet 1.1164) in the bitkeeper repository
export of enbd devices from Dom0 to DomU is working now. Thx :-)
Sven
>
>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)
[....]
>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
>
>
*********** END FORWARDED MESSAGE ***********
-------------------------------------------------------
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
|
|
|
| |
|
Home