similar to: Re: XEN Error Please help

hi, everyone I try to install a suse11 pv guest on redhat5.2 virtualization platform. But the startup process hung with messages: xen-vbd: registered block device major 202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise:

Hello! I have testing new xen 4.1.0 with Debian Wheezy. I have an strange problem. When I try to boot the DomU with disks in local img works Ok: disk=[''file:/VMs/plantilla-squeeze-disk.img,xvda1,w'', ''file:/VMs/plantilla-squeeze-swap.img,xvda2,w''] but when I try to boot with the same disk offered with iSCSI: (open-iscsi, login, ...)

I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950. In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64. I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues. Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my

Hi all I was reading through Xen 3 user manual and saw this tap:aio should be used instead of loopback... Then I came to do that, but I can get it working with replacing `file'' URI''s with `tap:aio''. My OS: Debian Lenny 2.6.26-2-xen-amd64 DomU Xen configuration file: kernel = ''/boot/vmlinuz-2.6.26-2-xen-amd64'' ramdisk =

Hi, I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen host but fail all the time. I''ve also searched Google and Debian as well as openSUSE resources but haven''t found any hint about my issue :-( First I''ve tried to install it as a paravirtualized guest but when the Debian installer tries to detect the disks I get this: [ 173.233735]

Hi Guys, I''m working with: 1. xen 4.1; 2. dom0 ubuntu kernel 3.2 I''m trying to run remus with disk replication (I can run without disk replication). But I read I need to use tap2 < http://nss.cs.ubc.ca/remus/doc.html>. Well... first I tried to create a pv guest. Then I take this guest.cfg: 1. name = "ubuntu-ha" 2. memory = 256 3. disk =

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

hi, Some of you might have seen the email on the centos-devel list, for the rest I just wanted to point out that we've been working on getting opennebula ( http://www.opennebula.org/ ) rpms and contextualised images for opennebula available with a very low barrier to entry for CentOS. The 'win' with OpenNebula is that its easy to install, easy to get going, scales well and mostly

Hello, I hope you don't find this email too offtopic. We have just published an expanded keynote line-up for the OpenNebula Conference 2013 (http://blog.opennebula.org/?p=4707) that includes experts from leading institutions using OpenNebula. The first ever OpenNebula Conference will be held on Sept. 24-26 in Berlin and is intended to serve as a meeting point for OpenNebula cloud users,

Hello everyone, We have just published an extended keynote line-up for the OpenNebula Conference 2013 (http://blog.opennebula.org/?p=4707) that includes experts from leading institutions using OpenNebula. The first ever OpenNebula Conference will be held on Sept. 24-26 in Berlin and is intended to serve as a meeting point for OpenNebula cloud users, developers, administrators, builders,

Hello everyone, As you may be aware, we are holding the first OpenNebula Conference [1] in Berlin, this 24-26 September. The conference is the perfect place to learn about practical Cloud Computing, aimed at cloud users, developers, executives and IT managers to help them tackle their computational and business challenges. The goal is to foster fruitful and educational discussions around Cloud

Hi everybody, I am using Opennebula 3.6 on a Debian Squeeze system. My configuration: Node-A kvm --version QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard virsh --version 0.9.11.3 Node-B kvm --version QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard virsh --version

I am trying to setup a driver domain for a NIC. I have passed through the device successfully and set netif=1 in the driver domain config. I also added the config to a guest domain vif=[''backend=7''] (7 is the ID of the driver domain) xenstore-ls /local/domain/7/backend/vif shows that the state of the device is 1 (initializing) (see below the email for the output) On the guest

Hello, ok, I found that cpu pinning was wrong, so I corrected it to be 1:1. The issue with iozone remains the same. The spec is running, however, it runs slower than 1-NUMA case. The corrected XML looks like follows: <cpu mode='host-passthrough'><topology sockets='8' cores='4' threads='1'/><numa><cell cpus='0-3'

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:

> Just making sure.. you''re running Xen 4.1 ? > The userspace qemu blkback implementation is *only* in Xen 4.1 .. > And it should get used automatically if dom0 kernel blkback is not available. Attempt of DomU install env above :- # xl create -c f14.install Parsing config file f14.install Daemon running with PID 3411                             [    0.000000] Initializing

Hi all, I am in a bit of a fix here, I have several Guests paravirtualized running on a Dom0 that is currently running the 2.6.18-92.1.22.el5xen Kernel. All my guests (administered by different people) have subsequently been updated to later versions of the kernel (namely 2.6.18-164.el5xen or 2.6.18-128.4.1.el5xen). Ones that are still running are using the Kernel 2.6.18-128.4.1.el5xen while

hi, i am trying to install xen hypervisor for opennebula on centos 6. 1. i tried installing in it but when i reboot the system with xen kernel the system doesn''t get booted. 2. i tried it again on a different system and now the package for xen is not available for yum installation. please provide me a proper set of instructions as to how to install xen hypervisor for opennebula.

Hi everyone I'm trying to create a virtual machine using OpenNebula [1] on a centos 6.4 server, but i'm facing some erros using kvm / libvirt. This server is running on a virtual machine created on XCP. Then, my infrastructure is: XCP 1.6 (hypervisor - dom0) + CentOS 6.4 (running on a XCP VM) + OpenNebula 4.0.1 (installed on CentOS). In the host machine, I have the same infrastructure.