similar to: bug report of xm list and xm vcpu-list

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()

These xm info, top, dmesg and log requre no parameter. But log''s error message differs from other 3 command''s error messages, when parameter is given. # xm log 1 Error: ''xm log'' requires 0 argument. log Print the xend log Other 3 commands ignore parameter. I think it might be better symmetricalize. Signed-off-by: Yoshinori

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=249 Attempting to save an active guest domain fails, with ''Invalid state record -- pfn count out of range: 268435456'' error. Changeset: 6997 Machine: IBM HS20 Blade, x86_64 (EMT64), SLES 9 SP2 distro. [root@bl2-10 ~]# xm list Name Id Mem(MB) CPU VCPU(s) State Time(s) Domain-0 0 245 0

Hello list, I want to virtualize my physical CentOS 4.5 yet. Therefor I download the CentOS 4.5 iso. After mounting the iso on my notebook and make the mounted iso available via nfs I start on my CentOS 5 xen machine following command: virt-install -n myServer --ram=512 -f /virt/myServer.disk -s 150 --nographics -p --location=nfs:nbk:/media/centos This works for CentOS 5 DomUs but CentOS 4.5

I''ve compiled xen-3.0.2-2 from sources. I''ve went to the end without errors. The ./install.sh script have been created the /etc/grub.conf file as it : # initrd /boot/initrd-version.img #boot=/dev/hdc default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.15-1.2054_FC5) root (hd0,0) kernel

I''m using RHEL 5. One of the virtual machines I have running is a WinXP install. I start this up after I login to X. If I log out of X, the virtual WinXP is still running (that''s fine with me). However when I log back into X and start the Virtual Machine Manager, I am unable to open the machine. It normally says "Virtual Machine Console is unavailable." There does

Package: xen-utils-common Version: 4.1.0~rc6-1 Severity: important Currently xend fails to create a fully virtualized vm because it has a different path hardcoded to it. Unable to complete install: 'POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: device model '/usr/lib64/xen/bin/qemu-dm' not found")' The correct path to use

Hi there I get the following error message when i try to "xm create <domid>" Error: Error creating domain: (22, ''Invalid argument'') I have included everything i can think of Thanks The DomU config is kernel = "/boot/vmlinuz-2.6.12-xenU" ramdisk = "/boot/initrd-2.6.12.6-xenU.img" memory = 128 name = "xen01" nics=1 disk = [

To make Btrfs code more robust, several return value checks where memory allocation can fail are introduced. I use BUG_ON where I don''t know how to handle the error properly, which increases the number of using the notorious BUG_ON, though. Signed-off-by: Yoshinori Sano <yoshinori.sano@gmail.com> --- fs/btrfs/compression.c | 6 ++++++ fs/btrfs/extent-tree.c | 2 ++

To make Btrfs code more robust, several return value checks where memory allocation can fail are introduced. I use BUG_ON where I don''t know how to handle the error properly, which increases the number of using the notorious BUG_ON, though. Signed-off-by: Yoshinori Sano <yoshinori.sano@gmail.com> --- fs/btrfs/compression.c | 6 ++++++ fs/btrfs/extent-tree.c | 4 ++++

Hi,    I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version and .... virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4

This patch fixes error(help) messages in main.py and shutdown.py. 1.change the maximun number of argument for xm_reboot 2.unify error message for xm_shutdown Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r 1e1107e3d894 tools/python/xen/xm/main.py --- a/tools/python/xen/xm/main.py Wed Jan 11 19:14:27 2006 +++

Just wondering if this is a known bug? Trying to migrate the VM off to a diff dom0 results in the below error. Other VMs migrated off fine (started at around the same time as this vm) and I''ve tried a few different target servers, all resulting in the same thing. [2011-09-13 13:48:24 3996] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 29 77 0 0 1 [2011-09-13

I''m having issues with HVM live migration and every xen version I''ve tried - 3.0.1, 3.1.x, 3.3.0 and 3.3.1. Migrations will fail intermittently with messages like this on the receiving hypervisor: [2009-02-02 11:35:19 12629] DEBUG (XendCheckpoint:264) [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 4 2 3 1 1 1 [2009-02-02 11:35:19 12629] INFO (XendCheckpoint:403)

Hello everyone, for research purposes I''m working on Xen 3.0.3 and trying to make some modifications to Xen migration. By looking at the documentation, I''ve learned that the part I''m interesting in are handled by two binaries (xc_save and xc_restore), so I thought about modifying just this two binaries instead of recompiling the whole Xen everytime, so what I do is just

I got latest (13601) yesterday evening. This doesn''t seem to work to do Restore (at least of the Windows test-image that I''ve been using for testing previously). The VM restores reasonably OK, but it jumps to an invalid address shortly after restoring, giving a D1 blue-screen error (DRIVER_IRQL_LESS_OR_EQUAL), which turns out to be "page-fault in driver" after I

Hello, Recently I ran yum update on a RHEL5 x86_64 machine and as part of the update, the following packages were installed: Updated: xen-libs-3.0.3-41.el5.x86_64 Updated: xen-libs-3.0.3-41.el5.i386 Installed: kernel-xen-2.6.18-53.1.14.el5.x86_64 Updated: xen-3.0.3-41.el5.x86_64 After the update, I rebooted the machine. Now, I cannot get xend to start:

Resent of mail sent on 28.04. xend: fix bug in option parsing If you enable legacy tcp xmlrpc in xend''s config but omit to enable ssl the following backtrace is generated when starting xend: [2010-04-28 16:09:04 15754] ERROR (SrvDaemon:349) Exception starting xend (''NoneType'' object has no attribute ''rfind'') Traceback (most recent call last): File

Starting about 2 weeks ago Xend has started to fall over a lot doing what should be normal actions, so much so that our xm-test suite more or less fails all the tests as it keeps apparently knocking over xend on relatively simple operations like create, and list. What is most bizarre now is this "no such process" error generated by Xend. Here is a segment of our xm-test results that

What are methods to debug domU when it hangs? Using xen 3.1 compiled from sources I could not manage to launch no domU. Fot instance, I run something like this: =====8<===================== disk = [ ''file:/oradata-act/sles.disk,hda1,w'', '',hdc:cdrom,r'' ] kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen" cpus =