similar to: Bug#435406: xen-utils-common: xm save does not use compression

Displaying 20 results from an estimated 10000 matches similar to: "Bug#435406: xen-utils-common: xm save does not use compression"

2007 Apr 08
1
Bug#418245: xen-utils-common: race condition in "xm list" when destroying domains.
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal After running "halt" in a couple of domains I ran "xm list" repeatedly to see when the halt command was complete. Below is some of the output. The "Device 0 not connected" should not occur. yoyoxen:~# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0
2007 Jul 19
1
Bug#433780: xen-utils-common: /etc/init.d/xend restart should restart xenstored and xenconsole
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal There should be a clean and clearly defined way to restart all the Xen daemons in the case of error. If the file /var/lib/xenstored/tdb is corrupt then you must stop xenstored, rm the file, and then restart it. Currently there is no defined way of doing this so the solution is to kill -9 the process, rm the file, and then reboot. --
2007 Apr 01
1
Bug#417243: xen-utils-common: Should display a usable error message when there is a config file error
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal When a block device name is wrong (the device does not exist) it should say "block device /dev/foo/bar does not exist" instead of waiting for ages and giving the following error: Using config file "/etc/xen/ha2". Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. Also the following parsing
2007 Jul 10
1
Bug#432583: xen-utils-common: "xendomains stop" won't save domains which name starts with "Name"
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal xendomains saves the active domains when shutting down. it get the list of active domains from the following command[1]: xm list | grep -v '^Name' the output of "xm list" is like: lichen:~# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0
2010 Sep 19
3
Bug#597403: xen-utils-common: need to run restorecon in /etc/init.d/xend on SE Linux systems
Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access
2007 Mar 10
0
Bug#414294: xen-utils-common: /etc/init.d/xendomains fail to save domains with "long" names
Package: xen-utils-common Version: 3.0.3-0-2 Severity: important patch I ran into this problem when using xen on Debian/Etch. I have several virtual xen instanses, and I name them using their fully qualified DNS domain name. These machines have failed to start automatically when I booted the host machine, and I just recently found out why. During shutdown, I was messages like this: Error:
2009 Feb 01
2
Bug#513842: xen-utils-common: please make pygrub available
Package: xen-utils-common Version: 3.2.0-2 Severity: wishlist Hi, It would be very useful it /usr/bin/pygrub was available -- it should be a symlink (or wrapper) that points to the real version in the Xen hypervisor. That would mean that the domain configuration for xen domains could be (relatively) static when upgrades are occuring between hypervisor versions. Thanks, Anand -- System
2007 Jan 17
0
Bug#407299: xen-utils-common: man 1 xm: warning: can't find numbered character 160
Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor When I try to read the man page of xm, these warnings show up: Manual page xm(1) line 1/tmp/zmanA5668G:641: warning: can't find numbered character 160 /tmp/zmanA5668G:643: warning: can't find numbered character 160 /tmp/zmanA5668G:651: warning: can't find numbered character 160 /tmp/zmanA5668G:652: warning: can't find
2007 Aug 10
1
Bug#437127: xen-utils-common: vif-common fails to identify ip address of ethernet device
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal On my systen, the script vif-common fails to retrieve the primary IP address of my ethernet device, preventing a domU from starting. I tracked this issue down to the file /etc/xen/script/vif-common. The function ip_of uses the following shell code to extract the address: ip addr show "$1" | awk "/^.*inet.*$1\$/{print
2007 May 07
0
Bug#422667: xen-utils-common: Init script outputs an error message while Xen is not installed any more
Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor Tags: patch Hi ! /etc/init.d/xendomains and /etc/init.d/xend complain about xen-utils-version not existing any more instead of failing silently. The following patch fix this problem. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1,
2007 Jun 27
0
Bug#430778: xen-utils-common: Here's proposed workaround script
Package: xen-utils-common Followup-For: Bug #430778 Here's a patch I made to have working rules here... feel free to comment/adapt. Hope this helps -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-xen-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8,
2010 Aug 31
0
Bug#570066: xen-utils-common: Please document this. See diff note in manpage
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]
2007 Jun 27
0
Bug#430778: xen-utils-common: NAT scripts not generic enough, and made for DHCP ?
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal I cannot find a use the network-nat and vif-nat provided in the general case, where I'd like to NAT between vifx.0 and ethx interfaces. I have setup the following in /etc/xen/xend-config.sxp : ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above.
2011 Nov 08
3
Bug#648029: xen-utils-common: /usr/lib/xen-common/bin/xen-toolstack (and thus /usr/sbin/xm) works with bash, but not dash
Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"
2009 Mar 10
0
Bug#519064: xen-utils-common: hvm migration fails because of missing /var/lib/xen/save
Package: xen-utils-common Version: 3.2.0-2 Severity: normal When I was trying to migrate (xm migrate) a guest from one host to another, it simply fails. On the source host the virtual machine gets destroyed without any warning message - on the destination host I see the following error message in /var/log/xen/xend.log [2009-03-10 08:01:22 9846] ERROR (XendCheckpoint:52) read_exact: EOF trying
2010 Nov 10
1
Bug#603099: xen-utils-common: requires python-xml
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>
2007 Jun 26
1
Bug#430676: xen-utils-common: network-nat increates insecure nat POSTROUTING MASQUERADE ?
Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal I'm not an expert in networking but I think that the current setup when using network-nat for domains is insecure. I've configured : (network-script 'network-nat netdev=eth1') (vif-script vif-nat) So when only domain 0 is started, I get the following : # iptables -L -n Chain INPUT (policy ACCEPT) target prot
2010 Sep 08
1
Bug#596048: xen-utils-common: /etc/init.d/xendomains stop saves images world readable
Package: xen-utils-common Version: 4.0.0-1 Severity: important When xen domUs are saved by running /etc/init.d/xendomains stop the memory images are saved world readable, so that every user on the system can read the memory dumps. The default mode of /var/lib/xen/save is 755, vm images are saved with mode 755. At least the save directory shoudn't be world readable. -- System Information:
2009 Jun 16
0
Bug#519064: xen-utils-common: /var/lib/xen/save gets created after reboot
Package: xen-utils-common Version: 3.2.0-2 Followup-For: Bug #519064 I've experienced the same problem (missing /var/lib/xen/save) on one host, but had no problem on another. Some investigation showed that /var/lib/xen/save gets created on some actions like a reboot whith a suspend/resume cycle. This problem will thus not be reproducable on quite some hosts, but is a real bug. The simplest
2008 Apr 21
1
Bug#477237: xen-utils-common: typo in /etc/xen/xend-config.sxp for xmlrpc configuration
Package: xen-utils-common Version: 3.2.0-1~bpo4+1 Severity: minor I use the version from backports, but it's still present in sid. In /etc/xen/xend-config-sxp : #(xen-tcp-xmlrpc-server-address 'localhost') #(xen-tcp-xmlrpc-server-port 8006) should be #(xend-tcp-xmlrpc-server-address 'localhost') #(xend-tcp-xmlrpc-server-port 8006) Small typo in a commented line, but