similar to: iscsi throughput in DomU

Hello everyone, I just put together a brand new system, and I''m getting the following when I try to start a domU: > [ 1902.049066] xend[12924]: segfault at b9ff6cd8 ip 00007f36c474afe1 sp 00007f36b9ff6af8 error 4 in libxenguest.so.4.0.0[7f36c4730000+24000] This is on an AMD CPU with the AVX instructions, and I already have this in my grub.cfg: > multiboot /xen-4.1.2.gz

Hi all, Is anyone successfully running/has succesfully upgraded to 2.6.32-220 from, say, 2.6.32-71.29.1? (i.e. done a normal run-of-the-mill yum update on, say a 6.0 instance all the way up cleanly to 6.2? Reason I ask is that booting into -220 (and I think also into -131 as well) results in a kernel panic for me. Some digging around and the new kernel seems to be enumerating the drives with the

Hello xen-users, I am trying to access a guest disk that was created using qcow-create from dom0 using xl block-attach/block-detach, which appears to be the current "Xen way" of doing it. However, after the following command, no /dev/xvdb is appearing: $ xl block-attach 0 tap:qcow2:/home/root/images/test.img xvdb I am using Xen 4.1.2 (installed from source tarball) with an Ubuntu

hi xen 4.0.1 w/2.6.32.41 Last week dom0 experienced an hard crash and box need to be restarted manually (despite kernel.panic=20). Serial console was not setup, only netconsole. No relevant entries through netconsole, but analyzing logs I see some crashes twenty minutes before fatal hang. Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.011963] Call Trace: Dec 2 01:29:39 xenhost-rack1 kernel:

Package: xcp-squeezed Version: 1.3.2-11 Followup-For: Bug #682202 ?I found race condtion between xcp-sqeezed and /etc/init.d/xen scripts. If sleep 10 added to xcp-sqeezed host (xcp-sqeezed and xapi) initialize normally, and if not with some probability sqeezed/xapi failed to start with message: Oct 9 16:45:57 xenhost-1 xapi: [ warn|xenhost-1|0 thread_zero|server_init D:1691a70e8b4a|startup]

Hello, maybe I''m stupid but I find no way to have the kernel in Dom0 instead of DomU for Centos 5. Here is what I did: Regular Centos 5 Dom0 install, then creating a LVM group (vms) and install DomU with virt-install works perfectly: virt-install --p --location=http://mirrors.kernel.org/centos/5/os/i386 --file=/dev/vms/centos5_data --name=centos5 --ram=512 --nographics I get a

I've got a Digium PCI telephone card that I'm trying to use with an AsteriskNow guest, on a CentOS 5.2 host. I've tried setting up the pciback stuff, and think I've done it right, but the card does not show up in the guest. I'm obviously missing something, so any help (including ways to debug this!) would be greatly appreciated. Here's some more info: The guest is

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without

Hey guys, what I am trying to do is a chainload into grub2 installation in a DomU. So far I determined, PV-GRUB does not understand grub2''s grub.cfg notation. So I created a dummy menu.lst which has the needed root kernel and initrd rows and then referenced this to the DomUs config. The main intention to do this, is to be able to use kernel upgrades without touching the menu.lst for

Hi everybody, I have the following the setup for a domU: bootloader = "/usr/bin/pygrub" memory = ''4096'' vcpus = 4 root = ''/dev/md0 ro'' disk = [ ''iscsi:iqn.2008-09.com.example.node1:server1,xvda,w'', ''iscsi:iqn.2008-09.com.example.node2:server1,xvdb,w'' ] name =

Hello all, I am attempting to use the 'virsh attach-device' command to add storage to a guest from a pre-defined iSCSI-based storage pool. My desire is to attach a volume from the storage pool and have the storage pool recognize that the volume is in use and either flag it as such, or remove it from the pool so that subsequent queries to the pool will only return available storage

Hi, I am running Xen 3.3.1 built from Source with Debian Lenny as the dom0. Everything works fine so far except pyGRUB. So, what I did was install CentOS (latest version ... 5.3 or something) using qemu to a LVM logical volume and from within CentOS I installed the Xen Kernel. Now pyGRUB shows me 3 grub entries: 1) CentOS (2.6.18-128.1.10.el5xen) <= xen hypervisor 2) CentOS

For those wanting to know how to mount filesystems through blktap2 here is how you do it, as I couldn''t find it fully documented. The instructions on the blktap2 readme file are rather out of date. You can mount them under Dom0 like so. e.g. to mount a vhd file, sudo xm block-attach 0 tap2:vhd:/home/xen/xenwin7-persist.vhd xvdb w 0 Now the device should appear under /dev ls

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when

hi, does someone tried bridge and or router functionality of linux kernel on multiprocessor system. Does multiprocessor system increase network performance or give ability to process higher traffic.. What about highest possible troughput someone have achieved ? etc.. tia _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl

I accidentally realized today that any domU''s using the paravirt disk driver potentially suffer from poor performance when they get handed in a physical volume and partitioning is done inside the guest. The physical volume passed in has to be one that has the compat 512 logical sector size but hints its real sector size (eg. 4096) as physical sector size. In dom0 handling is correct and

We just reported to xenbus that we can't close yet, because blkfront is still in use. So we shouldn't then immediately state that we are closing. Signed-off-by: Andrew Jones <drjones at redhat.com> --- drivers/block/xen-blkfront.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c index

We just reported to xenbus that we can't close yet, because blkfront is still in use. So we shouldn't then immediately state that we are closing. Signed-off-by: Andrew Jones <drjones at redhat.com> --- drivers/block/xen-blkfront.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c index

We just reported to xenbus that we can't close yet, because blkfront is still in use. So we shouldn't then immediately state that we are closing. Signed-off-by: Andrew Jones <drjones at redhat.com> --- drivers/block/xen-blkfront.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c index