similar to: xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 

Hi all, Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. [ 240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds. [ 240.172388]

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, I have three Xen hosts running Xen 4.0.2 (OpenSuSE 11.4 based). I also have one ''NFS'' server with an NFS export holding VM images and configuration files. Each host has a dedicated LAN link directly to the NFS server. I have another separated NFS export for VM locking (but I had the same issues before). When I attempt to live migrate a VM, it *looks''*like

Package: xen-hypervisor-4.1-i386 Version: 4.1.1-1 Severity: important Tags: wheezy I cannot boot a domU with networking after installing the package. root at topsail:~# xm create /etc/xen/udevtest.cfg -c root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. [2011-08-03

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 everyone! I''m new with Xen and i''ve been dealing with the same error the last week. I''m pretty much lost, i don''t know what else to do so i ask for your help. In my case i installed Xen on a amd64 Pc, with Gentoo. I installed the following packages: xen, xen-tools and xen-sources from the gentoo repositories. I''m using 2.6.31-xen-r10 gentoo

Hi All, I''m having a similar issue as Ian Tobin some weeks ago here: http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html I''m using Debian Squeeze amd64, downloaded the experimental debian xen-amd64 kernel with pv_ops support. linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb

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 All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting error. I tried doing googling but none of suggested solution is working for me. For more details please see below, I have highlighted few details in bold color just for

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting error. I tried doing googling but none of suggested solution is working for me. For more details please see below, I have highlighted few details in bold color just for

I have several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution

Hi all, I''d like to know if it''s possible to have more verbose output when running a block-prefix script. Other than xend.log. To be more specific I''d like to use bash -x to see why I''m running into the following error: > # xm create -c host.cfg > Using config file "host.cfg". > aa:bb:cc:dd:ee:ff > Error: Device 51712 (vbd) could not be

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

Hi guys, actually i use the following packages from etch-backports: =========================== ii linux-headers-2.6.18-6-xen-vserver 2.6.18.dfsg.1-18etch1 Common header files for Linux 2.6.18 ii linux-headers-2.6.18-6-xen-vserver-amd64 2.6.18.dfsg.1-18etch1 Header files for Linux 2.6.18 on AMD64 ii linux-image-2.6.18-6-xen-vserver-amd64

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

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 =

Hi all Greetings from Patagonia Argentina - this is my first message to this list. I''m having a weird problem: when I reboot some domU, some OTHER domU gets killed. Scenario: > cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 1 > uname -sri Linux 2.6.32.43-0.4-xen x86_64 > rpm -qa | grep xen- kernel-xen-base-2.6.32.43-0.4.1

uname -a SunOS i7 5.11 snv_114 i86pc i386 i86xpv The box is a core i7 with 6GB of RAM. The command virt-install --name 10u7 --ram 1024 --hvm --file /guests/10u7 --os-type=solaris os-variant=solaris10 --location /export/iso/sol-10-u7-ga-x86-dvd.iso get as far as opening the VNC client, when I select Solaris from grub, the OS starts to boot then panics, closing the session. So I

>That is, I think the following config should work on those Ubuntu >systems > PYTHON=python > PYTHON_PREFIX_ARG='''' >although you may need to do > PREFIX=/usr/local >too. # make tools fails on Ubuntu 9.04 Server with Config.mk suggested above This one Config.mk (untouched) works fine:- PYTHON ?= python PYTHON_PREFIX_ARG ?=