similar to: Anyone use Driver domain

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

Comparing my last know working configuration with the current one, it appears to be gagging on the new localhost\.localdomain that is in the configuration file. I don''t know if this got added by my machine when compiling. diff -ur xen-3.0-testing.hg/install/etc/xen/xend-config.sxp xen-unstable.hg/install/etc/xen/xend-config.sxp --- xen-3.0-testing.hg/install/etc/xen/xend-config.sxp

In the xend-config.sxp scritp I set: (xend-http-server yes) (xend-port 8000) (xend-address '''') When I point my browser at it, the page that comes up only displays two lines, each of which are just a ''/'' that is a link to itself. What am I missing? Thanks, Kirk _______________________________________________ Xen-users mailing list

# HG changeset patch # User Lutz.Dube # Node ID ca2c8c262dbaa6b2521cec60af7cd688dabdf850 # Parent 8992134dcfd0b9e1e86f4111e68a8aa48bd33c3c Values of cpu_weight and cpu_cap are lost after xend restart For managed domains in state ''halted'' I always get default values for cpu_cap / cpu_weight after xend restart. This is because the names of parameters differ between a SXP file to

Hi! I''m not new to Xen but I''m new to this list. I''m having a truely bizarre problem with Xen bridged networking at the moment. This is a new install, on RHEL4. The symptom is that any domU set up simply fails to talk to anything else. It''s there, and running, and it has an ethernet device, but there''s never any response. After digging through the

Hello, I use xen for a few months now and I upgraded to opensuse 10.3 with xen 3.1 (64bit versions) recently. Everything works fine, but there is a problem when I change xend-config.sxp to use my own network script (it''s slightly modified version of network-virtual scripts from http://en.opensuse.org/Xen3_yet_another_Virtual_Network_Concept ) instead of default network-bridge script.

Greetings and Happy Holiday Season: I filed an open issue with Fedora installer and rpm because of the same error. I was suggested to look in the xend-debug.log for detailed logs on the problem. This is enabled in nano /etc/xen/xend-config.sxp by adding the following lines (logfile /var/log/xend.log.debug) (loglevel DEBUG) then removing the logs rm -f /var/log/xend.log rm -f

> From: Nico Kadel-Garcia <nkadel@gmail.com> > Date: December 28, 2006 6:32:42 AM EST (CA) > To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> > Cc: "Bhatia, Nikhil" <bhatia@ornl.gov>, xen- > devel@lists.xensource.com, xen-users@lists.xensource.com, > ian.pratt@cl.cam.ac.uk > Subject: Re: [Xen-users] RE: [Xen-devel] Xen-3.0.3 migration problems > >

Hello with XEN 3.4.x antispoof=yes works on a bridge setup. I am using this line in xend-config.sxp (network-script ''network-bridge antispoof=yes'') It creates this under IPTABLES FORWARD chain: ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in peth0 Under XEN 4.0.1 it is not working, it does not create a IPTABLES rule. Customers can

Hi, I''ve just made changes on xend config xend-config.sxp file, but I''m not sure if restarting xend daemon also restart domUs? Thoughts? thanks in advance. -- Regards; Israel Garcia _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

This is all on SuSE enterprise 10 Our server was moved to a new location last night. After powerup there was no sign of networking so our ISP reconfigured the box. Outbound connectivity had previously been through eth1 but is now through eth0 Since restarting Xen I now have no network connectivity through the hosts. I have tried to provide all the relevant details below. If anyone has a moment

I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all the virtman functions. The errors I got indicate some missing python classes, specifically xen.install. I''m not sure why. This is what I get when I try to run virtman from the command line. If I try to run it from yast i get nothing.

When a domain is in the process of shutting down there is a small window when the domain is known to XenD, but it will be unable to form an SXPR for it due it being in the middle of device hot-unplug. This causes the ''xm list'' command to totally fail with an error like # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information about all/some

-----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 folks, is there a tool to convert a vm''s classic config file to sxp? I tried "xm create OLDCONF -n" and pasted the output in a config file at /var/lib/xend/domains/SOMEFOLDER/config.sxp, but that did not make virsh recognize the vm at all (although I restrarted xend, which helps for example after virt-clone). I am trying this on Xen4 using Debian6. Dirk

Hi *.*, This is a continuation on the 2 NICs thread after some more testing. Just to remember my goal. --------------------------- I want to create a domU with 2 virtual NICS. One of them will contact the outside world, the other one will contact a VPN. No reason in concrete for choosing the bridging protocol, only because its the default one. I installed the dom0 with the 2 NICs active, with

Hi folks, I''m updating my xen server from a dom0 on debian sarge, using a self compiled xen 3.0.4 and a kernel 2.6.16, to a standard debian etch using the deb packages xen 3.0.3 and kernel 2.6.18. On the old server, all my hvm machines use vnc console and a password is set into xend-config.sxp and it works nice. On the new etch server, with the same hvms and configuration files,

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

Hi, I want to use xm on xen-api-server. So first, I uncomment the following lines in /etc/xen/xend-config.sxp: (xen-api-server ((9363 pam ''^localhost$ example\\.com$'') (unix none))) and then restart xend, it seems all right: # netstat -anp | grep 9363 tcp 0 0 0.0.0.0:9363 0.0.0.0:* LISTEN

what i am doing wrong? My vethX of xend-dom0 dont start. ---- dcgs0058:~# lspci |grep Ether 0000:06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 0000:07:08.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) dcgs0058:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:13:72:4E:7E:B3 inet addr:172.28.0.200