Xen devel - Oct 2007 - [PATCH] [IOEMU] Allow blktap to be able to be booted as systemvolume for PV-on-HVM(TAKE 3)

Hi All,

I sent the patch to make blktap work with PV-on-HVM.
I corrected the part that had been pointed out in the Xen community.

・All xvdN disk is looked like hdN.
・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.)

We cannot use blktap for the volume of the system with PV-on-HVM
and are embarrassed.
Could you apply this patch? Or, please give the comment to me.

Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

Best Regards,

--
Takanori Kasai

----- Original Message ----- 
From: "Kasai Takanori" <kasai.takanori@jp.fujitsu.com>
To: "xen-devel" <xen-devel@lists.xensource.com>
Sent: Thursday, July 12, 2007 9:13 AM
Subject: [Xen-devel] [PATCH] Allow blktap to be able to be booted as 
systemvolume for PV-on-HVM(TAKE 2)

> 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@jp.fujitsu.com>
>
> 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@jp.fujitsu.com>
> To: "xen-devel" <xen-devel@lists.xensource.com>
> 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@jp.fujitsu.com>
>> Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
>> Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@jp.fujitsu.com>
>>
>> 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,
> 

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

Hi Kasai,

It seems there is a bug caused by this patch. 
If providing both hda and xvda, there would be two hda devices given to Qemu.
And the image of xvda would be recover the real hda. If xvda doesn''t
include booting system, HVM booting failed. So how about have a little modify?
If there is a hdx device, don''t translate xvdx to related hdx.

Best Regards,
Yongkang You
 
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com 
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>Kasai Takanori
>Sent: Monday, October 15, 2007 6:43 PM
>To: xen-devel
>Subject: [Xen-devel] [PATCH] [IOEMU] Allow blktap to be able 
>to be booted assystemvolume for PV-on-HVM(TAKE 3)
>
>Hi All,
>
>I sent the patch to make blktap work with PV-on-HVM.
>I corrected the part that had been pointed out in the Xen community.
>
>・All xvdN disk is looked like hdN.
>・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.)
>
>We cannot use blktap for the volume of the system with PV-on-HVM
>and are embarrassed.
>Could you apply this patch? Or, please give the comment to me.
>
>Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>
>
>Best Regards,
>
>--
>Takanori Kasai
>
>----- Original Message ----- 
>From: "Kasai Takanori" <kasai.takanori@jp.fujitsu.com>
>To: "xen-devel" <xen-devel@lists.xensource.com>
>Sent: Thursday, July 12, 2007 9:13 AM
>Subject: [Xen-devel] [PATCH] Allow blktap to be able to be booted as 
>systemvolume for PV-on-HVM(TAKE 2)
>
>
>> 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@jp.fujitsu.com>
>>
>> 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@jp.fujitsu.com>
>> To: "xen-devel" <xen-devel@lists.xensource.com>
>> 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@jp.fujitsu.com>
>>> Signed-off-by: Tomonari Horikoshi
<t.horikoshi@jp.fujitsu.com>
>>> Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@jp.fujitsu.com>
>>>
>>> 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,
>> 
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi Yongkang,

Thank you for reply.

There is a problem when hdN and xvdN are specified at the same time.
Because the patch has already been applied, the hot fix is sent by the addition.

It corrects as follows.
- Whether hdN is defined first is checked.
- If hdN is defined, xvdN is not replaced with hdN.

I will make the hot fix of the addition and contribute to the community.

Best Regards,

--
Takanori Kasai


----- Original Message ----- 
From: "You, Yongkang" <yongkang.you@intel.com>
To: "Kasai Takanori" <kasai.takanori@jp.fujitsu.com>;
"xen-devel"
<xen-devel@lists.xensource.com>
Sent: Tuesday, October 16, 2007 12:05 PM
Subject: RE: [Xen-devel] [PATCH] [IOEMU] Allow blktap to be able to be booted 
assystemvolume for PV-on-HVM(TAKE 3)

> Hi Kasai,
>
> It seems there is a bug caused by this patch.
> If providing both hda and xvda, there would be two hda devices given to
Qemu.
> And the image of xvda would be recover the real hda. If xvda
doesn''t include
> booting system, HVM booting failed. So how about have a little modify? If 
> there is a hdx device, don''t translate xvdx to related hdx.
>
> Best Regards,
> Yongkang You
>
>
>>-----Original Message-----
>>From: xen-devel-bounces@lists.xensource.com
>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
>>Kasai Takanori
>>Sent: Monday, October 15, 2007 6:43 PM
>>To: xen-devel
>>Subject: [Xen-devel] [PATCH] [IOEMU] Allow blktap to be able
>>to be booted assystemvolume for PV-on-HVM(TAKE 3)
>>
>>Hi All,
>>
>>I sent the patch to make blktap work with PV-on-HVM.
>>I corrected the part that had been pointed out in the Xen community.
>>
>>・All xvdN disk is looked like hdN.
>>・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.)
>>
>>We cannot use blktap for the volume of the system with PV-on-HVM
>>and are embarrassed.
>>Could you apply this patch? Or, please give the comment to me.
>>
>>Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>
>>
>>Best Regards,
>>
>>--
>>Takanori Kasai
>>
>>----- Original Message ----- 
>>From: "Kasai Takanori" <kasai.takanori@jp.fujitsu.com>
>>To: "xen-devel" <xen-devel@lists.xensource.com>
>>Sent: Thursday, July 12, 2007 9:13 AM
>>Subject: [Xen-devel] [PATCH] Allow blktap to be able to be booted as
>>systemvolume for PV-on-HVM(TAKE 2)
>>
>>
>>> 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@jp.fujitsu.com>
>>>
>>> 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@jp.fujitsu.com>
>>> To: "xen-devel" <xen-devel@lists.xensource.com>
>>> 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@jp.fujitsu.com>
>>>> Signed-off-by: Tomonari Horikoshi
<t.horikoshi@jp.fujitsu.com>
>>>> Signed-off-by: Tsunehisa Doi
<Doi.Tsunehisa@jp.fujitsu.com>
>>>>
>>>> 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,
>>>
>>
> 


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