similar to: [PATCH][RESENT] xend: fix bug in xend option parsing

Package: xen-utils-4.0 Version: 4.0.0-2 Severity: important xend does not start because of a bug in option parsing. Error described here: http://www.gossamer-threads.com/lists/xen/devel/172035 Patch: --- a/tools/python/xen/xend/XendOptions.py Mon Apr 26 12:13:23 2010 +0100 +++ b/tools/python/xen/xend/XendOptions.py Wed Apr 28 16:54:04 2010 +0200 @@ -207,18 +207,18 @@ def

Package: xen-utils-4.0 Version: 4.0.1~rc6-1 Severity: important Tags: patch The patch is not necessary for HVM DomU guests. The Error: 'NoneType' object has no attribute 'rfind' was fixed by installing xen-qemu-dm-4.0. [1] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588888 -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi everyone, I managed to install xen 4 on ubuntu lucid. I managed to read around what kernel configuration options are needed. The problem is that xend can''t start. If I try to run it I get errors from some python scripts. virt-viewer can''t connect to xend, also. I followed the steps in the Xen 4 wiki and the links from Boris'' blog. What should I do? These are the

Hi, I''m trying to install Xen on Ubuntu 11.04. I read somewhere (please correct me if this is wrong) that Ubuntu hasn''t had dom0 support since 8.04 LTS, and the recommended action was to grab a dom0-enabled kernel from Debian, so I did. I''m running 2.6.32-5-xen-amd64 and built Xen 4.1.1 from source. After installation and some troubleshooting, I tried to start

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.

Hi. I use xen-4.0.0 My domU successfully started, but when i tried to connect to DomU console i get error: root@debian-office:/opt/src/NexetaStor# xm console NexentaStor-EVAL-2.2.0 Unexpected error: <type ''exceptions.TypeError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/sbin/xm", line 7, in <module>

Hi. I use xen-4.0.0 My domU successfully started, but when i tried to connect to DomU console i get error: root@debian-office:/opt/src/NexetaStor# xm console NexentaStor-EVAL-2.2.0 Unexpected error: <type ''exceptions.TypeError''> Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/sbin/xm", line 7, in <module>

Hi, using btrfs with LVM snapshots seems to be confusing /proc/mounts After mounting a snapshot of an original filesystem, the devicename of the original filesystem is overwritten with that of the snapshot in /proc/mounts. Steps to reproduce: arnd@kallisto:/mnt$ sudo mount /dev/vg0/original /mnt/original [ 107.041432] device fsid 5c3e8ca2-da56-4ade-9fef-103a6a8a70c2 devid 1 transid 4

Hi, I downloaded XEN 3.1 source code on a fedora 6 machine. I did # make world # make install It did not give me an error then when I restarted the machine the Grub did not have 2 options. It had only one option that was the kernel. On loading the OS, when i gave # xend it gives the following errors: [root@localhost sbin]# xend ERROR Internal error: Could not obtain handle on privileged command

Hello ! I''m trying to run Xen on a EC2 AMI debian-6.0-squeeze-base-x86_64-20110417 (ami-35b68141) Following this how-to http://www.howtoforge.com/paravirtualization-with-xen-4.0-on-debian-squeeze-amd64 After installing the packages, I get : uname -a Linux ip-10-241-22-60 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux uname -r 2.6.32-5-xen-amd64 Then I do :

Dear Xen Users, at first, sorry for my bad english and in fact my post is wrong here, please light me the way to the right board. My Xen Host runs since two years without a problem. As of today, some v-servers was not reachable anymore. I did a short xm top and got dozen of erros. I did a reboot of the Host. Thereafter i get the same error messages when trying to start xend (/etc/init.d/xend

Hello, i´ve installed a Suse 8.1 minimal System with iproute 2.4.7 and iptables, Suse default Kernel 2.4.19. When I start the Wondershaper 1.1a Script I get the following Error: CBQ: "allot" is required to set WRR parameters. /home/skripte/./wshaper: line 72: allot: command not found CBQ: "allot" is required to set WRR parameters. /home/skripte/./wshaper: line 78: allot:

Hi everyone, I'm very new to R and I like to learn a lot... actually I have a little problem concerning errorbars with xyplot. My data look like run target hemi x 1 1 Nichts Links 0.0007743240 2 2 Nichts Links -0.0008153365 3 1 Target Links -0.0015825950 4 2 Target Links 0.0088743785 5 1 Nichts Rechts 0.0015898995 6 2 Nichts Rechts -0.0011465190 7 1

Dear Community, sorry for the somewhat dumb question. Maybe someone has any pointer to how to setup the RED queue to mark pakets with ECN. In particular what are appropriate parameter settings for limit, min, max, etc. All my trials end up with either "RTNETLINK answers: Invalid argument", although the command line (at least for me) looks fine in regard to what is said on the

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

Hi, I have been trying to get Xen 3.1 running on Fedora 7 since yesterday and no luck. At the beginning I thought it was a problem with teh installation of Fedora 7 so I reinstalled it. Still, I have the same problem. I have never had this problem with Xen (FC5,FC6). The xend.log (below) includes a line "VmError: Device 0 (vif) could not be connected. Hotplug scripts not working."

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Hi, My base system is Gentoo x64, and I compiled my kernel with Xen paravirtualization support. The kernel can boot without any problem in native mode. But when boot in Xen mode, I cannot start the xenstored service. This is my grub config file: title Gentoo x64 kernel-3.2.11-gentoo root (hd0,2) kernel /boot/kernel-3.2.11-gentoo root=UUID=38213e99-588e-4a7d-a215-8835f7afb1c4\