similar to: CentOS 6 Xen 4.4.1 packages available on virt6-testing

On 01/06/2015 08:54 AM, Johnny Hughes wrote: > On 12/15/2014 12:24 PM, George Dunlap wrote: >> At long last, I've got some beta CentOS 6 4.4.1 packages up on the CBS. >> >> Major updates include: >> * Update to Xen 4.4.1. Also includes all XSAs through 114 >> * Update to latest blktap 2.5 >> * Updated libvirt packages (1.2.10), which work well with libxl

On Tue, Dec 16, 2014 at 10:29:53PM +0200, Pasi K?rkk?inen wrote: > > > > * xend is now disabled by default. You can enable it by running > > chkconfig. xend has been removed from the tree entirely in Xen 4.5, > > so this should (hopefully) serve as a "wake-up-call" for people to > > begin the transition over to xend. > > > > * A lot have

On 12/15/2014 12:24 PM, George Dunlap wrote: > At long last, I've got some beta CentOS 6 4.4.1 packages up on the CBS. > > Major updates include: > * Update to Xen 4.4.1. Also includes all XSAs through 114 > * Update to latest blktap 2.5 > * Updated libvirt packages (1.2.10), which work well with libxl > > To use, add the following to a file in /etc/yum.repos.d: >

On Mon, Dec 15, 2014 at 06:24:36PM +0000, George Dunlap wrote: > At long last, I've got some beta CentOS 6 4.4.1 packages up on the CBS. > Great! > Major updates include: > * Update to Xen 4.4.1. Also includes all XSAs through 114 > * Update to latest blktap 2.5 > * Updated libvirt packages (1.2.10), which work well with libxl > > To use, add the following to a file

Hello, It seems currently when you "yum update" CentOS 6.6 Xen host you end up getting python-virtinst from c6 base repo: python-virtinst-0.600.0-24.el6.noarch and not from Xen4CentOS repo, because the version there is "older": 0.600.0-19. .. which means the centos/xen-specific patch in python-virtinst is "lost". (default to tap2 instead of tap1, to make blktap2

On 01/05/2015 04:15 PM, Pasi K?rkk?inen wrote: > On Tue, Dec 16, 2014 at 10:29:53PM +0200, Pasi K?rkk?inen wrote: >>> >>> * xend is now disabled by default. You can enable it by running >>> chkconfig. xend has been removed from the tree entirely in Xen 4.5, >>> so this should (hopefully) serve as a "wake-up-call" for people to >>> begin

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

Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']

Folks, The tag 4.0.1-rc3 has been added to http://xenbits.xensource.com/xen-4.0-testing.hg Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

With slight re-ordering to keep related things together <kbsingh> lars_kurth: Hi [13:52] <kbsingh> Are we doing this meeting on irc ? <lars_kurth> kbsingh: yes, we are [13:59] <lars_kurth> gwd: Hi. [14:02] <lars_kurth> Alright. I didn't put an agenda together <gwd> I've got a couple of things I wanted to bring up. [14:04] <gwd> Who else is here

Hello, I have been playing around with Remus on Xen 4.0.1, attempting to fail-over for an HVM domU. I''ve run into some problems that I think could be related to tapdisk2 and its interaction with how one sets up Remus disk replication in the domU config file. A few things I''ve noticed: -The tap:remus:backupHostIP:port|aio:imagePath notation does not work for me, although this

Forwarding to you original patch requested. It works for me. Boris --- On Sun, 7/11/10, eXeC001er <execooler@gmail.com> wrote: From: eXeC001er <execooler@gmail.com> Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable) To: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, July 11, 2010, 9:18 AM 1. Bug fix for error: "Error: Device

On Fri, Jan 16, 2015 at 09:16:05PM +0200, Pasi K?rkk?inen wrote: > Hello, > > As discussed on the last Virt SIG meeting I promised to do some libvirt + libxl testing using the latest Xen 4.4 rpms. > > Versions used: > > xen-libs-4.4.1-5.el6.x86_64 > xen-licenses-4.4.1-5.el6.x86_64 > xen-hypervisor-4.4.1-5.el6.x86_64 > xen-4.4.1-5.el6.x86_64 >

Hi,  I''m currently stuck with creating VM which cannot boot with disk using blktap2 driver. I''ve been searching nearly a whole week and I couldn''t get a answer. When creating vm with blktap2, it keep shows a error:   libxl: debug: libxl_device.c:200:disk_try_backend: Disk vdev=xvda, backend tap unsuitable because blktap not available.  VM configuration (XML):

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:

Thanks to work from Johnny, linux 3.18.12 with all the x4c blktap goodness have been built and are now in the virt6-testing repo. I've also uploaded libvirt 1.2.15. As you may have seen earlier today, virt6-testing also includes an updated 4.4.2 package with the latest security update (XSA-133). The kernel has had some basic testing (by myself, Johnny, and another community member), but

Hi, I''ve been testing Xen 4.0.1 with kernel 2.6.34.5 + http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.34-4.tar.bz2, and one of the things that I noticed immediately is there are two problems with tapdisk and this combination. First, the syntax "disk = [''tap:tapdisk:aio: ..." no longer works. When tested with HVM domU, it boots, but there was no disk

On Sat, May 16, 2015 at 2:08 PM, Johnny Hughes <johnny at centos.org> wrote: > On 05/13/2015 01:14 PM, George Dunlap wrote: >> Thanks to work from Johnny, linux 3.18.12 with all the x4c blktap >> goodness have been built and are now in the virt6-testing repo. I've >> also uploaded libvirt 1.2.15. As you may have seen earlier today, >> virt6-testing also