similar to: xen-4.0.0: Could not connect to DomU console

Resent of mail sent on 28.04. xend: fix bug in option parsing If you enable legacy tcp xmlrpc in xend''s config but omit to enable ssl the following backtrace is generated when starting xend: [2010-04-28 16:09:04 15754] ERROR (SrvDaemon:349) Exception starting xend (''NoneType'' object has no attribute ''rfind'') Traceback (most recent call last): File

Package: xen-utils-unstable Version: 3.3-unstable+hg17961-1 Severity: important if I try to start or restart xend, I get this errors: /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-unstable/bin/xend", line 146, in <module> sys.exit(main()) File "/usr/lib/xen-unstable/bin/xend", line 123, in main

Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to

debian/patches/tools-python-prefix.diff removes auxbin.pathTo and replaces it with auxbin.path_bin and auxbin.path_boot. However there are still references to auxbin.pathTo in xend. The attached switches those usages to the correct new function. Without these I get: Error: 'module' object has no attribute 'pathTo' when trying to start a guest with

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

Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',

Hello, I don't know if this question ought to go here, or rather on R-devel, so please bear with me. I'm interfacing to R via RPy (rpy.sf.net) and an embedded Python interpreter. This is really quite convenient. I use this approach to calculate the correlation coefficient of 1 independent dataset (vector) with 4 dependent vectors. It'd be nice if that could be done in 4 parallel

Hello, I don't know if this question ought to go here, or rather on R-devel, so please bear with me. I'm interfacing to R via RPy (rpy.sf.net) and an embedded Python interpreter. This is really quite convenient. I use this approach to calculate the correlation coefficient of 1 independent dataset (vector) with 4 dependent vectors. It'd be nice if that could be done in 4 parallel

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

hi all, When i tried to install debian as a new guest VM in paravirtualized mode on Xen the following error occurs. please help me to resolve the problem.. Unable to complete install ''<type ''exceptions.ValueError''> Invalid install location: Opening URL http://172.16.0.31:8088/debian1 failed.. Traceback (most recent call last):   File

Hello, i have two xen hosts servers configured to support migration of domus, but when i try to migrate, the command never ends, i can see on the remote server the machine with xm list but the machine is not accesible, and on the own server i see migrating-{machine_name} and i have access to it. Every server have one nic, with public ip (that is using with xenbr0), and i have a virbr0 configured

Hi everyone, i have a problem on a running xen installation. The server on which the following problem occurs manages 7 VMs at the moment. Now I wanted to create a new one. After sending the xm create command I get the following error: Using config file "/etc/xen/de-smartnet-asterisk". Error: Creating domain failed: name=de-smartnet-asterisk In my xend.log I can find the following

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello. I''m having a quite big problem with xen and I''m pretty much stuck with it by myself, so hopefully someone can help me out with this. Symptoms look like this: tvsrv1:~# xm create ns1 Using config file "/etc/xen/ns1". Error: Creating domain failed: name=ns1 And relevant parts from the xend.log: [2010-02-02 11:35:18

Hi all, I just compiled an installed the Xen Hypervisor, Tools and a new Kernel from the 3.1 source. The dom0 is running without problem and the xm seems to work fine, too (tried xm info, xm list, xm dmesg). Unforunately on creation of a domU I always get an error using a config file and a domU image that is definitley working (at least with 3.0.4): Using config file

Hi Bastian, I'd like to propose backporting the following changesets from upstream xen-unstable into the xen-3 package. With these it is possible to boot a default installation of Squeeze (using d-i) in a domU using pygrub. 20480:c2c2e67b8198 pygrub: if default entry is "saved" then use first entry. 20481:8f4e0adc2b3b pygrub: expands tabs before displaying menus. 20485:086a6a0c3f37

Hi everyone,  I am using bio3d package for some sequence analysis because of its nice integrated MUSCLE execution. However, I have been encountering some errors while I was running seqaln function, which calls for installed MUSCLE program. In my case, I stored the MUSCLE program on the desktop with pathway of "./Desktop/muscle/src/muscle". I had no problem running MUSCLE directly from

Hello, when I try to start xend I receive this error: root@xenized:~# 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", line 36, in <module> from xen.xend.server import SrvDaemon File

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

user debian-release at lists.debian.org usertag 469013 -goal-python2.5 retitle 469013 Python API memory handling bug in unused code path found 469013 3.0-unstable+hg11561-1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in xen-unstable-3.0-unstable+hg11561/tools/pygrub/src/fsys/ext2/ext2module.c) is not actually compiled and the results shipped[1]. As such,

Package: xen Version: 4.0.1-1 Severity: serious User: debian-python at lists.debian.org Usertag: python2.6 The package build-depends on python2.5-dev, which is not the default python version for squeeze. The package should be rebuilt with python2.6, either build-depending on python-dev (recommended) or python2.6-dev.