search for: total_available_memori

We''ve been looking in to support of 32bit domains on machines with large amounts of RAM. Working from the ballooning and reservation support added a few years ago: http://lists.xen.org/archives/html/xen-devel/2009-11/msg01277.html 32 bit domains eventually fail to boot with the following Xen complaint: xm create: Error: (4, ''Out of memory'', "panic:

Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from

I am running Xen on Debian wheezy. I switched from routed networking to bridged networking. Now I can''t seem to get eth0 to come up. When the network script tries to bring it up, it gets an error: RTNETLINK answers: File exists Any tips? details below brian root@trout:/etc/xen# egrep -v ''#|^ *$'' xend-config.sxp (network-script network-bridge) (vif-script vif-bridge)

Hi, we have a couple of nodes based on CentOS 6 and Xen4CentOS. Unfortunately some of these nodes keep crashing frequenly. We use the latest versions: # uname -r 3.10.43-11.el6.centos.alt.x86_64 # xm info host : vserver20 release : 3.10.43-11.el6.centos.alt.x86_64 version : #1 SMP Mon Jun 16 14:22:02 UTC 2014 machine : x86_64

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

Hi. I've set up a cluster with two Debian 6 nodes, running Xen 4 and libvirt 0.9 (from backports). My VMs run over a DRBD resource, to allow live migration between the nodes. I've successfully tried live migration using xm migrate, now I'd like to make it work using virsh, but cannot make it. Here's the error I'm getting: # virsh migrate efw xen+ssh://10.22.22.152/ error:

Hi, I followed Boris'' tutorial to the letter about installing Xen 4 on Ubuntu Lucid. Dom0 starts ok, and xm works, but virt manager can''t connect to xen:///. I''m pretty sure that the problem is with virt-manager''s configuration file. I run xen-4.0.1-rc3-pre with Kernel 2.6.31.13. Here''s xm list''s output: $ sudo xm list Name

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-common Version: 4.0.0-1 Severity: normal Hi, On system shutdown the 'xendomains' script appears to detect wrong guests: | Stopping libvirt management daemon: libvirtd. | Clearing ebtables rulesets: filter nat broute done. | Shutting down Xen domains: bev-d6x02(save).Error: Domain '1024' does not exist. | !(shut).Error: Domain '1024' does not exist. |

Package: xen-utils-common Version: 4.2.1-2 Severity: important After run xm create -c win2008.hvm Using config file "./win2008.hvm". Error: 'NoneType' object has no attribute 'rfind' /var/log/xen/xend.log: [2013-06-10 21:48:59 31935] ERROR (xmlrpclib2:181) Internal error handling xend.domain.create Traceback (most recent call last): File

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

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-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"

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Package: xen-utils-common Version: 4.1.2-3 Severity: important /etc/default/xen, which carries the TOOLSTACK setting, is not honored by xend init script. The xend initscript doesn't check for the value of TOOLSTACK. It just populates it in its initscript. lnx200-39:/etc/init.d# grep TOOLSTACK * xend:TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) xend: if [ -z

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

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

Package: xen-utils-common Version: 4.0.0-1 Severity: important When Xen is configured in routed mode, restarting xend fails because the script hotplugpath.sh is missing. Please see below for more information. *** root at eliott:~# /etc/init.d/xend restart Restarting Xen daemons: xend/etc/xen/scripts/network-route: line 20: /etc/xen/scripts/hotplugpath.sh: No such file or directory

Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was