similar to: [Xen-devel] State of Xen in upstream Linux

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 all, I'm hoping to get the Xen paravirt_ops implementation into the kernel very soon. I've been doing regular post/refine cycles, and I think its now very close to something that will be accepted. The principle concern at this point is that there haven't been very many people actually running the code. So this is where you come in. I'd appreciate it if people could grab the

Hi all, I'm hoping to get the Xen paravirt_ops implementation into the kernel very soon. I've been doing regular post/refine cycles, and I think its now very close to something that will be accepted. The principle concern at this point is that there haven't been very many people actually running the code. So this is where you come in. I'd appreciate it if people could grab the

Hi all, I'm hoping to get the Xen paravirt_ops implementation into the kernel very soon. I've been doing regular post/refine cycles, and I think its now very close to something that will be accepted. The principle concern at this point is that there haven't been very many people actually running the code. So this is where you come in. I'd appreciate it if people could grab the

hi, has anyone attempted to add grant tables, blockfront or netfront support to mini-os recently? Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''m experiencing total grant table corruption on a system and I''m hoping my symptoms will ring a bell with a member of the Xen developer community. The setup is Xen 4.0.0-RC2 (OpenSUSE 11.2 package) on a Nehalem system. The sole guest instance is 64bit FreeBSD running in HVM mode, a single vcpu, and a PCI passed-through LSI Logic 1068e SAS controller. FreeBSD is running

Hello, ????????at the beginning I want to underline that I've read SpeeX documentation and did some tests. I know that SpeeX was designed for networks in which packets arrive without errors, or don't arrive at all. SpeeX is very attractive if we consider low bit rates. I need to use SpeeX in very noisy environment, where speech quality doesn't matter, I'm interested in 2kb/s

Hello, More information and a patch for the bug. -- Pasi ----- Forwarded message from George Dunlap <George.Dunlap at eu.citrix.com> ----- From: George Dunlap <George.Dunlap at eu.citrix.com> To: Jan Beulich <JBeulich at novell.com> Cc: Sander Eikelenboom <linux at eikelenboom.it>, Jeremy Fitzhardinge <jeremy at goop.org>, Yunhong Jiang <yunhong.jiang at

----- Forwarded message from Keir Fraser <keir.fraser at eu.citrix.com> ----- From: Keir Fraser <keir.fraser at eu.citrix.com> To: "xen-devel at lists.xensource.com" <xen-devel at lists.xensource.com> Cc: "Dugger, Donald D" <donald.d.dugger at intel.com> Date: Fri, 21 Nov 2008 13:02:26 +0000 Subject: [Xen-devel] Linux 2.6.27 temporary tree on xenbits

>I probably shouldn''t have been operating machinery yesterday. >The crash is probably because I committed the e820 memory rearranging >stuff into the wrong branch, but something may have broken us from >tip/master as well. >   J Kernel was already broken at 2/28/09 --- On Sat, 2/28/09, Marc - A. Dahlhaus <mad@wol.de> wrote: From: Marc - A. Dahlhaus

Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: xen-devel@lists.xensource.com Cc: netdev@vger.kernel.org --- drivers/net/xen-netfront.c | 34 +++++++++++++++++++--------------- 1 files changed, 19 insertions(+), 15 deletions(-) diff --git

And also put my name behind the mainternship. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> --- MAINTAINERS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 0358a3e..e2252fc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -193,8 +193,9 @@ F: xen/include/xen/iommu.h LINUX (PV_OPS) M: Jeremy Fitzhardinge

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [

On Fri, May 24, 2013 at 02:59:05AM +0000, Gonglei (Arei) wrote: > Hi, > > > > > On Thu, 23 May 2013, Gonglei (Arei) wrote: > > > Hi, all > > > > > > I use O_DIRECT to open disk images for IDE, but I'm failed. After debug, I get > > the below logs: > > > [2013-05-22 23:25:46] ide: CMD=c8 > > > [2013-05-22 23:25:46] bmdma:

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become