similar to: Testing the kernels

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

Hi I need to use hypercalls from HVM domain (e.g. HYPERVISOR_add_to_physmap). However, it does not work when I am trying to invoke it from HVM Linux guest. Basically, I don''t see that anything happens on hypervisor''s side. I also grep''ed the guest code for ''vmmcall''/''vmcall'' and did not find anything. Is it possible to do it at all?

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

The kernel patch queue used by the Xen Cloud Platform domain 0 has been published at: http://xenbits.xen.org/XCP/linux-2.6.27.pq.hg This kernel has been the recipient of extensive testing and performance optimization and is actively maintained with the latest stable drivers. There is ongoing work to merge patches which are not currently upstream into the paravirtops tree or to remove the

The kernel patch queue used by the Xen Cloud Platform domain 0 has been published at: http://xenbits.xen.org/XCP/linux-2.6.27.pq.hg This kernel has been the recipient of extensive testing and performance optimization and is actively maintained with the latest stable drivers. There is ongoing work to merge patches which are not currently upstream into the paravirtops tree or to remove the

Hi, I have noticed that, in the code of linux/drivers/xen/balloon.c, there exists the snippet as this: static int __init balloon_init(void) { unsigned long pfn; struct page *page; if (!xen_pv_domain()) return -ENODEV; ..... } Does it means the driver will not work in HVM? If so, where is the HVN-enabled code for that? 2010-11-16 Rui Chu _______________________________________________

Ian, I came across the subject line on a 96GB server with over 85 VMs running. Completely frozen and unresponsive, qemu-dm processes hung on event channels. I''m using the XenServer 6.0 dom0 kernel on top of the xen-unstable tip hypervisor. I believe you solved the issue backporting some event channel patches to the 2.6.32 kernel, as described in this thread

Iirc I derived this from a prior commit from either Ian or Jeremy. Didn''t really check it out, so there''s very likely a more correct fix than what''s attached here. /local/exp/dns/scratch/xenbits/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/time.c: In function ''xen_setup_timer'':

> Mon, 12 Apr 2010 19:02:12 +0300 <pasik@iki.fi> wrote: > > On Mon, Apr 12, 2010 at 11:55:49AM -0400, Mike Viau wrote: > > > > > > > > > Can you please paste the full boot messages before it locks up? > > > > > > > > > > > > > > > > > > Unfortunately no, because I am not getting any

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1284113350 -3600 # Node ID 635270fe858be62c02ec2bf2cacd5fc7e2492a36 # Parent ef7166e5640fd50c3041435f9233e3abcf12f698 disable kernel build in Xen build system. Cloning and building a kernel as part of the Xen distribution implicitly advises that this kernel is the best kernel for all users and many users appear to be

Hello, Finally I managed to get a xen 4.0 working on ubuntu 10.04 with pvops kernel and libvirt. However I am having some problems with networking... after initial installation with netinstall image in hvm mode, when I transform the vm in xen pv (via pygrub with the current ubuntu kernel), networking startEd to act weird... Basically I''m not using a network script from xen. I define a

Hello, Finally I managed to get a xen 4.0 working on ubuntu 10.04 with pvops kernel and libvirt. However I am having some problems with networking... after initial installation with netinstall image in hvm mode, when I transform the vm in xen pv (via pygrub with the current ubuntu kernel), networking startEd to act weird... Basically I''m not using a network script from xen. I define a

Hi everyone, I am very excited to see that dom0 pvops is finally coming close to working, so I wanted to give it a try. >From the description it was not clear to me which kernel to chose as base for the patches.hg, so I took the latest (that was ~ 2 weeks ago) kernel on git.kernel.org I could find (post-2.6.28 git tip at that point). I managed to more or less apply all of the patches in the

Hello, The topic is self-explanatory: how to ensure that a PV driver domain correctly prepares its PCI devices for S3 sleep? If I do "pm-suspend" in dom0, and the driver domain has active network interfaces, suspend hangs the system. Yes, in case of this particular machine, suspend works fine when there is no driver domain. It is possible to manually invoke scripts from

In the spirit of improving communication of Fedora Xen plans to the world, below is a mail I recently circulated in the Fedora community about the direction for Xen-ified kernels from Fedora 9 and onwards. The short story, is that we intend to ship hypervisor & userspace based on Xen 3.2.0 tree, and a kernel based on latest LKML pv_ops tree and patches ontop of that to support Dom0 and

Hi Jeremy, I backported the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen: