similar to: Can''t create my seventh xen vm on rhel5

After a yum update my two guests that had been shutdown do not start any more. I have two other guests running that seem to work okay but I am now afraid that they won't come up again if I restart them. I am running CentOS5 with kernel 2.6.18-8.1.8.el5xen. Previously I had following xen versions installed: Oct 14 23:45:10 Updated: xen-libs.i386 3.0.3-25.0.4.el5 Oct 14 23:46:05 Updated:

Hi, I have 6 DomU's with 4-virtual interfaces and 1 DomU with only one. When starting the DomU's in order where the domain with only one interface is started last it refuses to start with following error. If I start it first there is no problem starting them all. ---Error--- [2011-10-02 18:37:33 xend.XendDomainInfo 6728] DEBUG (XendDomainInfo:1335) XendDomainInfo.handleShutdownWatch

Hi, I cannot boot Windows XP domU on SXCE104 dom0. It was running for weeks.. Is it a known bug? # virsh start wxpp01 & # virsh dumpxml wxpp01 <domain type=''xen'' id=''-1''> <name>wxpp01</name> <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> <os> <type>hvm</type>

Hi all When I have a domU that resides in the auto directory I get ''Error: Device 2049 (vbd) could not be connected'' and the domain starts in a paused mode. Shutting it down and restarting has the same effect. Following is some output from the xm log and an attempted restart. Directly after dom0 reboot: xen0:/etc/xen/scripts # xm list Name ID

Hi. We are running xen-3.0-testing. We use loop back mounted file systems. The server we are running restarts itself/crashes. This seems to happen around setting up loop back devices. (>63 loop back devices seems to trigger a crash, but we have seen then with fewer devices mounted as well). We have swapped all hardware (bar the disks) to a new server. Same issue. I see no disk

Hi List, beneeth some debian domU''s I tried fedoraCore3 from xen-get... My tests are sucessfull bu I can''t reboot this domU. The domU seem to shutdown correctly but doe not start again. xm list does not show my fedore domU again and an manual xm create leads to: Error: Device 2049 (vbd) could not be connected. File /opt/xen/domains/tta/disk.img is loopback-mounted through

Hi. I''ve just upgrade my xen 3.0.1 to xen unstable. I noticed that there is no vmx driver here, only hvm. Actually I cannot start my VT domain: root@akira:/etc/xen# xm create bluszcz.hvm Using config file "bluszcz.hvm". Error: Device 768 (vbd) could not be connected. Backend device not found. root@akira:/etc/xen# my config: import os, re arch = os.uname()[4] if

Hi, I have seen many posts regarding this but have not found the soultion. So please cna someone shed some light on this Thanks - padma I get this error when I do try to create a domU guest (xen 3.0.0, 2.6.12.6). The vif is set to vif = [ '' mac=aa:00:00:00:11, bridge=xenbr0'' ] and a "brctl show" shows xenbr0 8000,fefffffff interfaces vif0.0 peth0 Xend.log

Hi, Thanks or all the suggestions. The problem was the lack of hotplug support! The problem was solved by a reinstall of the native linux (RHEL4) with selecting all packages. I had initially chosen some packages and I believe hotplug support was left off (don''t know which package it belonged to. Regards - Padma -------------- Original message ---------------------- From: Nivedita

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

Hi, I have been getting the following error (logged in /var/log/xen/xend.log) when I try to migrate a VM from one particular host to the other (the reverse migration works fine). My system was working fine for a long time (i did several migrations in both the directions). I am using Xen-3.4.3 (installed from source code) with CentOS 5.4. I am using drbd to replicate the disks.

Hi all, I installed 2009.06, xVM and happily installed a domU with no issues. I just did this through the virt-manager GUI, and kept it as simple as possible. Later I installed and booted a zone with very simple and standard configuration. My existing xVM virtual machine did not immediately stop working, or have any interruption at all. But, I can no longer create new virtual machines, or even

Hi, excuse me if this is off-topic and feel free to ingore it in case. I''m using acts_as_taggable (the gem version) and found what to me looks like a bug in this code from the method tags_count: sql = "SELECT #{t}.#{t_pk} AS id, #{t}.name AS name, COUNT (*) AS count FROM #{jt}, #{o}, #{t} WHERE #{jt}.#{t_fk} = #{t}.#{t_pk} AND #{jt}.#{o_fk} =

I''m trying to learn about XEN and am having problems .. here is what I did .. I installed RHEL 5 Linux version 2.6.18-8.1.1.el5xen (brewbuilder@ls20-bc1-13.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Mon Feb 26 20:51:53 EST 2007 I updated all of the RPMs # yum update . stuff . No Packages marked for Update/Obsoletion I updated the

Hello all, I''m using Red Hat Enterprise Linux 5 (with RH Virtualization) and a Dell Poweredge 2950 with 10 NICs. My virtual operating systems are all RHEL4, and I''ve installed 4 instances. I''m trying to set up the virtual operating systems so that the physical NICs are allocated to certain operating systems. Using the following tutorial:

Hi, I have been trying to get Xen 3.1 running on Fedora 7 since yesterday and no luck. At the beginning I thought it was a problem with teh installation of Fedora 7 so I reinstalled it. Still, I have the same problem. I have never had this problem with Xen (FC5,FC6). The xend.log (below) includes a line "VmError: Device 0 (vif) could not be connected. Hotplug scripts not working."

On 04/09/13 09:34, McEvoy, James wrote: > I have run into a problem attempting to attach the seventh virtio-scsi device to a RHEL 6.4 Guest from a RHEL 6.4 host running libvirt version 0.10.2-18. > I have a guest that is running RHEL6.4 where I can attach disks sda(boot), sdb, sdc, sdd, sde and sdf but when I try to attach sdg the virsh attach-disk command fails with the error: > error:

Folks, 4.1.0-rc7 is now tagged in http://xenbits.xen.org/staging/xen-4.1-testing.hg Please test! This is hopefully the last RC before release, which we plan to happen on Monday. Only fixes for serious blocker bugs will now be considered for this release. Thanks, Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com