same problem here on karmic hypervisor. Seems to be something with the
"-S" switch which virt-manager uses to start the guests (as seen from ps
output). If I try and start the XP guest with -S, it just sits forever.
Issuing 'c' from kvm console (alt+2) just fails the boot process.
Trying to start an XP guest from virt-manager results in:
---------------------------------------------------
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 558, in startup
self.vm.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: monitor socket did not show up.: No such file or directory
Only way I can start this guest is by hand on the cli:
---------------------------------------------------
/usr/bin/qemu-system-x86_64 -M pc-0.11 -m 512 -smp 1 -name winsodxp -uuid
1fb923d5-7497-4d69-809b-786a4f94ece6 -monitor
unix:/var/run/libvirt/qemu/winsodxp.monitor,server,nowait -localtime -boot c
-drive file=/kvm/winxp3_s.img,if=ide,index=0,boot=on -drive
file=/kvm/iso/snoppix.iso,if=ide,media=cdrom,index=2 -net
nic,macaddr=ba:dd:c0:ff:ee:f5,vlan=0,model=rtl8139,name=rtl8139.0 -net
tap,fd=23,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice tablet
-sdl -k en-us -vga std
--
libvirtError: monitor socket did not show up.: Connection refused
https://bugs.launchpad.net/bugs/581934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
