similar to: equivalent xe subcommands to ''xm sysrq'' and ''xm dump-core''

Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as

Hi, I tried to test a wrong operation on purpose again. When I tried xm sysrq command to a inactive managed domain, I saw the following error message. The error message did not have a message text behind "Error:". And I found an AssertionError message in xend.log. # xm list PVdomain.1 Name ID Mem VCPUs State Time(s) PVdomain.1

Hello, Without using XM, is it safe to write the letter corresponding to the desired sysrq to xenstore in /local/domain/domid/control/sysrq ? Does anything else have to happen? I am working on some backup utilities that utilize the lvm2 library (liblvm2cmd) , libxenctrl and libxenstore. The program will issue a sysrq S to a guest, pause it, take a snapshot then unpause it (all very quickly). An

Xen Community, I have a team of people frantically creating manpages for the xe command and all of it''s 361 subcommands. The initial source documentation is in asciidoc but also saved as Docbook. From docbook we transform to epub, html, manpage and pdf. This is currently being hosted in a subversion server at a Seattle area college and we''d like to move it to the xen-org

> Hi, Simon > > >Two things: > > > >1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this > >(and if you want > > a dump, do ''xm dump'' followed by ''xm destroy'') > > > What do you mean? > I think we cannot dump with "xm destroy" now. >

''xl mem-set'' should update memory info in xenstore''s vm info. Signed-off-by: Yu Zhiguo <yuzg@cn.fujitsu.com> diff -r ccae861f52f7 -r 5847ce53f5dc tools/libxl/libxl.c --- a/tools/libxl/libxl.c Thu May 06 11:59:55 2010 +0100 +++ b/tools/libxl/libxl.c Sat May 08 01:38:51 2010 +0800 @@ -2290,11 +2290,22 @@ uint32_t videoram; char *videoram_s = NULL;

I submitted this yesterday in r274171. I think this allows for a more intuitive way to structure the options of command line tools. It's optional and if you do nothing llvm::cl will work as it always has for you. Probably self explanatory, but here's some output of --help from llvm-pdbdump, which was updated to use subcommands in r274247, in case anyone wants to see what this looks

Package: xcp-xe Version: 1.3.2-11 Severity: minor xe did not prove help in autocomplete for xe console command. Steps to reproduce: xe console[tab] Output (help) does not contains xe console command. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)

Package: xcp-xe Version: 1.3.2-8 Severity: minor When autocomplete for bash is activated following misbehavior happens: xe pif-list params=device,m[Tab] expected behavior: autocomplete to xe pif-list params=device,management actual behavior: xe pif-list params=management ('device' removed) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500,

This patch unifys error messag of migrate and sysrq. Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r bfcdf4099d23 tools/python/xen/xm/migrate.py --- a/tools/python/xen/xm/migrate.py Thu Jan 12 13:27:55 2006 +++ b/tools/python/xen/xm/migrate.py Fri Jan 13 15:26:14 2006 @@ -56,8 +56,8 @@ if opts.vals.help: opts.usage()

I am having trouble sending sysrq commands over USB serial, and I'm not sure what else to check. I have two identical machines, each with usb-to-serial adapters, joined by a null modem adapter. One runs an agetty, the other minicom. I can log in over the agetty as a user and it works as expected, until I try to send a sysrq. To send a break in minicom, I type [Ctrl]+[a] then [f]. Then I

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE="/usr/lib/xcp/bin/xe" MUST BE: XE="/usr/bin/xe" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux

Package: xcp-xapi Version: 1.3-16 Severity: normal Tags: patch Dear Maintainer, Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be: XE="/usr/bin/xe" HTH, David -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)

Hi, is there some way to trigger sysrq from the serial console in xenlinux? With native linux it works by sending a break + sysrq letter, in xenlinux it doesn''t work that way though ... cheers, Gerd -- panic("it works"); /* avoid being flooded with debug messages */ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Package: xcp-xe Version: 1.3.2-8 Severity: minor XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not. Difference: XCP 1.1 behavior: xe sr-probe type=nfs device-config:[Tab] device-config: device-config:serverpath= device-config:server= xcp-xe behavior: xe sr-probe type=nfs device-config:[Tab] (nothing) Other arguments

guestfish returns 0 if the commands completed without error, or 1 if there was an error. But the rule break when we use '-' prefix subcommands: ------------------------------------ $ guestfish <<\EOF > blabla > EOF blabla: unknown command $ echo $? 1 $ guestfish <<\EOF -blabla EOF blabla: unknown command $ echo $? 0 ------------------------------------ I think it should

Well, that was a lot of alphabet soup acronyms :). I''ve just been thinking about the claim in a prior post that using the xe cli with XCP abnormally increases the XCP server load. The only way I could see this happening is to be running xe from the servers command line. I use xe extensively to do the grunt work of XCCS (Xen Cloud Control System). I don''t see the loading

Package: xcp-xe Version: 1.3.2-14 Severity: normal I created an LV manually and ran the command: xe sr-create type=ext name-label=myHostSr0 \ device-config:device=/dev/mapper/vg00-sr0 The SR was created, however, I found that it was created as a nested LV, in other words, it appears xe did something like this: pvcreate /dev/mapper/vg00-sr0 vgcreate sr_vg lvcreate sr_vg sr0

Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) :

Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)