similar to: Dom0 configuration w/ xl

Hello, Fedora 19 running Xen 4.2.3 rpms, "xl list" after dom0 reboot: [root@localhost ~]# xl list Name ID Mem VCPUs State Time(s) (null) 0 1024 8 r----- 16.3 Why is dom0''s name "(null)" ? It seems also xenstore is quite empty: [root@localhost ~]# xenstore-ls tool =

Hi folks The current package in unstable is able to use xl. It is still a bit edgy but seems to work. Because the old xm with xend and xl clashs and one should only use one, this needs some more setup to provide a proper upgrade path. I propose the following: - Add a script "xen" that wraps xl and xm depending on the config for use by all the scripts. Most parts are command line

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as

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

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

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1338572607 -7200 # Node ID 3da83ff08d6b6431c104a431d6617ccb5977643b # Parent fde8ad0252ee6ddb8d71dda869db3b20b3d9ca62 xl.cfg: document the cpuid= option Signed-off-by: Olaf Hering <olaf@aepfle.de> diff -r fde8ad0252ee -r 3da83ff08d6b docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -969,9

Hello, As discussed on the last Virt SIG meeting I promised to do some libvirt + libxl testing using the latest Xen 4.4 rpms. Versions used: xen-libs-4.4.1-5.el6.x86_64 xen-licenses-4.4.1-5.el6.x86_64 xen-hypervisor-4.4.1-5.el6.x86_64 xen-4.4.1-5.el6.x86_64 xen-runtime-4.4.1-5.el6.x86_64 kernel-3.10.63-11.el6.centos.alt.x86_64 libvirt-daemon-driver-nwfilter-1.2.10-3.el6.x86_64

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

Prevent xl from doing any operation if xend daemon is running. That prevents bugs that happened when xl and xend raced to close a domain. Changes since v1: * Add documentation to xl man page. * Permit the execution of commands that don''t modify anything. * Indent error message. Cc: george.dunlap@eu.citrix.com Cc: ian.jackson@eu.citrix.com Signed-off-by: Roger Pau Monne

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

According to the xen 4.1 release notes linked from here: http://xen.org/products/xen_source.html Some features are missing from xen 4.1. i.e. *List of missing features from xl/libxl in Xen 4.1:* ** - *PVUSB (for more info see PVUSB sections of: XenUSBPassthrough<http://wiki.xen.org/xenwiki/XenUSBPassthrough.html> )* - *PVSCSI (for more info see:

I just downloaded Xen-4.1.1 from xen.org, compiled it, and installed it. I then compiled kernel 3.0.0 and added the hypervisor and dom0 kernel in a grub 2 entry. After booting, I executed "xl list," to confirm the hypervisor was running. I was greeted with this message: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such

Hello, I am tryiong to set up a Dom0, right now my problem is creating the first guest. This is xen unstable tip ubuntu running jeremy kernel I have this: daniel@dani-ubuntu-xen:/usr/sbin$ sudo xm info [sudo] password for daniel: Error: Unable to connect to xend: No such file or directory. Is xend running? daniel@dani-ubuntu-xen:/usr/sbin$ Yet, xl reports this: daniel@dani-ubuntu-xen:/usr/sbin$

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

Hello, I''m using Gentoo Linux amd64 with the 2.6.34-xen-r4 kernel from portage. I''ve been successfully using Xen 4.0 for almost a year, but now it seems that with the dawn of Xen 4.1, the package maintainers have forces unstable users to upgrade from 4.0 to 4.1 Looking forward to try the new xl interface, I installed it, but there seem to be a few problems with xen-4.1 First

Hello, I''m using Gentoo Linux amd64 with the 2.6.34-xen-r4 kernel from portage. I''ve been successfully using Xen 4.0 for almost a year, but now it seems that with the dawn of Xen 4.1, the package maintainers have forces unstable users to upgrade from 4.0 to 4.1 Looking forward to try the new xl interface, I installed it, but there seem to be a few problems with xen-4.1 First

I want to get couple of DomUs running with Xen. I installed Xen 4.1.5 from source on a Fedora 17 Dom0. I did some reading on configuring DomUs using xl/xm and cfg files. http://www.fclose.com/b/linux/2544/setting-up-lvm-backed-xen-domu/ http://www.fclose.com/w/Setting_Up_Xen_DomU_on_Fedora:_Unmodified_Fedora_on_Top_of_Xenified_Fedora_Xen_Dom0%23Install_Fedora_12_Linux_via_Internet So basically I

Hi, When I rename a domain with xl, the new name shows in xl list but not in xm list, and the other way around. xentop and xl top use the names visible in xm list. -- Hans xen 4.1.1 / 3.0.0-rc7 non hvm _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Hi, during some experiments with many guests I get crashing Dom0s because of too less memory. Actually the OOM killer goes ''round and kills random things, preferably qemu-dm''s ;-) The box in question has 128GB of memory, I start with dom0_mem=8192M (or 16384M, doesn''t matter). I also used "dom0_mem=8192M,min:1536M", but that didn''t make any