Bug 434580

Summary: virt-manager cannot start guest machines anymore
Product: [Fedora] Fedora Reporter: Michel Lind <michel>
Component: virt-managerAssignee: Daniel Berrangé <berrange>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: hbrock
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-28 05:02:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Windows XP guest configuration none

Description Michel Lind 2008-02-22 21:42:28 UTC 
Description of problem:
virt-manager worked fine for me until a couple of days ago. After today's
update, it won't start the guest machines -- it does not even get to BIOS screen.

Version-Release number of selected component (if applicable):
0.5.3-2.fc9.x86_64

How reproducible:


Steps to Reproduce:
1. virt-manager
2. Attempt to run a guest machine 
  
Actual results:
With selinux non-enforcing:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 472, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 379, in startup
    self.vm.create()
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 240, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: virDomainCreate() failed QEMU quit during console startup
bind() failed


Expected results:
Should work

Additional info:
Comment 1 Michel Lind 2008-02-22 21:42:28 UTC 
Created attachment 295680 [details]
Windows XP guest configuration
Comment 2 Michel Lind 2008-02-22 21:48:55 UTC 
My mistake -- the VM in question was set up before I turned on Vino, and for
some reason it ended up with a hardcoded VNC port of 5900, which is now in use