Red Hat Bugzilla – Bug 240828
When device is attached to VM in virt-manager, information of VNC port number is lost.
Last modified: 2009-05-09 18:26:21 EDT
Description of problem:
In virt-manager, when device(Disk and NIC) is attached to inactive VM that has
fixed VNC port number, information of VNC port number is lost.
Version-Release number of selected component (if applicable):
changeset : c60eab8f4ac6
Steps to Reproduce:
1. Create VM that has fixed VNC port number in virt-install.
# virt-install --vncport=<port number> ...
2. Shut down VM
3. Attach device to VM in virt-manager
4. Start VM
5. Display a port number of VM
# virsh vncdisplay <domain>
Port number unlike a port number set in virt-install is displayed
Port number set in virt-install is displayed.
This is a little odd - the port number is in the XML we get out & feed back in,
so I'm surprised its being lost. Can you capture output of 'xm list --long
<domain>' before & after adding the device. Also can you attach the
/var/log/xen/xend.log & /root/virt-manager/virt-manager.log files
Created attachment 155217 [details]
Log of Xen and virt-manager and an output of "xm list --long <domain>"
Attached file includes the following:
- xend.log : Log file of Xend
- virt-manager.log : Log file of virt-manager
- before.sxp : Output of "xm list --long <domain>" before
adding the device.
- after.sxp : Output of "xm list --long <domain>" after
adding the device.
change QA contact
I have a similar issue. If I add a vnc graphics drive through virt-manager and
set it to a static port it is created as 'automatically-allocate'
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
> Reporter, could you please reply to the previous question?
Can you tell me waht is 'the previous question' ?
If you are talking about comment#1, reporter(Masayuki Sunou) has
replied about it at comment#2.
change the status to ASSIGNED
The problem is that libvirt is incorrectly reading the static vnc port from xend (in fact, it isn't reading it at all!). Reassigning to libvirt.
I've also posted a patch upstream which adds some tests for this and fixes the bug, so when/if that is accepted we can move this to POST.
I checked that this issue is solved by virt-managerCS901, virtinstCS582 and libvirtCL1.1501 on Fedora8.
Awesome, moving this to POST. This should be closed when the next libvirt release (probably 0.4.6) makes it way to fedora 8/9.
This should be addressed in current libvirt release available in F9 updates-testing, 0.6.1
libvirt-0.6.1-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing-newkey update libvirt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-2407
This bug was fixed in a version much older than 0.6.1. In fact, I think 0.4.6 was pushed to F8, which is where this bug was originally filed. Closing as CURRENTRELEASE.