similar to: [PATCH] linux: Allow actually using CONFIG_XEN_BLKDEV_TAP=m

Hi tinc list members, There were some problems with Ivo's email adresses (both zarq@iname.com and zarq@spark.icicle.dhs.org) so I resent the stuff to the mailling list. ============================================= Hi Ivo, Hier is een oplossing voor een bugje in flush_queue(), en ook wat andere troepjes zoals een tincd scheduler. Dit werkt wat beter, omdat de

All the resources allocated based on xen_blkif_reqs are global in blkback. While (without having measured anything) I think that this is bad from a QoS perspective (not the least implied from a warning issued by Citrix''es multi-page-ring patches: if (blkif_reqs < BLK_RING_SIZE(order)) printk(KERN_WARNING "WARNING: " "I/O request space (%d reqs) < ring

As usual, written and (build-)tested on 2.6.27.4 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-11-04/drivers/xen/blktap/blktap.c =================================================================== --- head-2008-11-04.orig/drivers/xen/blktap/blktap.c 2008-10-01 16:35:04.000000000 +0200 +++

Can''t seem to fully boot a domU on either EM64T or Opteron with x86_64 xen-unstable. Both systems'' report this from xen: (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000100. (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000102. (XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR(00000000c0000080. They boot

hi, i''m trying move from file: based disk to tap:aio but things don''t work i have centos4 dom0 with centos4 domU xen 3.0.4-testing changeset: 13138:d401cb96d8a0 self compiled [root@xen linux-2.6.16.38-xen]# grep XEN_BLKDEV_TAP .config CONFIG_XEN_BLKDEV_TAP=m config disk = [ ''file:/var/lib/xen/test.img,hda1,w'',

Hi, Here is the refreshed version of the multi-page ring patch for blkfront and blkback. I currently don''t have time to refresh the blktap part of the patch. The patch should apply cleanly to the following changeset in the linux 2.6.18 tree: changeset: 752:0b859c9516ba tag: qparent parent: 751:6591b4869889 parent: 748:5012c470f875 user: Keir Fraser

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

Cannot use virt_to_machine() on a kmap()-ed address. As usual, written and tested on 2.6.24 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-01-28/arch/i386/mm/hypervisor.c =================================================================== --- head-2008-01-28.orig/arch/i386/mm/hypervisor.c 2007-10-19

I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning:

Do we want to move the Xen4CentOS kernel to new LTS 3.10.x from the current 3.4.x Kernel? If so, can we start testing the that kernel build? Is someone from Xen.org working on porting the xen specific patches that are required in the 3.10.x kernel from the ones we have in the 3.4.x tree in Xen4CentOS? The only one I know we need is the blktap module. I have created a new spec that builds a

Hello List If i have a PCI=[08:00.0](example) in any DomU config file the xm shutdown <ID> shuts down this DomU and the Dom0! Otherwise i shutdown this DomU from inside the DomU with halt or shutdown -r now, the Dom0 shuts down to. This happend on Xen 3.4.2 and Xen 4.0 (Kernel 2.6.18.8-xen, 2.6.18.8-xen0) The Operating System to Compile xen was Debian Lenny and the Dom0 os. Without

Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28

refactoring balback Signed-off-by: Ronghui Duan <ronghui.duan@intel.com<mailto:ronghui.duan@intel.com>> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c index 73f196c..b4767f5 100644 --- a/drivers/block/xen-blkback/blkback.c +++ b/drivers/block/xen-blkback/blkback.c @@ -64,6 +64,11 @@ MODULE_PARM_DESC(reqs, "Number of blkback requests to

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

I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64 bit version using the tutorial at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/ on a Lenovo thinkcentre workstation. When I boot I get a kernel panic. If I boot the Linux kernel that I compiled using the

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

Hi, I''m trying to run Xen 3.0 on my amd64 UP machine. So far xen0 is working fine but there is a problem with mounting rootfs on xenU kernel. Is there something else that needs to be compiled into xenU 3.0 kernel? $ grep XEN kernel-xenU-x86_64-3.0.config CONFIG_XEN=y CONFIG_ARCH_XEN=y # XEN # CONFIG_XEN_PRIVILEGED_GUEST is not set # CONFIG_XEN_PHYSDEV_ACCESS is not set

I setup Xen 3.1 on a etch 32 bit box with amd64. I compile the standard Kernel from Xen and on the other way the gentoo 2.6.20 for both dom0 uand domU. The Xen Setup was bridged. But if i download a tar file, i cant extract it cause of the following error: 09:48:35 (8.66 MB/s) - `xxx.tar.gz'' saved [64985129/64985129] tar: Skipping to next header gzip: stdin: invalid compressed

I''m getting this message (subject line) in daemon.log every time I start or restart xend. I''m not sure if this is related to the fact that I cannot boot up my Windows domU from a VHD file. The Windows domU was working fine with Xen 4.0.0 (with 2.6.32.14 dom0 kernel). When I upgraded to Xen 4.0.1-rc4 (with 2.6.32.16 dom0 kernel), I can no long boot the Windows domU from VHD. The