similar to: Re: xend won''t start

I''ll step back to Xen stable, because of my network probs with Xen unstable. So I configured and compiled Xen 2.0.6, but I came to the following error after starting Xend: Exception starting xend: ''module'' object has no attribute ''VIRQ_DOM_EXC'' Traceback (most recent call last): File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 302,

After install of update snv_101b the xend daemon dosn''t start any more. This is what I saw in the xend.log file [2008-11-22 10:58:59 572] INFO (SrvDaemon:334) Xend Daemon started [2008-11-22 10:58:59 572] INFO (SrvDaemon:338) Xend changeset: Mon Oct 13 22:14:51 2008 -0700 15904:94bd0a643efe. [2008-11-22 10:58:59 572] INFO (SrvDaemon:345) Xend version: Unknown. [2008-11-22 10:58:59 572]

Short:     Which package do I need to install to get "auto/I18N/Langinfo/autosplit.ix"? Long: The problem I have was discussed almost a year ago (see this thread), but the resolution was not complete... I''m using Mark Johnson''s slim.py script (package list below), against repo=http://pkg.opensolaris.org/dev, followed by `pkg install xvm-gui` and `svcadm enable

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

Package: xen-hypervisor-3.4-i386 Version: 3.4.3~rc3-2 Severity: important Tags: sid After booting into the xen kernel, xm cannot run because xend is not running (the sysfs hypervisor is not populated) # dpkg -l | grep xen ii libc6-xen 2.10.2-6 GNU C Library: Shared libraries [Xen version] ii libxenstore3.0

Dear, After reboot server I can not start any VPS Client. Dom-0 is running, but when I start any Dom-U this error message appear: - Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err ''Device 0 (vif) could not be connected. Could not find bridge device xenbr0''). Please help, Wendy _______________________________________________

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 all, I have recently installed FC5 along with xen via yum. I''ve successfully rebooted using the dom0 (2.6.16-1.2133_FC5) kernel, started xend, and trying to start my first domU after following the instructions in the user guide. However, I keep receiving a kernel panic and an error about XENBUS timeout. Any help greatly appreciated as I am stumped. Should I be using the provided

hi, i''ve been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ... i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- not working, and not clear as to why not .entirely possible i''ve missed some new config req''ts ... what do I need to do to get xen behaving under 11.1? i''m

I just set up a new box that has been giving me trouble since I first cloned the xen repo to it. I started off with "error: can''t find a register in class ''BREG'' while reloading ''asm''" errors that I fixed by changing my gcc profile(gentoo) to nopie. That introduced me to a ''__guard'' error that I fixed by changing my gcc

Hi, I''m running a recent fedora-compiled xen kernel and the libs that come with it. I''m unable to start xend. I''ve tracked down the problem to the fact that xen.lowlevel.xc seems to be unable to talk to xen via /proc/xen/ privcmd. When I run the test program below, I get a "function not implemented" which I think results from the fact that an ioctl

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.

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Hello, I''ve noticed that if I try to restart Xend via "/etc/init.d/xend stop" then "/etc/init.d/xend start", I won''t receive any errors but then when trying to execute "xm" commands after the restart I get error asking if Xend is started. Is there anything else I need to make sure gets stopped/started with Xend? Another question ... domU reboots

Hello, Recently I ran yum update on a RHEL5 x86_64 machine and as part of the update, the following packages were installed: Updated: xen-libs-3.0.3-41.el5.x86_64 Updated: xen-libs-3.0.3-41.el5.i386 Installed: kernel-xen-2.6.18-53.1.14.el5.x86_64 Updated: xen-3.0.3-41.el5.x86_64 After the update, I rebooted the machine. Now, I cannot get xend to start:

Hi, I've been using CentOS & Xen on a server that has 2 VM's configured. The default configuration includes one physical iface that is propagated (by a default bridge) to the VM's. Since I wanted to configure additional physical iface, define a new bridge and propagate it to the viface-s of the VM's, i configured the bridge/phys. iface and brought it up (here are

I ran into this problem... http://lists.xensource.com/archives/html/xen-users/2006-11/msg00893.html i also tried everything under the sun for 4 days got nowhere, i was using Xen-3.0.4-1 trying all versions source and install, the current latest release for reason slackware 11.0 don''t like it. What i found is that using Xen-3.0.2-install which i also use on ubuntu dapper, the install

Hi, I am posting this message because past 36 hours have been nightmare for me. I finally have solved the problem I by temporarily moving put the xml files from /var/lib/xend directories reboot then xend started. And DomU''s were failing to start the above xml files I kept back and got all DomU''s back. I am very very surprised.I do not have any logical answer to this some one

Package: xen-utils-common Version: 3.4.2-1 Severity: important File: /etc/init.d/xend Tags: patch Hello, /etc/init.d/xend assume xenfs is present and doesn't start xend if not. This dirty patch makes xend start and XEN being operationnal with old flavour xen kernels. I use 2.6.31.5 with forwarded ported Xen 2.6.18 dom0 kernel patch but it should work with debian's 2.6.26 ---