Hi Ian, I''m not completely sure about this one. The question is what you really wanted to achieve with that BLOCK_DRIVER_FLAG_EXTENDABLE thing. I suspect that you just put it into the wrong struct accidentally (bdrv_host_device instead of bdrv_raw), but I might be wrong. Changing it allows me to use qcow2 images through tap:ioemu again - in fact, I think it fixes extendable images in general, i.e. also for HVM. Please check if the attached patch makes sense and apply if appropriate. Kevin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Kevin Wolf writes ("[PATCH] qemu-xen: Fix extendable images"):> I''m not completely sure about this one. The question is what you really > wanted to achieve with that BLOCK_DRIVER_FLAG_EXTENDABLE thing. I > suspect that you just put it into the wrong struct accidentally > (bdrv_host_device instead of bdrv_raw), but I might be wrong. Changing > it allows me to use qcow2 images through tap:ioemu again - in fact, I > think it fixes extendable images in general, i.e. also for HVM. > > Please check if the attached patch makes sense and apply if appropriate.I think you''re right, thanks. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Apparently Analagous Threads
- Bug#536175: Bug#536175: Bug#536176: xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?)
- Bug#490409: xen-3: diff for NMU version 3.2.1-2.1
- [RFC][PATCH] Use ioemu block drivers through blktap
- [PATCH][QEMU] Add IA64-specific code for new qemu.
- Qemu-0.8.1 based ioemu preview available