Xen devel - Jan 2007 - [PATCH] [PV-ON-HVM] Fix evtchn interface

Hi All,

The interface of the evtchn has been changed as follows.

・xen-unstable.hg : cs13198
   [PV-ON-HVM] Update evtchn interface to match new PV Linux interfaces.
・xen-unstable.hg : cs13197
   [LINUX] Extend the event-channel interfaces to provide helper methods


However, the following errors occur if pv-on-hvm is done in insmod.
This patch corrected this issue. 

---
# insmod xen-vbd.ko
xen-vbd: Unknown symbol irq_to_evtchn_port
insmod: error inserting ''xen-vbd.ko'': -1 Unknown symbol in
module
---

Thanks,

--
Takanori Kasai

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

Hi Kasai,

After applying the patch, the unknown symbol issue is gone. However, I got 
another problem. After I load xen-platform-pci.ko successfully, Xen hangs up 
when I try to load xenbus.ko. Xen died sliently without any prompt when I 
did insmod xenbus.ko. I set up my HVM domain by installing a fresh RHEL 4.4 
from ISO image file which is using 2.6.9-42 kernel by default. Then I 
downloaded a fresh 2.6.16.33 kernel to HVM domain and built that kernel. I 
also built VBD modules on this HVM domain and using the same kernel version 
headers. However, I can still not load Xenbus.ko module. The Xen version
I''m
using is Xen 3.0.4 and the latest Xen_unstable.

Do you know how to solve this problem?

Thanks,

Liang

----- Original Message ----- 
From: "Kasai Takanori" <kasai.takanori@jp.fujitsu.com>
To: "xen-devel" <xen-devel@lists.xensource.com>
Sent: Tuesday, January 09, 2007 7:34 PM
Subject: [Xen-devel] [PATCH] [PV-ON-HVM] Fix evtchn interface

> Hi All,
>
> The interface of the evtchn has been changed as follows.
>
> ・xen-unstable.hg : cs13198
>   [PV-ON-HVM] Update evtchn interface to match new PV Linux interfaces.
> ・xen-unstable.hg : cs13197
>   [LINUX] Extend the event-channel interfaces to provide helper methods
>
>
> However, the following errors occur if pv-on-hvm is done in insmod.
> This patch corrected this issue.
>
> ---
> # insmod xen-vbd.ko
> xen-vbd: Unknown symbol irq_to_evtchn_port
> insmod: error inserting ''xen-vbd.ko'': -1 Unknown symbol
in module
> ---
>
> Thanks,
>
> --
> Takanori Kasai

--------------------------------------------------------------------------------

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

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

On Wed, 2007-01-10 at 11:34 +0900, Kasai Takanori wrote:
> Hi All,
> 
> The interface of the evtchn has been changed as follows.
> 
> ・xen-unstable.hg : cs13198
>    [PV-ON-HVM] Update evtchn interface to match new PV Linux interfaces.
> ・xen-unstable.hg : cs13197
>    [LINUX] Extend the event-channel interfaces to provide helper methods
> 
> 
> However, the following errors occur if pv-on-hvm is done in insmod.
> This patch corrected this issue. 
Keir has already applied this one (13284:d3e40fd6038e) but it is stuck
in the staging tree until regression testing passes.

Ian.



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

On 10/1/07 03:09, "Liang Yang" <multisyncfe991@hotmail.com>
wrote:
> After applying the patch, the unknown symbol issue is gone. However, I got
> another problem. After I load xen-platform-pci.ko successfully, Xen hangs
up
> when I try to load xenbus.ko. Xen died sliently without any prompt when I
> did insmod xenbus.ko. I set up my HVM domain by installing a fresh RHEL 4.4
> from ISO image file which is using 2.6.9-42 kernel by default. Then I
> downloaded a fresh 2.6.16.33 kernel to HVM domain and built that kernel. I
> also built VBD modules on this HVM domain and using the same kernel version
> headers. However, I can still not load Xenbus.ko module. The Xen version
I''m
> using is Xen 3.0.4 and the latest Xen_unstable.
> 
> Do you know how to solve this problem?
We''re working on this one. Should have a fix today.

 -- Keir


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

>After applying the patch, the unknown symbol issue is gone. However, I got 
>another problem. After I load xen-platform-pci.ko successfully, Xen hangs up
>when I try to load xenbus.ko. Xen died sliently without any prompt when I 
>did insmod xenbus.ko. I set up my HVM domain by installing a fresh RHEL 4.4 
>from ISO image file which is using 2.6.9-42 kernel by default. Then I 
>downloaded a fresh 2.6.16.33 kernel to HVM domain and built that kernel. I 
>also built VBD modules on this HVM domain and using the same kernel version 
>headers. However, I can still not load Xenbus.ko module. The Xen version
I''m
>using is Xen 3.0.4 and the latest Xen_unstable.
This should all be fixed now by -unstable cset 13321:5c5d9692f559


cheers,

S.


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

Just tested xen-unstable cse 13321. The bug is solved!!! VBD works now!!! 
Great!!!

Liang

----- Original Message ----- 
From: "Steven Hand" <Steven.Hand@cl.cam.ac.uk>
To: "Liang Yang" <multisyncfe991@hotmail.com>
Cc: "Kasai Takanori" <kasai.takanori@jp.fujitsu.com>;
"xen-devel"
<xen-devel@lists.xensource.com>; <Steven.Hand@cl.cam.ac.uk>
Sent: Wednesday, January 10, 2007 9:32 AM
Subject: Re: [Xen-devel] [PATCH] [PV-ON-HVM] Fix evtchn interface

>
>>After applying the patch, the unknown symbol issue is gone. However, I
got
>>another problem. After I load xen-platform-pci.ko successfully, Xen
hangs
>>up
>>when I try to load xenbus.ko. Xen died sliently without any prompt when
I
>>did insmod xenbus.ko. I set up my HVM domain by installing a fresh RHEL 
>>4.4
>>from ISO image file which is using 2.6.9-42 kernel by default. Then I
>>downloaded a fresh 2.6.16.33 kernel to HVM domain and built that kernel.
I
>>also built VBD modules on this HVM domain and using the same kernel 
>>version
>>headers. However, I can still not load Xenbus.ko module. The Xen version
>>I''m
>>using is Xen 3.0.4 and the latest Xen_unstable.
>
> This should all be fixed now by -unstable cset 13321:5c5d9692f559
>
>
> cheers,
>
> S.
>
> 

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

Hi,

I have these questions for a while. As AIO can help improve better 
performance and Linux kernel keeps tunning the AIO path,  more and more IOs 
can be expected to take AIO path instead of regular I/O path.

First Question:
If we consider Xen, do we need to do AIO both in the domain0 and guest 
domains at the same? For example, considering two situations, let a full 
virtualized guest domain still do regular I/O and domain0 (vbd back end 
driver) do AIO; or let both full-virtualized guest domain and domain0 do 
AIO. What is possible performance difference here?

Second Question:
Does Domain0 always wait till AIO data is available and then notify guest 
domain? or Domain0 will issue an interrupt immediately to notify guest 
domain0 when AIO is queued? If the first case is true, then all AIOs will 
become synchronous.

Third Question:
Does Xen hypervisor change the behavior of Linux I/O scheduler more or less?

Four Question:
Will AIO have different performance impact on para-virtualized domain and 
full-virtualized domain respectively?

Thanks,

Liang


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