similar to: xen-hotplug-cleanup script error

Package: xen-utils-common Version: 4.0.0-1 Hi, I discovered that one of the scripts does something wrong on my squeeze machine. /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected

tail /var/log/xen/xen-hotplug.log xenstore-read: couldn't read path backend/vbd/6/768/node /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected xenstore-read: couldn't read path backend/vbd/6/5632/node xenstore-read: couldn't read path backend/vbd/6/768/node

As suggested by Andi Kleen, don't allocate a GDT page if there is already one present. Needed for CPU hotplug. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-rc1/arch/i386/kernel/smpboot.c =================================================================== --- linux-2.6.14-rc1.orig/arch/i386/kernel/smpboot.c 2005-09-20 20:38:22.000000000 -0700 +++

As suggested by Andi Kleen, don't allocate a GDT page if there is already one present. Needed for CPU hotplug. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-rc1/arch/i386/kernel/smpboot.c =================================================================== --- linux-2.6.14-rc1.orig/arch/i386/kernel/smpboot.c 2005-09-20 20:38:22.000000000 -0700 +++

# HG changeset patch # User Brendan Cully <brendan@cs.ubc.ca> # Date 1282083158 25200 # Node ID 74b9fe513d8591ca14233590062079b042abb68d # Parent 774dfc178c39bd3fe2ec14b4f96e60b78391b397 hotplug: 21549:8bcaec29574e breaks vif-script with arguments. For example, (vif-script ''vif-bridge bridge=eth1'') in xend-config.sxp will cause vif-setup to attempt to execute

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1~rc3-1 Severity: normal Hi, I upgrade one server from lenny to squeeze, to start testing xen-hypervisor-3.4 and xen-hypervisor-4.0, but it seems to don't work. The error : xm create -c /etc/xen/slhoka.cfg Using config file "/etc/xen/slhoka.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. The error

The blktap2 test in xen-hotplug-cleanup was not quite right, causing orphaned /vm/<uuid>/device node in xenstore. Attempt to reattach the device failed: xen53: # xm block-attach 0 file:/tmp/d0 /dev/xvdp r xen53: # xm block-detach 0 /dev/xvdp xen53: # xenstore-ls /vm/00000000-0000-0000-0000-000000000000/device vbd = "" 51952 = "" frontend =

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: normal With SE Linux it's desirable to give utilities and daemons the minimum privileges. That includes not permitting general utilities to create directories under /var/run. I think it would be best if /var/run/xen-hotplug was created by an init script such as /etc/init.d/xen (or by systemd-tmpfiles when using systemd units).

Hi all, I've been looking at the next steps to try to get Xen running fully on top of pv_ops. To that end, I've (just) started looking at one of the next major jobs --- i686 dom0 on pv_ops. There are still a number of things needing done to reach parity with xen-unstable: x86_64 xen on pv_ops Paravirt framebuffer/keyboard CPU hotplug Balloon kexec driver domains but it

Hi all, I've been looking at the next steps to try to get Xen running fully on top of pv_ops. To that end, I've (just) started looking at one of the next major jobs --- i686 dom0 on pv_ops. There are still a number of things needing done to reach parity with xen-unstable: x86_64 xen on pv_ops Paravirt framebuffer/keyboard CPU hotplug Balloon kexec driver domains but it

Hi all, I've been looking at the next steps to try to get Xen running fully on top of pv_ops. To that end, I've (just) started looking at one of the next major jobs --- i686 dom0 on pv_ops. There are still a number of things needing done to reach parity with xen-unstable: x86_64 xen on pv_ops Paravirt framebuffer/keyboard CPU hotplug Balloon kexec driver domains but it

I''ll try this one more time, any help greatly appreciated. When I create an HVM domain in Xen 4.0.X, network vif frontend initialization stalls at some point and the frontend/backend are never connected. This works properly in Xen 3.3.1, but does not work in either Xen 4.0.0 or Xen 4.0.1. When I start an HVM domain: 1. QEMU creates a tap device and attaches it to the specified bridge

> Added: > trunk/scripts/hotplug/Makefile.am > trunk/scripts/udev/Makefile.am > Modified: > trunk/ChangeLog > trunk/Makefile.am > trunk/configure.in > trunk/docs/configure.txt > trunk/scripts/Makefile.am > trunk/scripts/hotplug/ (props changed) > trunk/scripts/udev/ (props changed) > trunk/scripts/udev/README > Log: > -

This patch fixes IO deadlocks in the vtpm hotplug scripts. Signed off by: Matthew Fioravante matthew.fioravante@jhuapl.edu --- Changed since previous: * rebased off of latest xen stable * replaced instances of gawk with awk diff --git a/tools/hotplug/Linux/vtpm b/tools/hotplug/Linux/vtpm --- a/tools/hotplug/Linux/vtpm +++ b/tools/hotplug/Linux/vtpm @@ -1,22 +1,18 @@ #!/bin/bash +export

Overriding PATH but not LD_LIBRARY_PATH is bogus, as it may result in the use of mismatched binaries and libraries. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/tools/hotplug/Linux/xen-hotplug-common.sh +++ b/tools/hotplug/Linux/xen-hotplug-common.sh @@ -31,6 +31,7 @@ dir=$(dirname "$0") exec 2>>/var/log/xen/xen-hotplug.log export

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

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,

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 5:25 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson > (davetho) wrote: > > > >

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

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]