similar to: Error: ''features'' is an invalid keyword argument for this function

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

Xen Host Server OS: SLES10 Kernel: 2.6.16.21-0.8-xen x86_64 Hardware: Sun 4200 Memory: 12Gb Guest Domains (2 total) RHEL4-U3 2.6.16-xen x86_64 2Gb Swap 4Gb RAM 2 Nics bridged to seperate physical Nics (Public and Private) Systems come up normal and we are able to mount filer space to the guest domains and do work. However, at some point, the guest

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, since pinning the cpu cores to Dom0 and the DomUs the shutdown of the VMs doesn''t work anymore. When shutting down or rebooting a DomU the DomU just freezes after the shutdown process but won''t reboot or stop the DomU. The shutdown itself seems to be complete though. We can reproduce this problem on 4 different servers.

Hi all, I have strange problem with memory allocation on my xen server. My xen server: - distro: Debian squeeze - xen-hypervisor: xen-hypervisor-4.0-i386 4.0.1-1 - boot options: /xen-4.0-i386.gz placeholder dom0_mem=256M Dom0: - kernel: 2.6.32-5-xen-686 #1 SMP - /etc/xen/xend-config.sxp: (dom0-min-mem 256) (enable-dom0-ballooning no) DomU: - name: storage - distro: Debian

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

When I try to run xm shutdown, I get the following error messages. At this point, I am unable to perform any operations in dom0, and must reboot the server. I currently have the network information for each domU (2) configured in the sxp file as well as the interfaces file of the domU. Any help would be greatly appreciated. Error: Device 0 not connected Usage: xm list [options] [Domain, ...]

Package: xen-utils-common Version: 4.0.0-1 Severity: normal This is an offshoot of Bug#588888, but is really a separate issue. It appears that with hvmloader, the disk device names presented to the vm must by from a specific set that hvmloader knows how to emulate. Names like hd[a-c] and sd[a-c] work, but sr0 does not. While this makes sense, when you think about what hvmloader is doing, it is

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)

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

Hello, Please excuse my complete xen ignorance but I am hoping someone will be able ot help me out here. I recently built my first Xen box using a 2, 1TB drives in a raid configuration, 2TB total. I installed Xen, I am able to access it via XenCenter. However, I am trying to use some of that 2TB as a local datastore but for the life of me I cannot get it mounted, I keep on getting this error:

Hi, I am using xen 3.1.0 on opensuse 10.3, for more details see below. When I try to start the third domU, then this will not work, I get the error: Error: Boot loader didn''t return any data! When I shutdown an other one, I can successfully start the machine that failed, see my log below. The xen configuration files are all similar to this one: name="FTP"

Hi All, I am adding the patch mentioned here http://lists.xen.org/archives/html/xen-changelog/2013-02/msg00235.html I am getting errors on compiling Xen tools. My /tools/include/xen-foreign/mkheader.py looks different from the one that is mentioned in the above link, which I feel is due to version difference. I am using Xen 4.3.3 version. My understanding is that due to this version difference I

Hello, Where can I find a link (or docs) to *working* network config for xen 4.1.2? My tests (s. below) were not successful. Thank you in advance for any hints. Regards, Mark # --- root@xen411dom0:~# cat /etc/network/interfaces # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback auto bond0

Even after upgrading to 3.0.0-testing, I''m still seeing mountains of these messages in the event log. Dec 21 17:36:00 xen1 kernel: set_rtc_mmss: can''t update from 60 to 6 Dec 21 17:36:31 xen1 last message repeated 31 times Dec 21 17:36:59 xen1 last message repeated 28 times Dec 21 17:37:00 xen1 kernel: set_rtc_mmss: can''t update from 61 to 7 Dec 21 17:37:31 xen1 last

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

Hi, I have set up an ubuntu edgy guest domain on a fiesty host domain. The installation was successful but on running xm create -c baseimage, I get the following error message: Error: (22, ''Invalid argument'') The problem seems very similar to the one here: http://lists.xensource.com/archives/html/xen-users/2007-07/msg00361.html but I''m not able to figure out what the

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

Hi, I have a problem with networking under XEN, I hope someone can help me out. The problem is that after some time (a day or so) the network suddenly stops working, and it takes some waiting and/or a reboot to fix this. I''m running XEN 3.1.0-rc7 on an Intel Core2 (x86_64). It''s a Fedora 8 system, with the following packages: o Xen version 3.1.0-rc7-2950.fc8

I am doubtful that the default bridge is active. When I do following no where the bridge name comes how do I make sure bridge is active. openworld:/etc/xen# ifconfig eth2 Link encap:Ethernet HWaddr 00:26:b9:82:42:38 inet addr:192.1.100.150 Bcast:172.21.255.255 Mask:255.255.0.0 inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link UP BROADCAST RUNNING

It is rc2-pre. Stubdom fails again.   Boris --- On Fri, 4/10/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] First release candidate for Xen 3.4.0 To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Keir Fraser" <keir.fraser@eu.citrix.com> Date: Friday, April