similar to: Bug#437127: [PATCH] hotplug: fix ip_of for systems using peer-to-peer link

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal On my systen, the script vif-common fails to retrieve the primary IP address of my ethernet device, preventing a domU from starting. I tracked this issue down to the file /etc/xen/script/vif-common. The function ip_of uses the following shell code to extract the address: ip addr show "$1" | awk "/^.*inet.*$1\$/{print

Hi, > Can you manually do on the xen interfaces what the scripts would? How about > doing it on some other interface configured in a similar way? Toying with the vif-route script, I might have found a workaround for this issue. If I disable the ifconfig and ip route commands from vif-route script, and bring up vif interface by hand later on, everything seems to work. In other works,

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341877305 -3600 # Node ID 310aa4c07d02168234a36e113a76d0d4eef373a7 # Parent 1d33f934dd675a1b91d2d4e0fa2d2a873a8debf5 hotplug: network-bridge: fix for interfaces with no gateway This comes from an old Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588477 which refers to

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341941699 -3600 # Node ID efb7fee3573b68e895de0341dd67df83cb68acc6 # Parent ca5c306052791edf6d96da3f80aecd750b86a5e4 hotplug: vif: fail if a duplicate vifname is used. This is based on a patch from Hans van Kranenburg in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658305. Quoting that bug report: When

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

Package: xen-utils-common Version: 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 Severity: important Tags: patch security -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),

Processing commands for control at bugs.debian.org: > forwarded 437127 http://lists.xen.org/archives/html/xen-devel/2012-07/msg00455.html Bug #437127 [xen-utils-common] xen-utils-common: vif-common fails to identify ip address of ethernet device Set Bug forwarded-to-address to 'http://lists.xen.org/archives/html/xen-devel/2012-07/msg00455.html'. > thanks Stopping processing here.

Processing commands for control at bugs.debian.org: > close 437127 Bug #437127 [xen-utils-common] xen-utils-common: vif-common fails to identify ip address of ethernet device Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 437127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437127 Debian Bug Tracking System Contact owner at

I did some fine tuning on the command line, and this one should be an even better alternative: ip -4 -o addr show primary dev $1 | awk '$3 == "inet" {print $4; exit}' | sed 's!/.*!!'

I can confirm the problem. The provided patch fixed it for me. Greets, Peter

Anything new here? The bug still perisists and is quiet annoying, especially when considering the simplicity of its fix. On a side note, vserver-debiantools had a similiar problem which got fixed within 2 days (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539448), while the faulty line of shell code still resides in vif-common after 2 years and several confirmations.

I agree, please fix this issue! The bug report is over two years old now. -------------- next part -------------- A non-text attachment was scrubbed... Name: saschafroehlich.vcf Type: text/x-vcard Size: 310 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20090820/ede2fd42/attachment.vcf>

Just a little tiny detail : ============================================================================== > --- trunk/scripts/hotplug/libhid.usermap (original) > +++ trunk/scripts/hotplug/libhid.usermap Fri Aug 25 19:18:19 2006 > @@ -21,5 +21,7 @@ > libhidups 0x0003 0x09ae 0x1003 0x0000 0x0000 0x00 0x00 0x00 0x00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As some of you might have noticed, CentOS 5 doesn't ship with hotplug (linux-hotplug.sourceforge.net). Things get handled directly by HAL, as far as I can tell. This is ok as long as you are using gnome/kde. However, on a TUI box, or when you are running another WM (I use IceWM here), you can't count o HAL. Actually, HAL (as shipped on CentOS

I rebooted my machine and now when trying to run a "vm ... virsh create /etc/xen/vm1.xml" I am getting the following error: libvirtError: virDomainCreate() failed POST operation failed: (xend.err ''Device 0 (vkbd) could not be connected. Hotplug scripts not working.'') I tried restaring xend and even mounting and unmounting the partition that holds the vm and still no

Hello, I am receiving script error: /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected Xen version 4.0.1-rc1-pre with pv_ops 2.6.33.3. Ubuntu 8.10 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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 have a HP370 with 16 GB memory. If I build 7 Guests everything works fine. If I start the 8 guest I get this error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I have xen 3.0.1 with PAE on Redhat 4.1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I''m using kubuntu dapper, so /proc/sys/kernel/hotplug is disabled, and instead udevd is running to get events from kernel and do what is necessary. in my first steps with xen (unstable), I get this error: root@nandemonai:~# xm create myxm Using config file "/etc/xen/myxm". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. root@nandemonai:~#