similar to: Bug#441249: Bug#441249: xen-hypervisor-3.0.3-1-i386-pae: "Problems using XEN when Quagga is running"

Hi, I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and I''m facing some problems when I start the DomU. In detail, it means that the DomU IP-Adress will not be implemented in the Kernel routing table after starting the domU via "xm create /<path +configfle>" After making a "netstat -nr" it will not show the IPadress bound to the

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

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying

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

The principle was not made any changes to occur this problem. We infra have dc3 and dc4 ADDC. root at dc3:/etc/samba# samba -V Version 4.7.7-Debian (van-blle apt) Result of gpupdate /force in a joined computer client: C:\>gpupdate /force > Updating Policy... > User policy could not be updated successfully. The following errors were > encountered: > The processing of Group Policy

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341875694 -3600 # Node ID 1d33f934dd675a1b91d2d4e0fa2d2a873a8debf5 # Parent 54384951de02e2db909116d64aa6a65d06ffa708 hotplug: fix ip_of for systems using a peer-to-peer link This is from an old Debian bug at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437127 I'm slightly inferring what the configuration

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341875694 -3600 # Node ID 1d33f934dd675a1b91d2d4e0fa2d2a873a8debf5 # Parent 54384951de02e2db909116d64aa6a65d06ffa708 hotplug: fix ip_of for systems using a peer-to-peer link This is from an old Debian bug at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437127 I'm slightly inferring what the configuration

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

Hi guys! I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU (not an image) started. Attached you will find /etc/xen/xen1.conf and the result of "xm create -c /etc/xen/xen1.conf" in xen1.log. Can you help me? What did I wrong? Is it about the fstab in xen1 (see also attached)? Many thanks in advance! Regards Stefan

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

Hi folks, Host - Debian Etch Guests - Debian Etch. Performed following steps to create duplicate guest, a mail server. 1) # cp /etc/xen/guest-1.cfg /etc/xen/guest-2.cfg edit guest-2.cfg changing the settings of:- disk = [''file:/vserver/domains/guest-2_directory/disk.img,hda1,w'', ''file:/vserver/domains/guest-2_directory/swap.img,hda2,w''] # Hostname name

I''m not able to start, destroy, or delete a DomU: > xen1:~ # xm start test4 > Error: Domain is already running > Usage: xm start <DomainName> > > Start a Xend managed domain >   -p, --paused                   Do not unpause domain after starting it    >   -c, --console_autoconnect      Connect to the console after the domain   

Hi have been trying to get winbind working on Solaris 9 but to no effect. version info: samba: 3.0.0 openldap: 2.1.23 kerberos: MIT 1.3.1 Have followed the instructions in every howto, usenet posting I could find: nscd not running created relevant links in /lib and /lib/security/sparcv9 applied patch for nsswitch as recommended kinit -e works net ads join works wbinfo -t works wbinfo -u

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: normal My setup is a basic one. No changes to the /etc/xen/* files. Network in a domU works perfectly fine. But, after shutdowning a domU, I can see the following lines in /var/log/debug: May 6 10:31:45 vaio logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/18/0 May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge:

Hi, I install a guest Fedora inside the host Fedora. When I use the service xend status to check the status of xend. It shows xend is running. However when I use xm create xen1 to start the guest domain xen1, it failed. The corresponding file xen1 is in /etc/xen/xen1. The error msg is as follows: [root@phillis xen]# xm create xen1 Using config file "./xen1". Going to boot Fedora

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",

Posted this to xen-users back in Oct (http://www.gossamer-threads.com/lists/xen/users/186768), but just confirmed that I''m still seeing this behavior on 4.1. Polling the UCE-SNMP-MIB::ssCpuRawIdle counter results in a total that''s double the actual number of cpu''s on the system, so for example: nms ~ # snmpwalk -v 2c -c ''XXX'' xen1

Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when