Hi Daniel,
Thank you for the reply.
That's not safe enough since it always looks for a ':' regardless of
whether the driver is 'tap' or not.
Does it mean to have to check the assumed keyword(aio,sync,qcow)?
If it is so, I will correct the patch.
It also doesn't take account of
fact that the device may be named 'xvda' rather than 'hda'.
I saw the presented patches. The xvdN was forcedly looked like the hdN.
For example, the hdc is a special device named CDROM in qemu-dm.
Therefore, I think that it should not forcedly do it because it cannot take the
consistency.
I think the HVM domain to be should boot on the hda as it is a specification of
qemu-dm.
Best Regards,
--
Takanori Kasai
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|