similar to: Bug#772809: Update debian xendomains init and default to latest xen upstream

Il 10/12/2014 12:56, Ian Campbell ha scritto: > On Wed, 2014-12-10 at 12:47 +0100, Fabio Fantoni wrote: >> Thanks for your work on xen packages, I have some question about 4.5 >> packages: >> I saw a debian/rules that disable blktap2 but >> debian/patches/tools-blktap2-prefix.diff is still present and used in >> series, if blktap2 is now disable I think is nomore

Il 10/12/2014 14:59, Ian Campbell ha scritto: > On Wed, 2014-12-10 at 14:45 +0100, Fabio Fantoni wrote: >> If I remember good there isn't particular bugs caused by the xendomains >> missed things. >> The more useful parameters when mainly windows domUs are used is >> XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems >> to decrease the

On Wed, 2014-12-10 at 14:45 +0100, Fabio Fantoni wrote: > If I remember good there isn't particular bugs caused by the xendomains > missed things. > The more useful parameters when mainly windows domUs are used is > XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems > to decrease the "overload" caused by windows startup (even if pv drivers >

Source: xen Version: 4.4.0-4 Severity: normal Xendomains init and default files are taken from debian folder instead source and are not updated for some years. Please update them from upstream source. I did a fast update and test of them available here: https://github.com/Fantu/pkg-xen/commit/4d1914776256d209665d490182cf662f70cda619 -- System Information: Debian Release: jessie/sid APT prefers

Thanks for your work on xen packages, I have some question about 4.5 packages: I saw a debian/rules that disable blktap2 but debian/patches/tools-blktap2-prefix.diff is still present and used in series, if blktap2 is now disable I think is nomore needed. I saw also many other patches about prefix still present but for xen 4.5 time ago I saw a big series of patches about honor tools prefix,

Package: xen-utils-common Version: 4.4.1-5 Severity: important Dear Maintainer, I tried to upgrade xen-utils-4.4 depending on xen-utils-common. Here is aptitude answer: ... Param?trage de xen-utils-common (4.4.1-5) ... insserv: Service xenstored has to be enabled to start service xendomains insserv: Service xenconsoled has to be enabled to start service xendomains insserv: exiting now!

On Wed, 2014-12-10 at 12:47 +0100, Fabio Fantoni wrote: > Thanks for your work on xen packages, I have some question about 4.5 > packages: > I saw a debian/rules that disable blktap2 but > debian/patches/tools-blktap2-prefix.diff is still present and used in > series, if blktap2 is now disable I think is nomore needed. Yes, this can probably go. > I saw also many other patches

Hi, Ever since xl become the preferred toolstack, I have had problems using the xendomains startup/shutdown script. Having retested today, it seems that the issues are now reduced down to xendomains being unable to restart previously saved domains. Here is a typical session using xl running Xen 4.2.2 on Ubuntu 64 12.04 bit server, using stock Dom0 kernel (3.2.0-43-generic)

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

Hello Everyone! Been looking around the internet but have not found a solution for my problem yet, all i found was a report on opensuse forums with no replays. I have a Xen dom0 running on OpenSuse 11.4 x86_64, on this I’ve created 3 PV instances all running OpenSuse 11.4 x86_64 as well. All 3 PVs were installed the same way with the same package selection and only ONE of this 3 PVs hangs at

Hello all I''ve just installed xen 4.1.1 on my server and was tryoing to tweak xendomains script to work with new xl schema but I can´t get it to save domains. It does start them with some changes I made to it but when I issue service xendomains stop I just get [ OK ] but domains stay running. Has xendomains script been ported to work with 4.1.1 or is there another alternative to it.

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a

Hello, for everybody who develops or uses the script /etc/init.d/xendomains, there is a serious error in this script. If the given variable XEN_DOMAINS_AUTO_ONLY is set to true in /etc/sysconfig/xendomains, then the saving of the domains always fails - the domains are shut down instead of the saving. This is very bad especially for some HVM domains which MUST be saved instead of shut

Hello, for everybody who develops or uses the script /etc/init.d/xendomains, there is a serious error in this script. If the given variable XEN_DOMAINS_AUTO_ONLY is set to true in /etc/sysconfig/xendomains, then the saving of the domains always fails - the domains are shut down instead of the saving. This is very bad especially for some HVM domains which MUST be saved instead of shut

Usage: vga="qxl" Reposted for xen 4.4, require SSE support on hvm domU otherwise it works only as a standard vga. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> Signed-off-by: Zhou Peng <zpengxen@gmail.com> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> --- docs/man/xl.cfg.pod.5 |

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer, After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto fails with errors like this Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

Package: xen-utils-common Version: 4.4.1-9+deb8u4 Severity: normal Dear Maintainer, I have a server with a large number of domUs set to auto-start. For the first time I have booted it with all of them needing to start from cold, but the xendomains service only got part way through. syslog showed nothing notable about the domains starting? Apr 16 14:57:45 snaps xendomains[4631]: Starting

So, let's get started! One of the first changes we might want to do is move away /etc/sysconfig/xendomains... We should put it either in /etc/default/xendomains (since it's an init script configuration) or /etc/xen/xendomains (since it's xen related)... Which one do you prefer? As for the way to do it I propose a dpatch file that changes the two files in the upstream tarball that

There is some ugliness in the current version (4.4.1-2) although it doesn't seem to actually break anything in my case. From /var/log/boot: /etc/init.d/xendomains: line 128: domains: bad array subscript Starting Xen domain (from /etc/xen/auto/dnsmaster.cfg).../etc/init.d/xendomains: line 135: domains: bad array subscript

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines