23 messages in com.xensource.lists.xen-ia64-develRE: [Xen-ia64-devel] Please try PV-on...
FromSent OnAttachments
DOI Tsunehisa16 Oct 2006 05:30.patch, .patch, .patch
Doi....@jp.fujitsu.com17 Oct 2006 05:29 
Doi....@jp.fujitsu.com17 Oct 2006 05:31 
Tristan Gingold17 Oct 2006 05:45 
Doi....@jp.fujitsu.com17 Oct 2006 06:12 
Tristan Gingold17 Oct 2006 06:34 
You, Yongkang17 Oct 2006 07:27 
You, Yongkang17 Oct 2006 07:36 
You, Yongkang17 Oct 2006 18:59 
Alex Williamson17 Oct 2006 21:16 
Doi....@jp.fujitsu.com18 Oct 2006 00:55 
You, Yongkang18 Oct 2006 01:02 
Doi....@jp.fujitsu.com18 Oct 2006 01:15 
You, Yongkang18 Oct 2006 01:17 
Doi....@jp.fujitsu.com18 Oct 2006 01:37 
Kasai Takanori18 Oct 2006 22:32 
You, Yongkang19 Oct 2006 02:41 
Kasai Takanori20 Oct 2006 02:51 
Kasai Takanori15 Nov 2006 20:09 
You, Yongkang15 Nov 2006 21:08 
Kasai Takanori15 Nov 2006 22:11 
You, Yongkang15 Nov 2006 22:55 
Kasai Takanori16 Nov 2006 20:15 
Subject:RE: [Xen-ia64-devel] Please try PV-on-HVM on IPF
From:You, Yongkang (yong@intel.com)
Date:10/17/2006 06:59:42 PM
List:com.xensource.lists.xen-ia64-devel

HI Tsunehisa,

More testing results based on changeset 11810: ---------- 1. I did a continuous KB in VTI VBD disk 35 times, all passed. The KB speed in
VBD is a little faster than in IOEMU disk. 2. I did a lot of scp >1G file by VTI VNIF, all pass. The scp speed is
extraordinary higher than without VNIF. 3. UP and SMP(2vcpus) VTI can both use PV drivers.

Issues: ---------- I noticed there are too many "kernel unaligned access" reported by VTI, after
insert vnif module.

Two issues reported by yesterday: ----------- 1. If use IOEMU NIC too, insert VNIF driver will cause VTI domain crash. IA32
hasn't this issue. 2. After insert VNIF driver, VTI kernel often calls trace when running
applications (kudzu, vi etc.).

Best Regards, Yongkang (Kangkang) 永康

-----Original Message----- From: xen-@lists.xensource.com [mailto:xen-@lists.xensource.com] On Behalf Of DOI Tsunehisa Sent: 2006年10月16日 20:31 To: xen-ia64-devel Subject: [Xen-ia64-devel] Please try PV-on-HVM on IPF

Hi all,

We've ported PV-on-HVM drivers for IPF. But I think that only few tries it. Thus, I try to describe to use it.

And I attach several patches about PV-on-HVM.

+ fix-warning.patch - warning fix for HVM PV driver + notsafe-comment.patch - add not-SMP-safe comment about PV-on-HVM - to take Isaku's suggestion. + pv-backport.patch (preliminary) - current HVM PV driver for only 2.6.16 or 2.6.16.* kernel - this is preliminary patch for backporting to before 2.6.16 kernel - we tested only compiling on RHEL4.

[Usage of PV-on-HVM]

1) get xen-ia64-unstable.hg tree (after cs:11805) and built it.

2) create a guest system image. - simply, install guest system on VT-i domain

3) build linux-2.6.16 kernel for guest system - get linux-2.6.16 kernel source and build

4) change guest kernel in the image to linux-2.6.16 kernel - edit config file of boot loader

5) build PV-on-HVM drivers # cd xen-ia64-unstable.hg/unmodified_drivers/linux-2.6 # sh mkbuildtree # make -C /usr/src/linux-2.6.16 M=$PWD modules

6) copy the drivers to guest system image - mount guest system image with lomount command. - copy the drivers to guest system image # cp -p */*.ko guest_system...

7) start VT-i domain

8) attach drivers domvti# insmod xen-platform-pci.ko domvti# insmod xenbus.ko domvti# insmod xen-vbd.ko domvti# insmod xen-vnif.ko

9) attach devices with xm block-attach/network-attach - this operation is same for dom-u