similar to: Error: Device 768 (vbd) could not be connected. Backend device not found.

Hi. I am trying get use xen vmx, it shows only black window. I attach my config and logs. config: import os, re arch = os.uname()[4] if re.search(''64'', arch): else: kernel = "/usr/lib/xen/boot/vmxloader" builder=''vmx'' memory = 128 name = "bluszcz" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

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

Anybody out there running Windows XP, Windows XP SP2 or Windows 2003 server with the default XEN 3.0.3 on Ubuntu Feisty ? Have Ubuntu Feisty Dom0 with a number of Ubuntu 6.1/7.04, Debian and FC6 DomUs all working lovely. But it will not work for any windows versions. The install gets as far as the blue "Setup is Starting Windows" screen. Intel VT extensions are enabled and the F5 trick

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

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

I have loaded FC6 with the virtualizations kernel, and I am attempting to load WinXP. I searched all the logs and docs and configured what I think is correct based on these. When I do an xm create dfw11286lv1.hvm, I get the following messages: Using config file "dfw11286lv1.hvm". Started domain dfw1128glv1 However, I never get a window with the installer. Also, when I open the

Hi I m trying to install a full virtualized guest on my dell poweredge 1950 with centos 5.1 64 bits. I just launched the following command virt-install -n elaphe -r 4096 -f /var/lib/xen/images/elaphe -s 40 -b vlanbr15 --hvm Would you like to enable graphics support? (yes or no) yes What is the virtual CD image, CD device or install location? /var/lib/xen/F-7-i386-DVD.iso Starting

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

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, I am trying to install Windows 2003 server as a guest OS in Centos 5 Xen and installation is freeze , i am attaching screen shot, here is xend log file details [2007-10-29 17:04:11 xend.XendDomainInfo 3413] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'testwin'], ['memory', '1024'], ['maxmem', '1024'],

I am running Pentium D 930 with 2 gigs of ram. Fedora Core 6 with Xen enabled. I am able to start the install and it goes to the first stage of needing to be rebooted. I restart the Domain and it starts to finalize the windows install. And is fine until it starts asking for serial numbers or computer names. Then all of a sudden the guest freezes. The guest CPU goes to zero and so does the

Hi all, I''m having some problem migrating a simple domU between two hosts. Short question: xm migrate (live or not) fails even though either host is capable of running the VM. Error seems to be: "not a valid guest state file: pfn count read" Long question: I have two boxes (devvmdevvmhost1 and devvmhost2) running xen 3.0.3 (RHEL 5), they are attached to a Dell MD3000 unit

hi xen-list, i have installed xen-3.3.1 from source on a core2duo. the xen kernel boot fine. i create a file image with dd and a simple domU config file for windowsXP: import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' kernel = "/usr/lib/xen/boot/hvmloader"

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

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains

Hi all, I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2. execute steps: 1)Install fully suse 11 sp2 to host pc 2)Boot from Xen kernel menu 3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html 4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz

Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =