similar to: xm / xl rename bug?

On a fresh reboot free: total used free shared buffers cached Mem: 3371340 448156 2923184 0 5328 77840 ---------- top: Mem: 3371340k total, 449044k used, 2922296k free, 5344k buffers ---------- xentop - 01:44:00 Xen 3.4.3-rc4-pre 1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 4160828k total, 4022996k used, 137832k free CPUs: 4

Hi, One of the I noticed during migration from XM toolchain to XL in PCI Pass-through was that we used to specify target bdf in HVM guest as pci = [ ''0000:07:11.6=0@1a'' ] However with XL, it now seems like this is the correct syntax: pci = [ ''0000:07:11.6@1a'' ] Is that correct? I''ve verified that it works but what about zero in

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

i am trying to add auto migration feature in XEN. so is anyone has worked related to migration part. i need help regarding files related to migration. -- Regards Gautam _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''ve attached the preliminary patch to add vncviewer options to the ''xl create''. It applies cleanly against c/s 4e1d091d10d8. All feedback is welcome. Goncalo # HG changeset patch # User Goncalo Gomes <goncalo.gomes@eu.citrix.com> # Date 1332257809 0 # Node ID 46f8afe643dee8de2c592c65204567fbad657616 # Parent 4e1d091d10d83130842170cd61f1194e5459f2aa Add

I see that "xl list" shows a domain waiting idly for console input as "r", whereas "xm list" shows the same domain as "b". I also see that the State field for "xl list" contains only three characters (e.g. "r--"), whereas "xm list" shows six (e.g. "-b----"). Is this expected/intended (e.g. "r" in xm list

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

In XM toolchain, we use to put pci = [ ''0000:07:11.6=0@1a'' ] but looks like in XL toolchain there is no way to specify function in the guest. Kindly let me know. XM - pci = [ ''0000:07:11.6=0@1a'' ] XL - pci = [ ''0000:07:11.6@1a'' ] In the guest VM we see that PCI device is getting 0 function in both the cases however, it may not work the

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Using the xl toolstack there's no information about the networks of the domUs in xentop. I have a PV and a HVM domU and both are shown as having 0 network interfaces, while in fact they have functioning interfaces. Here's one of the interfaces that should be shown, from xenstore: 29 = "" 0 = "" frontend =

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

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

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 inakoshi.hiroya@jp.fujitsu.com # Date 1191287395 -28800 # Node ID 5543e74774a826b1781893982ed5052312b820fc # Parent 83239b2890723e0c06bad507bb273a970784b18e Flush stdout when xentop -b gets SIGINT and SIGTERM. It is useful when you stop xentop -b by keyboard interrupt or by other programs such as killall from a batch script. You would have missed the bottom part of

Package: xen-utils-4.4 Version: 4.4.1-9 Severity: normal # /usr/lib/xen-4.4/bin/xl create -c /etc/xen/katana Parsing config from /etc/xen/katana libxl: error: libxl_utils.c:217:logrename: failed to rotate logfile - could not rename /var/log/xen/qemu-dm-katana.log.6 to /var/log/xen/qemu-dm-katana.log.7: Permission denied Segmentation fault The above happens repeatably when I run xl on a system

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

# 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, I noticed that the CPU% reported by xentop appears to be too high. With dom0 idle xentop is reporting between 14-17% CPU utilization while at the same time top in dom0 is reporting 1-4% CPU utilization. I see that the TODO for xentop includes a task to make CPU% more accurate but looking at the code for xentop and libxenstat I''m not sure how to go about this. Assuming the CPU

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

Hi, I am in the process of upgrading some xen installations from 3.x to 4.1.1 and got into this: box# xl create vm1.cfg warning: Config file looks like it contains Python code. warning: Arbitrary Python is no longer supported. warning: See http://wiki.xen.org/xenwiki/PythonInXlConfig Failed to parse config file: Invalid argument I''m using python stuff to define vifs and disks