similar to: Error: Device 2051 (vbd) could not be connected. Hotplug scripts not working.

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

Hardware: Dell Poweredge R510 (32G ram, 8 CPU- Xeon) 64bit - xen 4.0.1 stable 64bit - 2.6.32.18 dom0 (.config attached) running Ubuntu 10.04 32 bit - 2.6.18.8 domU (.config attached) running ubuntu 8.04 domU has 3 tap2 disks, on lvm snapshots. domU has 2G mem, 2 VCPU workload on domU - ssh + top running, destroy domain -- This works . But, If i run a heavier workload say postgres db (just

If I start a domain with a number of vbd devices, it''s a crap shoot if they''ll all show up in the domU''s /proc/partitions. I''ll eventually see all the devices if I keep rebooting the domU. The value of /local/domain/$DOMID/device/vbd/*/state are all 1 for the missing devices, and 4 for the ones that show up. When it works: domU:~# cat /proc/partitions

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

Hi, since I upgraded from Lenny, DRBD VBD scripts not works at all. This config works : disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ] But his one doesn't work at all : disk = [ 'drbd:ads-disk,xvda,w' ] I obtain this error : # xm create ads.cfg Using config file "/etc/xen/ads.cfg". Error: Device 51712 (vbd) could not be connected. Hotplug scripts

Hi, I am running Xen 3.1 on Ubuntu Gutsy, AMD64 distro. When I try to migrate a Windows XP domain, the domain migrates, but does not get restored in the destination node. The block device is provided by open-iscsi/iet and is accessible from both nodes. Below are logs from both source and destination nodes: Please throw some light on where the problem could be: TIA, Regards, -- Shuveb Hussain.

Hello, My name is Fermín Galán. I have started recently to use Xen (so please forgive me in advance if I''m too "newbie" :) and I''m facing my first problems... I''m trying to create a domU, but I''m getting an error: tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected.

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 first of all, thank you for a great project i really enjoy! ok, now here comes the bug report... i''m trying to test xen migration capabilities, with xen-3.1, hand compilled, fetched from mercurial repository. my setup looks like this - x86_64 dom0, x86_32p dom0, x86_32p domU. when trying to migrate from 64 to 32 bit dom0 i''m

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

Xen Host Server OS: SLES10 Kernel: 2.6.16.21-0.8-xen x86_64 Hardware: Sun 4200 Memory: 12Gb Guest Domains (2 total) RHEL4-U3 2.6.16-xen x86_64 2Gb Swap 4Gb RAM 2 Nics bridged to seperate physical Nics (Public and Private) Systems come up normal and we are able to mount filer space to the guest domains and do work. However, at some point, the guest

Hello everyone, for research purposes I''m working on Xen 3.0.3 and trying to make some modifications to Xen migration. By looking at the documentation, I''ve learned that the part I''m interesting in are handled by two binaries (xc_save and xc_restore), so I thought about modifying just this two binaries instead of recompiling the whole Xen everytime, so what I do is just

I seem to be having trouble getting the NFS root filesystem to mount after the kernel boots. As per thread from 2002 16 January (http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I double checked my DHCP config files, but to no avail. It cannot seem to attach to the mountd port on the bootserver. Here is some output from the kernel: loop: loaded (max 8 devices) Intel(R) PRO/1000

Hello, I have deployed Bugzilla 3.6.2 on CentOS 5 (with rpmforge perl-* packages) and I have a problem with SELinux preventing mail being sent via sendmail. (see SELinux reports below, especially the second one) When SELinux is in permissive mode, mail sending from Bugzilla is working properly. Has anybody got recent Bugzilla to work with SELinux on CentOS? Thanks in advance! Mathieu

Hi there guys. I''m trying to setup an Ubuntu 9.04 DomU, it boot fine, but does finishes to load completelly, this is what I get. I''m using xen 4 Linux netwarrior 2.6.31.13 #7 SMP Wed Jun 30 18:09:49 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linu * Skip starting firewall: ufw (not enabled)... [ OK ] * Configuring network

Hi, I''m running a two node xen-Cluster with CentOS 5.3. I''m using gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP for Dom0 (xen 3.0.3). Live migration works fine as long as the DomU guest is running CentOS 5.3 or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is running the current 2.6.9-78.0.17.EL.cern kernel, the migration

Dear All, am new to xen and recently implemented it. i had some issues initially but googling arround and some wise replies from you guys out there managed to clear them. now I have 2 virtual machines on my xen domains one is windows 2003 and other windows2008 both the virtual machines were working fine for about a week jus 2 days back we had a change in our network . i mean we rearanged the

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

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 Severity: normal Tags: squeeze -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-i386 depends on

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