[Xen-devel] [PATCH]: blktap2 : control function

[eXeC001er <execooler@xxxxxxxxx>]

Hi.

I tried to create small patch for blktap2 : control function:

diff -r 840f269d95fb tools/python/xen/xend/XendDomainInfo.py

--- a/tools/python/xen/xend/XendDomainInfo.py Wed May 19 22:59:52 2010 +0100

+++ b/tools/python/xen/xend/XendDomainInfo.py Fri May 21 20:17:15 2010 +0400

@@ -3292,6 +3292,7 @@

                 fn = BOOTLOADER_LOOPBACK_DEVICE

 

             try:

+                time.sleep(5)

                 blcfg = bootloader(blexec, fn, self, False,

                                    bootloader_args, kernel, ramdisk, args)

             finally:

@@ -3299,7 +3300,7 @@

                     log.info("Unmounting %s from %s." %

                              (fn, BOOTLOADER_LOOPBACK_DEVICE))

 

-                    dom0.destroyDevice('tap', BOOTLOADER_LOOPBACK_DEVICE)

+                    dom0.destroyDevice(devtype, BOOTLOADER_LOOPBACK_DEVICE)

 

             if blcfg is None:

                 msg = "Had a bootloader specified, but can't find disk"

With this patch DomU boot from VHD disk without error.

But i can not fix other bug:

if after DomU (boot disk is blktap2-type) stopped i can not start it again, because i get error "raise VmError("Device %s is already connected." % dev_str)" in "DevController.py".

but i found workaround:

stop blktap2_mount: echo 1 > /sys/class/blktap2/blktapX/remove

remove records from xenstore: 

xenstore-rm /vm/00000000-0000-0000-0000-000000000000

xenstore-write /local/domain/0/vm ""

Now i can run my DomU again.

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