similar to: error when starting xen

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.

Followed all the howto instructions and when this runs I get the following: (with debug on) [root at quigonn named]# /usr/local/samba/sbin/samba_dnsupdate -d 200 /usr/local/samba/lib/python2.4/site-packages/samba/__init__.py:44: RuntimeWarning: Python C API version mismatch for module ldb: This Python has API version 1013, module ldb has version 1012. import ldb

Hi *, when I try to start this config kernel = "/boot/vmlinuz-2.6.11-xenU" memory = 128 name = "Virtual1" vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] disk = [ ''phy:vg00/domu01_lv,sda1,w'' ] root = "/dev/sda1 ro" extra = "4" I get this errors in xend.log (tried two times): [2005-05-23 13:37:22 xend] INFO

After a recent power cycle of our building, I discovered that the xend pyc files have full paths to the install directory where I built the xen tools. Turns out the xend python process calls stat() on these pyc filenames. In this case, the automounter was broken so the stat() hung and xend failed to start. I was very suprised to see the full path to the dist/install *.py files in the strace

Hi to all. I''m installed XEN3.1 correctly but I''m some problem to start it. XEN start but I received this message: VFS: Cannot open root device "hda5" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) This is strange because my grub is configured like this:

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

Hi, xstransact and xswatch are well designed python interface that can be used by third party utils rather than only in xend. But the logging approach here binds xswatch to xend and prevent it from being used by other utils. This patch removes the dependency on XendLogging from xswatch. Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com> regards, zhigang

Hi, I''d like to test the stability of live migration during heavy load of domU. scenario: - both dom0s and domU are running on Debian Sarge. - script on dom0 triggers live-migration to the other dom0 - domU is running I/O tests, e.g. bonnie++ - domUs root- (ext3) and swap fs is stored on two partitions in a san - san is connected using fibre channel cards to both dom0s - san in dom0

Hi all, I''ve been looking though my xend.log and have noticed a reoccuring error: [2006-01-12 09:45:36 xend] DEBUG (XendDomainInfo:634) Closing console, domain 2 [2006-01-12 09:45:36 xend] INFO (XendRoot:112) EVENT> xend.domain.exit [''ipcop'', ''2'', ''crash''] [2006-01-12 09:45:36 xend] INFO (XendRoot:112) EVENT>

Moi! I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly. I''m still able to boot dom0 and start domUs but networking doesn''t work anymore. xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is used. Interface appears in domU and all seems to be fine, except no any data doesn''t move in any direction. I can''t even ping

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

Fedora is keen to stop using PyXML and I have been sent a bug report https://bugzilla.redhat.com/show_bug.cgi?id=842843 which includes a patch to remove the use of XMLPrettyPrint in tools/python/xen/xm/create.py . I am going to try this in the Fedora build, but I was wondering if it makes sense to do this in the official xen releases as well. Michael Young

Hi I downloaded Speex 1.0.1 and I am not able to compile the source files (examples) speexenc.c and speexdec.c What are the libraries needed to run the above examples ? I am using VC++ 6.0 /Win XP. I addes ogg.lib and libspeex.lib files. do I need to any more lib files ? Please advise. Regards Ravi. <p>--------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95

Xen patchbot -unstable wrote: > # HG changeset patch > # User emellor@leeni.uk.xensource.com > # Node ID da24df1ea484cf72dc9d367d52e828777e0e20cd > # Parent c1bb4eb565296bdb00aed84fcc877befbcebd8e9 > Improve error handling, in particular fixing the ProtocolError that is thrown > when a domain is specified by the user that does not exist. Added a few > error codes -- many

Xend lifecycle changes -- basic functionality. xend/XendDomain.py | 287 ++++++++++++++++++++++++++++++++++---------- xend/XendDomainInfo.py | 203 +++++++++++++++++++++++-------- xend/XendRoot.py | 8 + xend/server/XMLRPCServer.py | 2 xm/create.py | 4 xm/main.py | 29 +++- xm/new.py | 68 ++++++++++ 7

On 20 October 2010 at 09:57, Aman Thakral wrote: | Thanks for your reply. I just created a link to | /usr/local/lib/R/lib/libRlapack.so in /usr/local/lib. It works now. | I'm just curious, is this the "right" way to do it? Is there a better way? I am coming to this a little late but ... it is a band aid to a self-inflicted wound. You only have libRlapack because you built R

I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning:

I had this exact same problem with 2.0.7. I had done a little investigation and found scheduled_work gets called to schedule the shutdown in the user domain kernel, but the shutdown work that gets scheduled never actually gets called. I''m glad someone else is seeing this same problem now :-) Like you, it worked a number of times in a row, then would fail, and it didn''t seem to

Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9