Hello,
I use the newest xen-unstable on my server, until I updated from
xen-testing to xen-unstable I'am unable to start a domU domain.
If I start a domain with 'xm create -f <domainname>' there is no
response, I'am only able to press CTRL+C to abort this. here is a strace
output of the command:
socket(PF_FILE, SOCK_STREAM, 0) = 3
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
connect(3, {sa_family=AF_FILE, path="/var/lib/xend/xend-socket"}, 27) = 0
send(3, "POST /xend/domain/sheldon HTTP/1"..., 151, 0) = 151
send(3, "op=wait_for_devices", 19, 0) = 19
recv(3,
After pressing CTRL+C, I can see the domain in 'xm list' with status
'p', but the only operation I'am able to do, is to destroy the domain.
It looks like xm waits for xend for an answer but never get it, right?
Does anyone know what the problem is?
greetings
Torben Viets
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|