similar to: No subject

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi, Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695,

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: wishlist [resending from another address since my ISP seems to be queueing emails for up to 25 hours and counting...] I did some experiments with the xen remus HA system. With overlord3:~$ debdiff xen_4.0.1-1.dsc xen_4.0.1-1lindi1.dsc diff -Nru xen-4.0.1/debian/rules.real xen-4.0.1/debian/rules.real --- xen-4.0.1/debian/rules.real 2010-08-02

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: wishlist I did some experiments with the xen remus HA system. With overlord3:~$ debdiff xen_4.0.1-1.dsc xen_4.0.1-1lindi1.dsc diff -Nru xen-4.0.1/debian/rules.real xen-4.0.1/debian/rules.real --- xen-4.0.1/debian/rules.real 2010-08-02 16:10:13.000000000 +0300 +++ xen-4.0.1/debian/rules.real 2011-01-05 00:32:41.000000000 +0200 @@ -159,6 +159,7 @@

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Please can you add python-xml as a dependancy for xen-utils-3.2-1 on lenny and above. Without python-xml a dependancy for "xm new" isn't satified. Thanks, Matthew Millar -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl isn't started by default. If blktapctrl isn't started then none of the tap: disks (eg tap:aio) work. This functionality has been removed in tools-misc-xend-startup.diff @@ -120,24 +86,14 @@ if not sys.argv[1:]: print 'usage: %s {start|stop|reload|restart}' % sys.argv[0] elif

Package: xen-utils-common Version: 3.4.2-3 Followup-For: Bug #571634 I can confirm that this bug not only exists in the current version but that it makes a DomU which forwards packets unusable. Other "simpler" DomUs which do not forward work perfectly. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (1000, 'stable'), (100, 'testing')

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Tags: patch Hi, There is a bug xen-3-3.2.1/tools/libfsimage/reiserfs/fsys_reiserfs.c, it is using "unsigned long" which is 64 bits on amd64 arch and 32 bits on i386 arch. This makes pygrub can't work on reiserfs on amd64 arch. You can easily reproduce it. A patch is included for fixing this problem. diff

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl doesn't start. This means that none of the tap: disks work (eg tap:aio). It produces this in the log BLKTAPCTRL[6569]: blktapctrl.c:788: blktapctrl: v1.0.0 BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (aio)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (sync)]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory XSA-57 version 3 libxl allows guest write access to sensitive console related xenstore keys UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= The libxenlight (libxl) toolstack library does not correctly set permissions on

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: important -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core) Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-amd64 depends on no

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Hi, I think would be good to have a note in manpage about this issue. Will save time to many people which will search about xmlproc in squeeze. --- xm.1.orig 2010-08-31 11:02:15.393343178 +0200 +++ xm.1 2010-08-31 11:05:25.978339569 +0200 @@ -466,7 +466,9 @@ .RE .IP "\fBnew\fR \fIconfigfile\fR [\fI\s-1OPTIONS\s0\fR]

Hi, When I tested the xm pause/unpause command, I found poor error messages. The following is the error messages. # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 492 1 r----- 394.6 vm1 1 512 1 r----- 3.0 # xm pause 0 Error: (22, ''Invalid argument'') # xm pause

Package: xen-utils-common Version: 4.1.2-1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines

Hi Konrad, Does this look at all familiar? There is some more info in the full bug log at http://bugs.debian.org/637234 . In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e

Package: xen-utils-common Version: 4.0.0-1 Severity: normal I am also struggling with this. I got farther by creating a .sxp file (xmexample.hvm.cfg is from /usr/share/doc/xen-utils-common/examples): # xm create -n -f xmexample.hvm.cfg | tail -n +2 > xmexample.hvm.sxp (why xm create -n mixes diagnostics with the output of -n on stdout, I do not know) and then specifying it on the command

Thanks for the reply. Sorry I didn't provide more details, but, yes, these are HVM domains. I use PV domains whenever possible, but in the case of Windows XP, that isn't possible, so I have to use HVM. I haven't tried suspending to OCFS2 with a PV domain, but I may give that a shot. Still, I think it's strange that it works perfectly fine to my ext3 and reiser filesystems, but

Package: xen-utils-common Version: 4.0.0-1 Severity: important The xm utility requires python-xml but the package does not depend on it. # xm new --help_vars Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>

Hi, all, When working on adding PM support to xen, we realized that some enhancements are required to suspend/resume domU. Following is some background and thoughts, and welcome on comments. :-) Currently we use a simple approach (pause/unpause) for domU when ready to pull whole platform into a power save state, saying a S3. Because pause/unpause is out of domU''s knowledge, domU

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1~rc3-1 Severity: normal Hi, I upgrade one server from lenny to squeeze, to start testing xen-hypervisor-3.4 and xen-hypervisor-4.0, but it seems to don't work. The error : xm create -c /etc/xen/slhoka.cfg Using config file "/etc/xen/slhoka.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. The error