Xen issues after upgrading to 12.1

Hi All,

After upgrading to 12.1 I am no longer able to start existing Xen domains or create new ones…

knovapg1:~ # uname -a
Linux knovapg1 3.1.0-1.2-xen #1 SMP Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux

knovapg1:~ # xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 7767 2 r----- 17.4
KM8DevKev 4096 2 0.0

knovapg1:~ # xm start KM8DevKev
Error: Unable to connect to xend: Connection refused. Is xend running?

knovapg1:~ # ps aux | grep xen*
root 16 0.0 0.0 0 0 ? S 10:00 0:00 [xenwatch]
root 17 0.0 0.0 0 0 ? S 10:00 0:00 [xenbus]
root 1233 0.0 0.0 10728 1088 ? S 10:00 0:00 xenstored --pid-file=/var/run/xenstored.pid
root 1342 0.0 0.0 90488 608 ? SLl 10:00 0:00 xenconsoled --pid-file=/var/run/xenconsoled.pid
root 1395 0.0 0.1 117292 12408 ? S 10:00 0:00 /usr/bin/python /usr/sbin/xend start
root 1400 0.0 0.2 710632 17592 ? SLl 10:00 0:00 /usr/bin/python /usr/sbin/xend start
root 4362 0.0 0.0 6792 872 pts/0 S+ 10:25 0:00 grep --color=auto xen*

I’m not sure if this is related or not but he following entries appear in /var/log/warn…

Nov 21 10:00:48 knovapg1 kernel: 13.008739] Unable to read sysrq code in control/sysrq
Nov 21 10:00:48 knovapg1 kernel: 13.526083] Unable to read sysrq code in control/sysrq

Thanks in advance for any help you can provide.

did u manage to solve it mate? I am in the same boat… any help?

Me too! One thing that I’ve found is that the file /etc/libvirt/libvirtd.conf has every line #'d out. I’ve been fiddling with this for a couple of days now - new SuSE distro, new Samsung i5 laptop, first foray into 64bit architecture, I’ve brought the whole kaboodle to it’s knees 2 or 3 times. Any suggestions greatly appreciated.

dmk