similar to: Long delay between xen/HVM domU shutdown and releasing vbd (drbd)

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

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Rebooting from inside domU hangs in initrd: Begin: Waiting for root file system... ... Root file system is not available because underlying DRBD device got deactivated during reboot: $ cat /proc/drbd version: 8.0.13 (api:86/proto:86) GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by phil at fat-tyre, 2008-08-04

Control: tags -1 +moreinfo On Wed, 24 Sep 2008 17:19:08 +0200 Valentin Vidic <vvidic at carnet.hr> wrote: > Package: xen-utils-3.0.3-1 > Version: 3.0.3-0-4 > Severity: normal > > > Rebooting from inside domU hangs in initrd: > > Begin: Waiting for root file system... ... > > Root file system is not available because underlying DRBD device > got

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

Hello List, i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working. Here is my config: ---------------------------------------------- kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''128'' root = ''/dev/sda2 ro'' disk = [ ''drbd:pgone-disk,sda2,w'' ] name

Hello all, I''ve just installed a new dom0 with openSUSE 11.3 (x86_64) and I''m seeing domUs crashes when reading from disks. The problem occours when in domU configuration I use memory=1024 maxmem=2048 My setup is DRBD on LVM on Software RAID 10 and drbd devices are used as disks for domUs, using phy:/dev/drbd0,hda,w phy:/dev/drbd1,hdb,w The domU in test is HVM, I''m

Error: Device 2051 (vbd) could not be connected. Hotplug scripts not working. Hello xen users,                  i got the following error Device 2051 (vbd) could not be connected. Hotplug scripts not working. my xend log (last part)looks like this [2007-06-06 12:49:44 32539] DEBUG (__init__:1094) Storing domain details: {''console/ring-ref'': ''187566'',

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

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

Hi Everyone, I''m trying to get Xen to use a native DRBD device but it seems it will not create the virtual machine. It does not seem to like the DRBD device type, any ideas on what might be wrong? I''m pretty sure my xen config file is OK and the DRBD device looks fine too. Full details below. xm create centostest Using config file "./centostest".

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''m a sysadmin and I''ve installed on my server Red Hat Enterprise Linux 5 to use its xen embedded with six virtual machines just created and running. Now I have a problem: when I attempt to create my seventh virtual machine, xen gives me this error: Error: destroyDevice() takes exactly 3 arguments (2 given) In /var/log/xen/xend.log find this errors: [2007-11-13 11:34:00

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, when installing windows server 2008 Std hvm I get always a blue screen telling me: ''a clock interrupt was not received on a secondary processor within the allocated time interval'' I googled around and found, that this occured with vista as well: http://lists.xensource.com/archives/html/xen-changelog/2007-01/msg00170.html Config is: + virt-install --name=win2008ss

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

After a few times of building xen by source, I can''t start domU anyway. I tried "yum erase xen kernel-xen" and "yum install xen kernel-xen" again, but the problem is still exist. There are xenstore-write errors in /var/log/xen/xen-hotplug.log: xenstore-write: could not write path backend/vbd/1/2050/hotplug-error xenstore-write: could not write path

I sent before few days. However, anyone did not comments. So, I resend this patch series. I hope to response for this patch series. This patch series provides the function to display VBD information through xentop. VBD information will be possible to get through sysfs which is locale in /sys/devices/xen-backed/vbd-x-xxxx, by previous patch. In this patch series, libxenstat collects these