Yes, that solves the problem.
Thanks a lot.
BTW. what configuration will lead me to the blktap (blktap1) driver instead of the new blktap2 driver?

On Tue, Jun 22, 2010 at 6:57 PM, Luís Silva <luis.silva@axiomasoft.pt> wrote:
Hello,

I think that in order to use tap devices with pvops kernel you have to use "tap2:aio:path_to_file". At least it works for me... Even for 4.0.1 rc2 I had to use "tap2:tapdisk:aio:...".

Luís

On Tue, 2010-06-22 at 11:01 -0400, Jia Rao wrote:
The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1.


However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver.


When using tap:aio: PATH/disk.img in domU disk configuration, the boot process hanged at a prompt:
XENBUS: Waiting for devices to initialise: 295s...290s...
Then after reboot, the domU can not mount the filesystem /dev/root and kernel panic.


When using tap:tapdisk:aio PATH/disk.img. the booting process terminated at a error:
Error: [Errno 2] No such file or directory: 'aio:/PATH/disk.img'


When using file:PATH/disk.img, domU can boot successfully.


Thus I am afraid it is somethin wrong with tapdisk driver in dom0


FYI
dom0: 2.6.32.15 centos 5.4
dom0 config: 
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=m
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m


I did load the modules: blktap xen_blkfront xen_netfront before starting xend.


xen: 4.0.1-rc3-pre


any ideas?


Thanks. 




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