search for: blktapctrl_linux

...KTAPCTRL[2444]: blktapctrl.c:792: Found driver: [vmware image (vmdk)] BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [ramdisk image (ram)] BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [qcow disk (qcow)] BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [qcow2 disk (qcow2)] BLKTAPCTRL[2444]: blktapctrl_linux.c:86: blktap0 open failed BLKTAPCTRL[2444]: blktapctrl.c:859: couldn''t open blktap interface BLKTAPCTRL[2444]: blktapctrl.c:922: Unable to start blktapctrl I''ve also attached the output from /var/log/xen/xend.log when attempting to bringup the Windows domU. When the Windows domU...

...lkback: ring-ref 8, event-channel 10, protocol 2 (x86_32-abi) blkback: ring-ref 9, event-channel 11, protocol 2 (x86_32-abi) blkback: ring-ref 10, event-channel 12, protocol 2 (x86_32-abi) blkback: ring-ref 11, event-channel 13, protocol 2 (x86_32-abi) and when i start xend i get the following: blktapctrl_linux.c:92: couldnt find device number for blktap0 blktapctrl.c:859:couldnt open blktap interface blktapctrl.c:922:unable to start blktapctrl any ideas? Ben -------- Original-Nachricht -------- Betreff: Strange network problem Datum: Mon, 03 May 2010 08:22:02 +0200 Von: Benjamin Schweikert <b.s...

...9]: blktapctrl.c:790: Found driver: [vmware image (vmdk)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [ramdisk image (ram)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [qcow disk (qcow)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [qcow2 disk (qcow2)] BLKTAPCTRL[6569]: blktapctrl_linux.c:92: couldn't find device number for 'blktap0' BLKTAPCTRL[6569]: blktapctrl.c:857: couldn't open blktap interface BLKTAPCTRL[6569]: blktapctrl.c:916: Unable to start blktapctrl This appears to be because blktapctrl is trying to open one of these /sys/class/xen/blktap0/de...

...vmdk)] BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [ramdisk image (ram)] BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [qcow disk (qcow)] BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [qcow2 disk (qcow2)] BLKTAPCTRL[1091]: blktapctrl.c:738: Found driver: [ioemu disk] BLKTAPCTRL[1091]: blktapctrl_linux.c:21: Created /dev/xen/blktap0 device # # uname -r 2.6.18.8-xen # xm create -c /mnt/xenU Using config file "./xenU". # Error: Device 0 (vif) could not be connected.Hotplug scripts not working. In log message i found the following message # tail -35 /var/log/xen/xen-hotplug.log /etc/xen/...

I run my production DomU''s using Xen 3.4.1 at the moment with the old 2.6.18.x dom0 kernel. I just built a new Xen version (4.0.1-rc5) with jemerys git repo of 2.6.32.16 dom0 pvops kernel. When starting domains the go instantly into a paused state and eventually i see this error on the command line. [root@host test1]# xm create -c vps.config Using config file

Hi Konrad I encountered a bug when trying to bring offline a cpu then online it again in HVM. As I''m not very familiar with HVM stuffs I cannot come up with a quick fix. The HVM DomU is configured with 4 vcpus. After booting into command prompt, I do following operations. # echo 0 > /sys/devices/system/cpu/cpu3/online # echo 1 > /sys/devices/system/cpu/cpu3/online With