similar to: Xen/paravirt_ops page on Xen wiki

I''ve updated the wiki to reflect some more of the steps and workarounds that are currently needed. Please add your comments/updates/corrections: http://wiki.xensource.com/xenwiki/XenParavirtOps Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

----- Forwarded message from Jeremy Fitzhardinge <jeremy at goop.org> ----- From: Jeremy Fitzhardinge <jeremy at goop.org> To: Xen-devel <xen-devel at lists.xensource.com>, xen-users at lists.xensource.com, Virtualization Mailing List <virtualization at lists.osdl.org> Cc: Date: Wed, 30 Jul 2008 17:51:37 -0700 Subject: [Xen-devel] State of Xen in upstream Linux Well,

I'm implementing a more efficient version of the Xen iret paravirt_op, so that it can use the real iret instruction where possible. I really need to get access to per-cpu variables, so I can set the event mask state in the vcpu_info structure, but unfortunately at the point where INTERRUPT_RETURN is used in entry.S, the usermode %fs has already been restored. How would you feel if we changed

I'm implementing a more efficient version of the Xen iret paravirt_op, so that it can use the real iret instruction where possible. I really need to get access to per-cpu variables, so I can set the event mask state in the vcpu_info structure, but unfortunately at the point where INTERRUPT_RETURN is used in entry.S, the usermode %fs has already been restored. How would you feel if we changed

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

From: "Luis R. Rodriguez" <mcgrof at suse.com> The general documentation we have for pv_ops is currenty present on the IA64 docs, but since this documentation covers IA64 xen enablement and IA64 Xen support got ripped out a while ago through commit d52eefb47 present since v3.14-rc1 lets just simplify, generalize and move the pv_ops documentation to a shared place. Cc: Isaku

From: "Luis R. Rodriguez" <mcgrof at suse.com> The general documentation we have for pv_ops is currenty present on the IA64 docs, but since this documentation covers IA64 xen enablement and IA64 Xen support got ripped out a while ago through commit d52eefb47 present since v3.14-rc1 lets just simplify, generalize and move the pv_ops documentation to a shared place. Cc: Isaku

What's paravirt_ops.halt for? Is it the non-safe equivalent to safe_halt, or is it intended for shutting down the machine? It doesn't seem to be used anywhere. J

What's paravirt_ops.halt for? Is it the non-safe equivalent to safe_halt, or is it intended for shutting down the machine? It doesn't seem to be used anywhere. J

Hi all, I'm pleased to announce a Xen paravirt_ops kernel available for testing at http://xenbits.xensource.com/ext/paravirt_ops/. These kernels are based on this morning's 2.6.21, along with all the paravirt_ops + Xen patches. The pre-built i386 kernel RPM is based on the FC6 configuration, and it has both Xen and VMI paravirt_ops support enabled. Unfortunately the RPM is a bit rough,

Hi all, I'm pleased to announce a Xen paravirt_ops kernel available for testing at http://xenbits.xensource.com/ext/paravirt_ops/. These kernels are based on this morning's 2.6.21, along with all the paravirt_ops + Xen patches. The pre-built i386 kernel RPM is based on the FC6 configuration, and it has both Xen and VMI paravirt_ops support enabled. Unfortunately the RPM is a bit rough,

Hi all, I'm pleased to announce a Xen paravirt_ops kernel available for testing at http://xenbits.xensource.com/ext/paravirt_ops/. These kernels are based on this morning's 2.6.21, along with all the paravirt_ops + Xen patches. The pre-built i386 kernel RPM is based on the FC6 configuration, and it has both Xen and VMI paravirt_ops support enabled. Unfortunately the RPM is a bit rough,

I have installed Ubuntu Intrepid Server on bare metal and successfully ran:- # apt-get install ubuntu-xen-server.     It installed several packages on system . Now i can see files /boot/xen-3.3.gz, /etc/init.d/xend, /etc/init.d/xendomains, but no xenified kernel gets in. Attempt  to use vmlinuz-2.6.27-7-server, obviously , fails with system panic.    I do remember recompiling  procedure for Xen

Subject: Add a sched_clock paravirt_op The tsc-based get_scheduled_cycles interface is not a good match for Xen's runstate accounting, which reports everything in nanoseconds. This patch replaces this interface with a sched_clock interface, which matches both Xen and VMI's requirements. In order to do this, we: 1. replace get_scheduled_cycles with sched_clock 2. hoist cycles_2_ns

Subject: Add a sched_clock paravirt_op The tsc-based get_scheduled_cycles interface is not a good match for Xen's runstate accounting, which reports everything in nanoseconds. This patch replaces this interface with a sched_clock interface, which matches both Xen and VMI's requirements. In order to do this, we: 1. replace get_scheduled_cycles with sched_clock 2. hoist cycles_2_ns

Hi, I am running XEN 4.1 on Debian 6 and I cannot find blktapctrl process running. xend is started. I installed XEN from 4.1 source following instructions here: http://wiki.xensource.com/xenwiki/XenParavirtOps http://wiki.xensource.com/xenwiki/Xen4.0 Should there be a blktapctrl process running in this version? The problem I have encountered is that I can create a domain on a raw disk image but

Some of these boot hooks do not need to be patched, in fact, it is better not to patch them at all and thus keep them totally private. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r dba7b8b8e43d include/asm-i386/paravirt.h --- a/include/asm-i386/paravirt.h Thu Apr 19 16:12:02 2007 -0700 +++ b/include/asm-i386/paravirt.h Thu Apr 19 16:16:19 2007 -0700 @@ -686,12 +686,12 @@ static