F10a virt-manager

John Summerfield debian at herakles.homelinux.org
Tue Aug 12 15:00:51 UTC 2008


Does anyone have virt-manager working on F10a?

I have configured it with consolehelper to work for mere mortals w/o 
passwords. It works fine that way on f9, as it should.

On F10a it silently fails. This is all I see:
[summer at potoroo ~]$ virt-manager
[summer at potoroo ~]$
This is a little unusual, I don't know whether strace has gone mad, or 
there is a real problem:
[summer at potoroo ~]$ strace -f -o /tmp/virt  virt-manager
PANIC: attached pid 6053 exited
[summer at potoroo ~]$

These are the last few lines of the above trace:
6052  read(4, 0x16796a4, 4096)          = -1 EAGAIN (Resource 
temporarily unavailable)
6052  poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}], 2, -1) = 1 
([{fd=3, revents=POLLHUP}])
6052  --- SIGCHLD (Child exited) @ 0 (0) ---
6052  rt_sigreturn(0x11)                = 1
6052  wait4(6053, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG, 
NULL) = 6053
6052  select(5, [4], [4], NULL, NULL)   = 1 (out [4])
6052  writev(4, [{"+\0\1\0"..., 4}], 1) = 4
6052  select(5, [4], [], NULL, NULL)    = 1 (in [4])
6052  read(4, 
"\1\2l\0\0\0\0\0\10\0\200\5\0\0\0\0\300v\255\201\210\177\0\0\0\0\0\0\0\0\0\0"..., 
4096) = 32
6052  read(4, 0x16796a4, 4096)          = -1 EAGAIN (Resource 
temporarily unavailable)
6052  select(5, [4], [4], NULL, NULL)   = 1 (out [4])
6052  writev(4, 
[{"\1\0\n\0\5\0\300\6\206\0\0\0\234\377\234\377\1\0\1\0\0\0\0\0\0\0\0\0\0\n\0\0\1"..., 
92}], 1) = 92
6052  read(4, 0x16796a4, 4096)          = -1 EAGAIN (Resource 
temporarily unavailable)
6052  exit_group(0)                     = ?
(END)

It's odd in that files are not closed, and in that it terminated 
immediately after a failed read.

This is where "4" is created:
6052  socket(PF_FILE, SOCK_STREAM, 0)   = 4
6052  connect(4, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X0"...}, 110) 
= -1 ECONNREFUSED (Connection refused)
6052  connect(4, {sa_family=AF_FILE, path="/tmp/.X11-unix/X0"...}, 110) = 0

so it seems likely that the PANIC message arises from the problem.

There's noting obvious (to me) in ~/.xsession-errors


Running as root ("sudo /usr/sbin/virt-manager") it hangs trying to 
connect to qemu.

xen is, of course, out of the question.





More information about the fedora-test-list mailing list