similar to: [RFC] openvswitch support script

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

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

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

When i try to compile xen 3.0-devel with "make world", i''ve got the following compile error: gcc -m32 -march=i686 -Wall -W -g -Wp,-MD,.xenstore_read.o.d -I../../tools/libx c -I../../xen/include/public -I../../xen/include/public -I../../linux-2.6-xen-sp arse/include/asm-xen/linux-public -c -DCLIENT_read -o xenstore_read.o xenstore _client.c xenstore_client.c:16:16: xs.h: No

Hi, the vif scripts (vif-route, vif-bridge, etc.) that come with xen just don't work for me. I don't feel like I need a bridged setup. My ISP insists of routing the IPs of the domUs to my dom0. So now I'm using script=vif-route. But it has some caveats ... The vif-route script turns on proxy_arp, even though the domUs use the dom0 as a default gateway, for everything except their own

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1297182367 0 # Node ID a46b91cd8202726aecd9ddefd8e75faff48144d6 # Parent deaa7bc1a7ff6cfad7865394cb8b7205741004c9 libxl: allow guest to write "control/shutdown" xenstore node. The PV shutdown/reboot/suspend protocol requires that the guest acknowledge a request by clearing the node therefore it is necessary

On Thu, 14 Jul 2016, Dmitri Stepanov wrote: > Some of those hosts haven't NUT including upsmon (and other software > which is not included by suppliers of the hosts) for a number of > reasons. I don't need to inform not-NUT hosts about any UPS events, > etc... but only shutdown all the hosts after upssched timer expired. So > I think shutdown them via ssh would be

On Sun, 8 May 2016, Min Wang wrote: > Hi > centos 6.3 uses traditional SysV script ( not systemctl) > > here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown File /etc/init.d/ups is an administrative script which is used to set up the nut daemon - I was looking for a run-time script called by systemd, but since there is no systemd, could you run the attached

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

This patch moves some dom0 variables and backend device configuration from frontend directories to /local/domain/<backdomid>/backend or /vm. Also, - the first console is created as a xend device and moves from console/0 to device/console/0 - /vm_path/<domid> is introduced, referencing the /vm path - /vm_path/device/backend holds the backend device location, rather than storing it

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

This patch exposes a generic interface which can be expanded in the future to implement USB for PVUSB, qemu, and stubdoms. It can also be extended to include other types of USB other than host USB (for example, tablets, mice, or keyboards). For each device removed or added, one of two protocols is available: * PVUSB * qemu (DEVICEMODEL) The caller can additionally specify "AUTO", in

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

We don't have to always extract all files from the OVA archive. The OVA, as defined in the standard, is plain tar. We can work directly over the tar archive if we use correct 'offset' and 'size' options when defining the backing file for QEMU. This puts much lower requirement on available disk space. Since the virt-v2v behaviour for OVA input now depends on QEMU version

HI in centos: C="/usr/bin/upssched-cmd" here is the output of that file: # more /tmp/NUT.report NUT configuration 2016-05-10 03:02:20 UTC ########### /etc/ups/nut.conf ########### MODE=netserver ########### /etc/ups/ups.conf ########### [cyberpower] #driver = powerpanel #port = auto driver = usbhid-ups port = auto vendorid = 0764 desc = " My main

# 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

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

We don't have to always extract all files from the OVA archive. The OVA, as defined in the standard, is plain tar. We can work directly over the tar archive if we use correct 'offset' and 'size' options when defining the backing file for QEMU. This puts much lower requirement on available disk space. Since the virt-v2v behaviour for OVA input now depends on QEMU version

On 2009-05-15, at 07:26, David Greene wrote: > On Friday 15 May 2009 05:50, Jay Foad wrote: >> > >>> The one major thing to be aware of is that it isn't safe to use >>> &V[0] when V is an empty std::vector >> >> Oh dear. That's a bit of a flaw in the plan. I suppose the solution >> is to switch to SmallVector whenever this might be a