similar to: Bug#727100: domain doesn't reboot with xl toolstack

On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > When you use xl toolstack, you can't reboot domUs. > When you switch back to xm toolstack, than reboot works again. > I think the problem with the debian packaged version is the same as in > this thread: > http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html > I also think it's a security issue,

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Switching to the xl toolstack I expected my configuration to work unmodified, but it doesn't, and I couldn't find any documentation regarding this, since xl.cfg(5) is missing. Original version, used with xm: vfb = ['type=vnc,vnclisten=0.0.0.0:6369,vncdisplay=6369,vncpasswd=x'] Working xl version: vnclisten="0.0.0.0:6369"

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: minor In the file /etc/xen/xl.conf there's a suggestion that vif scripts should be named relative to the /etc/xen/scripts directory, which is not the case, since absolute paths have to be used. The manual page xl.conf(5) is also missing. Relevant snippet: # default vif script #vifscript="vif-bridge"

I get “Unable to connect to libvirt” when using virt-manager in combination with the XL toolstack and Xen 4.2.1. (No problems when using virt-manager in combination with the XM toolstack.) More details of the situation can be found in a bug-report that I filed on launchpad. Please see: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281 Judging from the information that I provided

Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and

Hej folks, I''m messing around with DRBD once again but with a new Xen 4.1.2 installation using the XL toolstack instead of the xend daemon. However, after getting my DRBD installed and a device operational, trying to create a domU using the drbd block device doesn''t want to work: xl create -c test.cfg Parsing config file test.cfg Unknown disk type: drbd My config has: disk

Hello, everybody! Does anyone have experience of running win7/winxp with xl? As for me, I got HAL_INITIALIZATION_FAILED BSOD on win7 booting and guest hanging in case of winxp. When i run these guests (with the same configs) with xm, everything is ok. The guests boot perfectly. Did anyone run into it too? I use the lattest xen-unstable, but i saw the problem several months ago too. My

I have an issue on Xen 4.2+ (now on yesterday''s tip) where when I try to use an iso image as cdrom for a pv domU, it appears that the devices is an unusable state on the domU side. DomU kernel output: http://bpaste.net/show/63482/ xen logs: http://bpaste.net/show/63490/ udevadm monitor output: http://bpaste.net/show/63481/ I can work around this issue easily by creating a loop back

Hello, After creating and destroying a number of domUs, I noticed that /local/domain/0/backend starts to get cluttered when using XL. The vif, vfb, vkbd, and vbd sections look like this: 270 = "" 271 = "" 272 = "" 273 = "" 274 = "" 275 = "" Where the dom ID is set to an empty value, however the console

Hello, Hope you can help. A while ago users noted performance degradation or dom0 stability issues when shuting down a HVM guest that uses VGA passthrough (e.g. Windows 7), and booting up the guest again. A workaround was to eject the graphics card within Windows, before shutting down the guest. This process is described here: http://blog.ktz.me/?p=219. I tried to follow those instructions, but

Hello, Currently it seems that the drbd disk type with Xen''s XL toolstack (vs XM) to get the automatic promotion/demotion behavior of drbd devices is not supported. Is there something I can tweak with the block-drbd script to get this to work? Thanks, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello, Currently it seems that the drbd disk type with Xen''s XL toolstack (vs XM) to get the automatic promotion/demotion behavior of drbd devices is not supported. Is there something I can tweak with the block-drbd script to get this to work? Thanks, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

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''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: normal It seems to be impossible to save or migrate HVM guest using the xl toolstack. Trying to do so hangs the process initiating the action, and the domU can't be shut down with the 'xl shutdown' command after this. 'xl destroy' works. The domain keeps running during the save operation, doesn't get paused for any

I?m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none".

After a few days, one of my DomU becomes unresponsive. Here''s the output of my DomU''s. root@xenII:/var/log/xen# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 7126 2 r----- 723932.0 redhat-sdsweb 11 4091 2 -b---- 92633.1 w2k8-AD