similar to: driver domain backend vif stuck in initializing state

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

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

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:

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:

What is the best kernel to run? is it better to run 3.4.4 or one from xen git? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

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 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 =

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 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 =

On Thu February 23 2012, 12:46:46 AM, 08bit002@nirmauni.ac.in wrote: > i am working with opennebula > installed vnc in my 2 pc(nodes with Centos) > > i got this error when i tried to migrate UBUNTU_10.04.iso from pc 1(front > node) to pc 2(cluster node) [...] > PCI: setting up Xen PCI frontend stub [...] > PCI: System does not support PCI > PCI: System does not support PCI

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, ...)

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, I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and I''m facing some problems when I start the DomU. In detail, it means that the DomU IP-Adress will not be implemented in the Kernel routing table after starting the domU via "xm create /<path +configfle>" After making a "netstat -nr" it will not show the IPadress bound to the

I have a HP370 with 16 GB memory. If I build 7 Guests everything works fine. If I start the 8 guest I get this error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I have xen 3.0.1 with PAE on Redhat 4.1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi all, So i am starting a domu essentially with MiniOS and the configuration file is as follows: ################################ kernel = "path/to/mini-os.gz" #4MB is all i need memory = 4 cpus = "1" name = "Domain3" on_crash = ''destroy'' vif=[''mac=00:16:3E:00:00:01 , bridge=xenbr0, ip=10.0.0.1''] ################################

Hello, I was also hit by this problem. Perhaps it is related to the xen-netback module in the dom0 kernel? Have a look at: http://www.gossamer-threads.com/lists/xen/devel/275548 -- greetings eMHa -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL:

I have the following script, how can I implement to achieve that calculate the VIF. Thanks. U1.7km<-c(15:24) R<-c(1.2,0.2,3.6,2.5,4.8,6.3,2.3,4.1,7.2,6.1) Hm<-c(1:10) mod<-nls(R~a*(U1.7km^b)*(Hm^c), start=list(a=2.031, b=0.800, c=-0.255), trace=T) summary(mod) coef(mod) coef(summary(mod)) -- View this message in context:

I''ve just gotten xen-4.0.1-rc4-pre on top of Ubuntu 10.04 using the 2.6.32.15 kernel source installed and booting into Dom0 thanks to you guys! I was under the impression that xend would setup at least a basic bridge interface and some vif interfaces automaticlly.. I don''t get any of that. And when I try to start xend manually after reboot I get: ifdown: interface eth0 not

This is on a snapshot from 11/12/2005 of unstable. I wrote some quick debug code into vif-route to see what is going on during runtime, ex: echo "xenbus_path = $XENBUS_PATH" >>/root/route.log echo "command = $command" >>/root/route.log After starting/stopping a domain a few times it contains: xenbus_path = backend/vif/20/0 command = online xenbus_path =