similar to: xm list vs. xl list: more differences?

Hi all, this is a non comprehensive list of missing features in libxenlight and\or xl: - xen_platform_pci flag support in VM config files; - relative paths support in VM config files; - hap support in VM config files; - -c option to xl create; - remus; - trigger command; - tmem-* commands; - sched-* commands; - usb-* commands; - scsi-* commands. In general if you execute "xm

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

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

Hmmm... It appears I never posted the corrected version of this patch so it never made it upstream. See: http://lists.xen.org/archives/html/xen-devel/2011-11/msg00587.html http://lists.xen.org/archives/html/xen-devel/2011-11/msg02145.html It would be good if this very minor fix was also applied to 4.2 (and, if possible, 4.1). Thanks, Dan =================== The program xen-tmem-list-parse

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

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

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi As we will use xl in xen 4.1. I had try use xl to do something. And I find some command is fails. For config file, when give "disk=" too args, it will show segment fault if we use xl create to start guest. Is there any change for xl''s config file? Following command can not work: xl migrate: when I use xl migrate domain localhost to do migrate, it shows error:

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

docs/man/xl.pod.1 | 6 +++++- tools/libxl/xl_cmdimpl.c | 39 ++++++++++++++++++++++++++++++++++++--- tools/libxl/xl_cmdtable.c | 3 ++- 3 files changed, 43 insertions(+), 5 deletions(-) xl: Introduce shutdown xm compatibility option -a to shutdown all domains Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it> diff -r 9dc729b75595 -r 67f9ef649937 docs/man/xl.pod.1 ---

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)

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

Hello everyone! With the completion of our first few release candidates for 4.2, it''s time to look forward and start planning for the 4.3 release. I''ve volunteered to step up and help coordinate the release for this cycle. The 4.2 release cycle this time has been nearly a year and a half. One of the problems with having such a long release is that people who get in features

Hi Stefano Here is some xl related bugs which opened for long time and I didn''t see anyone working on them. I retest them with latest xen upstream and all of them are still exist. 1. [XL]Fail to create multi-guests with NIC assigned http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761 xm don''t have the issue. 2. [XL]Guest network broken after do SAVE/RESTOR with xl

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, I''m currently switching from toolstacks from xm to xl. Because I have a rather complex network setup with my domUs, I use xen''s nat capabilities. But what works fine with xm behaves slightly strange in xl: I use something like the following to establish a domU interface within my vif part: ''type=vif, mac=00:16:3E:06:DA:B2, ip=192.168.2.1, vifname=fw11,

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

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> diff -r 3b409f65abae docs/man/xm.pod.1 --- a/docs/man/xm.pod.1 Thu Dec 01 17:26:48 2011 +0000 +++ b/docs/man/xm.pod.1 Thu Dec 01 18:01:35 2011 +0000 @@ -1,6 +1,6 @@ =head1 NAME -xm - Xen management user interface +xm - Obsolete xen management user interface =head1 SYNOPSIS @@ -8,10 +8,14 @@ B<xm> I<subcommand>

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1320922479 0 # Node ID bc79b560aafa1e4dc42af00e6a326dc651b5636a # Parent 460b507e15f864dd6712f5040e36538d6e076ae4 libxl: use named options for tsc_mode. It seems that this knob is expoerted from the hypervisor as a raw integer (no symbolic names) documented in xen/include/asm-x86. Propagating that all the way to the