similar to: arch linux xen 4.2 no network

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, is there any possibility to get a XEN DomO and DomU running with bridget and routed mode together. The reason behind this is, to get the requests via the official IPs to the DomU''s (routed-mode) and the interworking between the DomU''s with connected with help of the (bridged-mode). I got it work, with setting everything up manually. But as I understood the

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 =

Hi all, My NT environment cannot recognize my SAMBA servers(Bad IP address when ping from MS DOS prompt) and after I restarted the nmbd daemon it can see my SAMBA servers. Does anyone know why this happens? Is it there is a change in the WINS server's database? Please advise. thanks & regards, Bridget

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. Please, I'd like to know if somebody can help me with this problem. I have successfully configured a PBX with Asterisk 1.4 and a Digium analog card with 4 ports. This PBX has a lot of incoming and outgoing calls, and works perfect in general, but there are some extrange cases where an incoming call is bridget with an outgoing call, and the caller that is calling TO the PBX can

Hi, One of my users is having this problem. He saved an MS Excel file on the UNIX disk and he always experienced cannot write to the file even if it is his file. I am not sure if this is the SAMBA problem or the NT problem(we are using Windows Terminal Server Edition). Sometimes, he experiences these message "cannot open read only file" or "this file is opened by administrator,

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.

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

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]

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

Hi There, I''ve installed xen 3 and xen-tools on my Debian etch server and all seems well, until I try to start a guest domain. debian:/home/xen# xm create /etc/xen/D4G3.cfg Using config file "/etc/xen/D4G3.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. I get the error: "Error: Device 2049 (vbd) could not be connected. Backend device

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

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

Hello, i am experiencing something weird on my Xen Dom0 Since a few days, i can no more install or reboot any vm using tap:aio driver My vms complains about no mounted disks OS: On openSUSE 11.2 (x86_64) with xen-tools-3.4.1_19718_04-2.1.x86_64 kernel-xen-base-2.6.31.8-0.1.1.x86_64 xen-libs-3.4.1_19718_04-2.1.x86_64 kernel-xen-2.6.31.8-0.1.1.x86_64

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