similar to: Bug#770456: Please start a qemu process in domain 0.

On 27.11.2014 12:18, Ian Campbell wrote: > On Thu, 2014-11-27 at 11:02 +0100, Stefan Bader wrote: >> On 21.11.2014 13:50, Ian Campbell wrote: >>> Package: xen-utils-common >>> Version: 4.4.0-1 >>> Severity: important >>> Tags: patch >>> >>> Under some circumstances the xl toolstack needs to create a loopback >>> mount of a

On Thu, 2014-11-27 at 11:02 +0100, Stefan Bader wrote: > On 21.11.2014 13:50, Ian Campbell wrote: > > Package: xen-utils-common > > Version: 4.4.0-1 > > Severity: important > > Tags: patch > > > > Under some circumstances the xl toolstack needs to create a loopback > > mount of a guest disk in dom0 (e.g. in order to run pygrub). Depending > > on

Hi, I just finished preparing the Xen-4.5 merge from experimental into our next release (Vivid/15.04). And something I actually should have done since the 4.4 times is to report back the delta I have in case there are things Debian might want to pick up as well. So below is the commented debdiff between the 4.5.0-1 in experimental and the Ubuntu version I prepared so far (only compile tested on

On 21.11.2014 13:50, Ian Campbell wrote: > Package: xen-utils-common > Version: 4.4.0-1 > Severity: important > Tags: patch > > Under some circumstances the xl toolstack needs to create a loopback > mount of a guest disk in dom0 (e.g. in order to run pygrub). Depending > on the nature of the guest disk (e.g. qcow2 or raw file image based) > this can require a qemu

On Thu, 2014-11-27 at 17:41 +0100, Stefan Bader wrote: > On 27.11.2014 12:18, Ian Campbell wrote: > > On Thu, 2014-11-27 at 11:02 +0100, Stefan Bader wrote: > >> On 21.11.2014 13:50, Ian Campbell wrote: > >>> Package: xen-utils-common > >>> Version: 4.4.0-1 > >>> Severity: important > >>> Tags: patch > >>> >

On Thu, 2015-01-22 at 13:02 +0100, Stefan Bader wrote: > That one modifies xen-init-list to look at domains managed by the xl namespace. > This additionally works around a bug in xl which will report a syntax error when > "xl list -l" is called while domains in a different namespace exist. Which is > the case when libvirt is used to start them. FWIW in 4.5 xl is supposed to

Package: xen-utils-common Version: 4.4.1-2 Severity: normal For correct operation under SE Linux the start script needs to assign correct security labels to firectories it creates. Note that restorcon doesn't cause any problems if run twice. If it's executable then you can safely run it. Below is a patch that demonstrates how to solve this problem. --- xen.old 2014-10-12

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my server from squeeze to wheezy and then to jessie. Server is Intel S3200SHV m/b with Intel(R) Core(TM)2 Quad CPU. I'm pretty sure that before that it was running whatever came before squeeze, I forget the name. I was trying to get xen_pciback to work, so I

Package: xen-utils-common Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Severity: important Please modify the init scripts in a manner similar to the following to give the correct SE Linux labels. Failing to correctly label them may result in Xen not working correctly when SE Linux is enabled. --- /etc/init.d/xen.orig 2012-06-24 10:29:04.000000000 +1000 +++ /etc/init.d/xen 2012-06-24

Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access

On Mon, 2014-12-01 at 13:47 +0100, Stefan Bader wrote: > > Anyway, your diff seems to only add some code to xenstored_start, I was > > expecting a change to qemu_start -- did you find that code was OK in the > > end? Or did you end up switching to --exec? > > Errm, that part was the addition I inlined. The updated change was the full diff > between current init script

/usr/lib/xen/bin/qemu-system-i386 doesn''t exist on ARM. We need to check if the file exists/is executable and starts it. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/hotplug/Linux/init.d/xencommons | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tools/hotplug/Linux/init.d/xencommons b/tools/hotplug/Linux/init.d/xencommons index

Hi, I have a CyberPower UPS connected to a Ubuntu karmic machine. All functions are working well. I can use upsc to see all the UPS parameters, power loss and battery low events are correctly detected, and shutdown is correctly initiated. If I run upsdrvctl shutdown, the UPS cuts power immediately. However, if I simulate a shutdown with upsmon -c fsd, the UPS fails to cut power. The

Ubuntu 14.04. 2 node ctdb in an 4.1.11 AD domain with 4.1.11 member servers on each node. winbindd is present but nss and pam are controlled by sssd. All OK, except that the event script which starts samba is not working. smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER clustering = Yes ctdbd socket =

Hello together, > * Report your success/failure! > * Samba4 as a replicating domain controller is still developing rapidly, and we > like to hear from users about their successes and failures. While Samba4 is > still in rc state we would encourage you to report both your successes and > failures to the samba-technical mailing list on

On 22.01.2015 17:02, Ian Campbell wrote: > On Thu, 2015-01-22 at 13:02 +0100, Stefan Bader wrote: >> That one modifies xen-init-list to look at domains managed by the xl namespace. >> This additionally works around a bug in xl which will report a syntax error when >> "xl list -l" is called while domains in a different namespace exist. Which is >> the case when

26470:acaf29203cf9 "tools+stubdom: install under /usr/local by default" moved more stuff under /usr/local than was desirable. In particular SYSCONFIG_DIR (configuration for initscripts) moved to /usr/local/etc/{sysconfig,defaults} while the initscripts themselves (correctly) remained in /etc/init.d. Moving /etc/xen/scripts breaks the udev bakcned rules file. Lastly stuff under /var was

On Thu, Mar 26, 2015 at 9:16 AM, Emilien Kia <kiae.dev at gmail.com> wrote: > > > After looking a bit deeply, we have another little problem. When we intend > to start upsd with the init script (at least under debian-based distrib - > tested on Linux Mint 17.1) when we have the NSS problem, the init script > exit with the "[OK]" state even if the "real"

When installing xen-utils-V in a driver domain domU, it drags in xen-utils-common, which also contains the init script for xenstored and xenconsoled. Installing the package will fail right away, because it exits non-zero after checking whether it's running in a xen dom0 or not: systemd[1]: Starting LSB: Xen daemons... xen[7215]: Starting Xen daemons: (warning). systemd[1]: xen.service:

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are