similar to: blk_tap: Error initialising /dev/xen/blktap - No more devices

Hi, have a debian 5.0 with all patches and xen 4.3.1 (debian repo) installed. If I use a VM with paravirtualizing it works fine. But a full virtualized image doesn''t boot. Message: ---8<--- # xm create deb50.cfg: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. ---8<--- That is my deb50.cfg ---8<--- # Debian 5.0 import os, re arch = os.uname()[4]

Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was

This is on a snapshot from 11/12/2005 of unstable. I wrote some quick debug code into vif-route to see what is going on during runtime, ex: echo "xenbus_path = $XENBUS_PATH" >>/root/route.log echo "command = $command" >>/root/route.log After starting/stopping a domain a few times it contains: xenbus_path = backend/vif/20/0 command = online xenbus_path =

I am having the same problem, however on RHEL 2.6.16. I have tried setting up the bridge manually but it does not work. Can someone give some clues on what we should do to solve this problem in RHEL Thanks P. Krishna -------------- Original message -------------- From: Jens Nachtigall <nachtigall@web.de> > I found this at http://julien.danjou.info/xen.html > > Set up the

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

Hi I wrote a vif script to support openvswitch. I use it on some of my machines, so it works for non-qemu domains. Ian asked me to send it here, maybe someone wants to take a look. Bastian #!/bin/bash #============================================================================ # ${XEN_SCRIPT_DIR}/vif-openvswitch # # Script for configuring a vif in openvswitch mode. # The hotplugging system

Searching the archives and web i''ve learned that this error has occured for other users as well. I already did quite a bit of debugging but can''t figure out what the problem might be. I''m running Xen unstable (changeset 8002) on an AMD64 server (rented from 1&1). I''ve patched the 2.6.12.6 kernel with a custom patch to get network and disk adapter running,

line 52: XENBUS_PATH: parameter null or not set what the XENBUS_PATH is? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

1: is it possible to use ioemu:sda instead of ioemu:hda ? 2: is ioemu keyword optionnal ? conf seems to work without 3: why d i need to put vfb = [ "type=vnc,vncunused=1,keymap=fr" ] line ? seperate vnc = 1 + vncunused = 1 look identical to me, but are ignored. have the conf parser changed ? 4: during dom0 startup: > * Starting Xen control daemon ... > * Error: either

Hello all, I''m doing some testing with Xen and NPIV disk on the platform SLES 10 SP2 and SLES 11 (xen 3.3). On SLES 10 sp2, I have not encountered major problems during the tests (exept with live migration). I was able to attach a disk with the command "xm block-attach npiv:..." an I am also able to start a VM using a bootable NPIV disk. On sles11, after changing the script

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

Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. /etc/xen/scripts/vif-bridge handles MTU settings in the vif, but the otherwise similar /etc/xen/scripts/vif-openvswitch does not. I added it in, here's the diff-c and the full fixed file is also

Based on Waldi''s RFC at http://lists.xen.org/archives/html/xen-devel/2012-09/msg00943.html To use it set vif.default.script="vif-openvswitch" in /etc/xen/xl.conf or use script=vif-openvswitch in the vif configuration. Appears to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the

Dear Community, i have a problem with a new debian XEN 64bit squeeze Server, when i started a windows hvm domU. I tested with the routed and now in the bridge network mod. I start the domU with xm create win.cfg and 1 or 2 second the dom0 is reboot. I install a debian domU on the system, and this is without any problems in routed and bridge mod. In the logfile are no informations, in the routed

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

I just created arch linux xen 4.2 unstable package so it compiled fine and installs fine. When I run xl create it starts vm. I have vif devices created but they don''t attach to bridget that are created on startup . I have xenbr0 and xenbr1 created. If I run this I get vifi attached ro bridge. Is this xl issue or python. # export vif=vif1.0 # export

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

We''ve been noticing a lot of these errors when booting VMs since we moved to 3.0.3 - I''ve traced this to the hotplug scripts in Dom0 taking >10s to run to completion and specifically the vif-bridge script taking >=9s to plug the vif into the s/w bridge on occasion - was wondering if anyone has any insight into why it might take this long. I added some instrumentation to

I''m running SLES10 SP1 and have been using file:/ for my file-backed domUs. The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three or four XEN servers. I''m having issues with the loopback devices not being released when the domUs shutdown or migrate, so I decided to switch over to tap:aio for my file-backed domUs. This isn''t working, either.