similar to: Tap:aio not working in current unstable?

Mats, Thanks for your trial; following your mail I tried it with hda; it is the same, it does not work - "fdisk -l" does not show hda. Regards, Ian On 4/2/07, Petersson, Mats <Mats.Petersson@amd.com> wrote: > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Brown

I have never been able to get tap:aio devices running. When I try it in a Linux PV domain, it says: XENBUS: Waiting for devices to initialise: 295s... And they don''t work in my GPLPV drivers, which is the problem I am trying to solve, but I''d like to see them work under Linux first. Is there anything extra I need to do? I have loaded the xenblktap module (forgot to do this

Hi, xen-3.0.3-41.el5 on RHEL5.1 I''m trying to use tap:aio thusly: disk = [ ''file:/var/lib/xen/images/webmail.golden.net.img,hda,w'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',

Hi there I am analyzing disk performance. I'm testing raw (tap: aio) and lvm (phy :). The tests I'm doing on a SLES11SP3, cpu I7, 4GBRam, disco-SATAII 7200rpm. With phy: lvm achievement 70-80MiB / s (an acceptable value) With tap: aio: file.raw achievement 5-9MiB / s, which is very low ... 10MiB / s is what you should expect access to a tap: aio: file.raw? or I have something

I don''t know what has happened because know I can''t even get this guest booting. The guest conf I think is correct: kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen" builder=''linux'' memory = 384 name = "ns1" vcpus = 1 #vif = [ ''mac=FE:FF:FF:FF:FF:FF , ip=139.185.48.214, ''bridge=xenbr1'' ] vif = [ '''',

I am running xen-unstable (change log 23842) and linux 3.0 (ubuntu 10.10) on a Lenovo x220. I am having trouble installing ubuntu 11.04 64-bit with the following config file: builder=''hvm'' memory = 1024 name = ''ubuntu'' vcpus = 2 pae = 1 acpi = 1 apic = 1 vif = [ '''' ] disk =

I mounted an iso file like so: ------------------------------------------- # mount -o loop=/dev/loop0 /path/to/iso /tmp/mnt #ls /tmp/mnt cdromupgrade  dists  doc  install  isolinux  md5sum.txt  pics  pool  preseed  README.diskdefines  ubuntu ------------------------------------------- I used the following file to try to have pygrub boot the mounted iso: -------------------------------------------

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'']

Hello, I'm wondering if anyone out there is doing tap:aio disk devices on a Xen HVM vm with any success. Please let me know if you are, and perhaps your version info and a config file snippet. I've posted this to the xen-users list, and what I'm trying to do seems to be correct, works on Ubuntu, Debian, and XenSource; but it doesn't work on CentOS. Here's the snippet from my

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

> -----Original Message----- > From: xen-staging-bounces@lists.xensource.com > [mailto:xen-staging-bounces@lists.xensource.com] On Behalf Of > Xen staging patchbot-unstable > Sent: 24 April 2007 12:16 > To: xen-staging@lists.xensource.com > Subject: [Xen-staging] [xen-unstable] hvm rombios: Fix int15, > func 0x86 (udelay). > > # HG changeset patch > # User

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:

All, Is is possible for xm create foo.cfg to traverse a symlink to access the foo.img. Here''s an example config and the resulting error.. --- name = "jim" memory = "512" disk = [ ''phy:/dev/VolGroup00/foo,xvda,r'', ''tap:aio:/home/fred/local/jim/build/foo_swap.img,xvdd,w'',

Hello, I''m trying to test pv-grub on existing Xen 3.3.1 installation on Debian Etch Dom0. I got the following error: Unexpected error: exceptions.OSError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/sbin/xm", line 10, in ? main.main(sys.argv) File "//usr/lib/python/xen/xm/main.py", line 2884, in main

Can anyone explain to me why tap:aio sucks so badly? We''ve got numerous CentOS 5 dom0s running file-backed domUs with tap:aio. The moment any one of them starts doing something disk-intensive, idle CPU in dom0 decreases, iowait increases, and disk IO for every other domU on the system suffers. Where lies the problem, and what to do about it? Sincerely, Ray Barnes