similar to: xend fails to start says missing xen utils

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

Hi, I just installed a pv-ops Dom0 2.6.32.27 Kernel on a 64 bit non VT machine. Following instructions here http://wiki.xensource.com/xenwiki/Xen4.0 for 64 bit Ubuntu 10.04 apt-get install bcc bin86 gawk bridge-utils iproute libcurl3 libcurl4-openssl-dev bzip2 module-init-tools transfig tgif texinfo texlive-latex-base texlive-latex-recommended texlive-fonts-extra texlive-fonts-recommended

Hi, I have searched the question which I am asking.But if some one has mentioned on their blog or link some where they have mentioned as how they installed CentOS as DomU on Debian Lenny (dom0)running xen-3.2.1 and I should have a look Then please share it here. -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

I am doubtful that the default bridge is active. When I do following no where the bridge name comes how do I make sure bridge is active. openworld:/etc/xen# ifconfig eth2 Link encap:Ethernet HWaddr 00:26:b9:82:42:38 inet addr:192.1.100.150 Bcast:172.21.255.255 Mask:255.255.0.0 inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link UP BROADCAST RUNNING

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 :

-------- Forwarding messages -------- From: test <www.ryanliang@126.com> Date: 2012-11-13 14:37:51 To: xen-announce@lists.xen.org Subject: "virsh list" shows nothing//Fw:xend can''t start(CentOS 6.2 Final) Hi, I followed this article: http://www.howtoforge.com/virtualization-with-xen-on-centos-6.2-x86_64-paravirtualization-and-hardware-virtualization , to install

I am not clear with the working of hypervisor xen. How does an instruction executed by kernel in Ring0 of DomU gets mapped or executed by hypervisor and then is excuted in Dom0. Is this thing some where on the wiki page? -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I am not clear with the working of hypervisor xen. How does an instruction executed by kernel in Ring0 of DomU gets mapped or executed by hypervisor and then is excuted in Dom0. Is this thing some where on the wiki page? -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

When I try to create a PV domU, the VM starts up and I can access it through "xm console <id>", but when I try to connect to it through VNC, the port just hangs. I''ve tried using RealVNC and TightVNC, and also tried on Linux and Windows. All that happens on the client is that it says that the connection has established, and hangs there. I''ve tried running

Package: xen-utils-common Version: 3.3.1-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh

Package: xen-utils-common Version: 3.3.1-1 ck-a800:/home/kkadmin# /etc/init.d/xend start Starting XEN control daemon: xenstored xenconsoled xendFATAL: Failed to initialize dom0 state: Invalid argument . failed! xend.log [2009-07-12 06:55:40 15120] INFO (SrvDaemon:331) Xend Daemon started

Oh yes you can run XEN on VB. I am running the following config: ========= GUEST ========= [root@xenserver ~]# cat /etc/issue Citrix XenCloudPlatform Host 0.1.1-25823p [root@xenserver ~]# uname -a Linux xenserver 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 SMP Fri Jan 15 16:20:16 EST 2010 i686 athlon i386 GNU/Linux ======== HOST ======== OS Name: Microsoft Windows 7 Ultimate OS

Hi all, one of my servers crashed last sunday just right after a startup and I need to understand what was going on. I am running Windows 2008 R2 Standard Edition on Oracle VM 3.1 - Xen 4.1.2-OVM On sunday a scheduled task shutted down cleanly the vm. the shutdown started at Sun Jun 16 10:00:33 and it ended at 2013-06-16 10:00:46.938. xend.log says: [2013-06-16 10:00:45 7228] INFO

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-3.0.3-1 Version: 3.0.3-0-4 Severity: important # /etc/init.d/xend start Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in <module> from xen.xend.server import SrvDaemon File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/server/SrvDaemon.py", line 17, in <module> import

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

I have uploaded xend.log http://pastebin.com/XyQkEits and daemon.log http://pastebin.com/m0fpnzyR I was creating a DomU which had failed to boot via pygrub. It seems problem lies in Debian itself /var/run/xend/boot/ does not exist on the target system. Here is a snapshot http://farm5.static.flickr.com/4006/4626021351_d1a6f9c014_b.jpg Following was the error Traceback (most recent call last):

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

Package: xen-utils-common Version: 3.2.0-1~bpo4+1 Severity: minor I use the version from backports, but it's still present in sid. In /etc/xen/xend-config-sxp : #(xen-tcp-xmlrpc-server-address 'localhost') #(xen-tcp-xmlrpc-server-port 8006) should be #(xend-tcp-xmlrpc-server-address 'localhost') #(xend-tcp-xmlrpc-server-port 8006) Small typo in a commented line, but

Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access