Hi All,
I sent the patch to make blktap work with PV-on-HVM.
For system volume to boot hda or xvda,
I corrected the patch.
Signed-off-by: Takanori Kasai <kasai.takanori@xxxxxxxxxxxxxx>
This patch made it possible to use either.
disk = [ 'tap:aio:/xen/test/rhel5ga_full.img,hda,w' ]
or
disk = [ 'tap:aio:/xen/test/rhel5ga_full.img,xvda,w' ]
It is assumed that hda is a volume of the system
if both xvda and hda are specified.
disk = [ 'file:/xen/test/rhel5ga_full.img,hda,w',
'tap:aio:/xen/test/drive2.img,xvda,w' ]
Best Regards,
--
Takanori Kasai
----- Original Message -----
From: "Kasai Takanori" <kasai.takanori@xxxxxxxxxxxxxx>
To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Sent: Friday, July 06, 2007 7:50 PM
Subject: [Xen-devel] [PATCH] Allow blktap to be able to be booted as
systemvolume for PV-on-HVM
Hi All,
We were testing the PV driver on the HVM domain.
When blktap was booting system volume, PV-on-HVM domain was not able to be
started.
The configuration file is specified as follows.
disk = [ 'tap:aio:/xen/test/rhel5ga_full.img,hda,w' ]
The error occurred by the initialization of system volume in qemu-dm.
qemu: could not open hard disk image 'aio:/xen/test/rhel5ga_full.img'
It is because "aio:" is added to the head of params in xenstore.
However, qemu-dm open device by params.
This patch corrected the problem of params on the qemu-dm.
Signed-off-by: Takanori Kasai <kasai.takanori@xxxxxxxxxxxxxx>
Signed-off-by: Tomonari Horikoshi <t.horikoshi@xxxxxxxxxxxxxx>
Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@xxxxxxxxxxxxxx>
The execution result is as follows.
# xm create -f rhel5ga_vti.conf
Using config file "./rhel5ga_vti.conf".
Started domain RHEL5GA-test2
# xm block-list RHEL5GA-test2
Vdev BE handle state evt-ch ring-ref BE-path
768 0 0 1 -1 -1 /local/domain/0/backend/tap/75/768
... <<= /* Waiting for booting process */
# xm block-list RHEL5GA-test2
Vdev BE handle state evt-ch ring-ref BE-path
768 0 0 4 7 8 /local/domain/0/backend/tap/75/768
Best Regards,
allow-blktap-system-volume-2.patch
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|