Re: [Xen-devel] Problem with blktap2

[Jun Koi <junkoi2004@xxxxxxxxx>]

2009/6/19 Zhang, Yang <yang.zhang@xxxxxxxxx>:
> Sorry, qemu's issue also has been fixed by c/s 
> 5e592af4bc5649ef0066c77db445c3be26b4c7bb.
>

I got the latest code, but the problem still stands.

Now the error is a bit different:

"Error: Device 0 (vif) could not be connected. Hotplug scripts not working."


And below is the qemu log file. Do you have any suggestion?

Thanks,
J


domid: 3
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap3.0 xenbr0
Strip off blktap sub-type prefix to
qcow2:/home/xen/img.qcow2.ubuntu904 (drv 'tapdisk')
qemu: type (image format) 'tapdisk' unknown for vbd
'/local/domain/0/backend/tap/3/768/type' or image
'qcow2:/home/xen/img.qcow2.ubuntu904'
Watching /local/domain/0/device-model/3/logdirty/next-active
Watching /local/domain/0/device-model/3/command
qemu_map_cache_init nr_buckets = 4000 size 327680
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 716ebba7-593a-f4c9-3353-32ed070a4d7f
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/vm/716ebba7-593a-f4c9-3353-32ed070a4d7f/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/716ebba7-593a-f4c9-3353-32ed070a4d7f/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0




















> -----Original Message-----
> From: Jun Koi [mailto:junkoi2004@xxxxxxxxx]
> Sent: 2009年6月19日 11:35
> To: Zhang, Yang
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Problem with blktap2
>
> 2009/6/19 Zhang, Yang <yang.zhang@xxxxxxxxx>:
>> i'm not sure that since the blktap2 changes the config. I always uses the 
>> config "tap:tapdisk:qcow2:/root/xxx". This always fine to qcow2
>>
>
> I changed my disk configuration to:
>
> disk = ['tap:tapdisk:qcow2:/home/xen/img.qcow2.ubuntu904,hda,w']
>
> But then when creating the VM, it hang up for a minute or so, and
> finally reported error like:
>
> "Error: Device 768 (tap) could not be connected. Hotplug scripts not working."
>
> You suggested to kill "tapdisk", but I dont see any process like
> "tapdisk" running in my box (only blktapctrl). Is that a problem??
>
> Then qemu log reports error like below. I am especially concerning
> about the error "type tapdisk unknown...", so I am not sure that the
> above disk configuration (..tapdisk...) is correct. Do you have any
> idea?
>
> Thanks,
> J
>
>
> cat /var/log/xen/qemu-dm-ubuntu904.log
> domid: 2
> qemu: the number of cpus is 1
> config qemu network with xen bridge for  tap2.0 xenbr0
> Strip off blktap sub-type prefix to
> qcow2:/home/xen/img.qcow2.ubuntu904 (drv 'tapdisk')
> qemu: type (image format) 'tapdisk' unknown for vbd
> '/local/domain/0/backend/tap/2/768/type' or image
> 'qcow2:/home/xen/img.qcow2.ubuntu904'
> Watching /local/domain/0/device-model/2/logdirty/next-active
> Watching /local/domain/0/device-model/2/command
> qemu_map_cache_init nr_buckets = 4000 size 327680
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 7b6c05c7-1686-699b-dfdd-ef25da4d2039
> Time offset set 0
> populating video RAM at ff000000
> mapping video RAM from ff000000
> Register xen platform.
> Done register platform.
> xs_read(/vm/7b6c05c7-1686-699b-dfdd-ef25da4d2039/log-throttling): read error
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw 
> state.
> xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
> xs_read(): vncpasswd get error.
> /vm/7b6c05c7-1686-699b-dfdd-ef25da4d2039/vncpasswd.
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>
>
>
>
>
>
>
>> -----Original Message-----
>> From: Jun Koi [mailto:junkoi2004@xxxxxxxxx]
>> Sent: 2009年6月19日 11:04
>> To: Zhang, Yang
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-devel] Problem with blktap2
>>
>> 2009/6/19 Zhang, Yang <yang.zhang@xxxxxxxxx>:
>>>  I meet this issue before. You can reboot and have a try.
>>>  If still exist, stop xend and kill process blktapctrl and tapdisk, run 
>>> make install again to see this issue whether still exist.
>>>
>>
>> hmm. then the problem will vanish for goods? i will try now, and let
>> you know the result.
>>
>> Could you confirm that
>>
>> disk = ['tap:aio:qcow:/home/xen/img.qcow2.ubuntu904,hda,w']
>>
>> is a right configuration?
>>
>> Thanks a lot,
>> J
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jun Koi
>>> Sent: 2009年6月19日 10:38
>>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>>> Subject: [Xen-devel] Problem with blktap2
>>>
>>> Hi,
>>>
>>> I am trying to use the unstable tree (changeset: 19738) to run some old 
>>> images.
>>>
>>> My old configuration file has:
>>>
>>> disk = ['tap:qcow2:/home/xen/img.qcow2.ubuntu904,hda,w']
>>>
>>> I got the error like:
>>>
>>> ----
>>> Using config file "./ubuntu904.cfg".
>>> Error: need more than 3 values to unpack
>>>
>>> I guess that I should modify the disk configuration for new blktap2,
>>> so I changed it to :
>>>
>>> disk = ['tap:aio:qcow:/home/xen/img.qcow2.ubuntu904,hda,w']
>>> ----
>>>
>>> but then i still got the error like below:
>>>
>>> ----
>>> Using config file "./ubuntu904.cfg".
>>> Error: Failed to create device.
>>>    stdout: vbd open failed: -1
>>>    stderr:
>>> Check that target "/home/xen/img.qcow2.ubuntu904" exists and that
>>> blktap2 driver installed in dom0.
>>> ----
>>>
>>> I can confirm that I have blktap2 installed, as in
>>> /boot/config-2.6.18.8-xen I have:
>>>
>>> CONFIG_XEN_BLKDEV_TAP=y
>>> CONFIG_XEN_BLKDEV_TAP2=y
>>>
>>> So how can I fix the problem now?
>>>
>>> Thanks,
>>> J
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>>
>>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel