Description of problem: PV domains get the correct VNC port but HV domains get configred to find the first free port. Version-Release number of selected component (if applicable): This first showed up in FC19 and is still in FC20 with lib How reproducible: The attached patch needs to be applied to fix this problem refer to the libvirt git comment http://libvirt.org/git/?p=libvirt.git;a=commit;h=b55cc5f4e31b488c4f9c3c8470c992c1f8f5d09c
Created attachment 892495 [details] patch from libvirt git
I just pushed the upstream patch to both v1.1.3-maint (used by Fedora 20) and v1.0.5-maint (Fedora 19) branches, so the next libvirt update will pull in this fix.
(In reply to Laine Stump from comment #2) > I just pushed the upstream patch to both v1.1.3-maint (used by Fedora 20) > and v1.0.5-maint (Fedora 19) branches, so the next libvirt update will pull > in this fix. v1.3.5 arrived a few days ago and it still has this bug.
I assume you mean 1.1.3.5. That version was cut/built on May 3, two days before this BZ was opened, so it doesn't have the fix. When there is a build with this fix, this BZ will be moved to MODIFIED status and a comment with details of the build will be posted.
(In reply to Laine Stump from comment #4) > I assume you mean 1.1.3.5. That version was cut/built on May 3, two days > before this BZ was opened, so it doesn't have the fix. When there is a build > with this fix, this BZ will be moved to MODIFIED status and a comment with > details of the build will be posted. Ok. Sorry to be a nag. When 1.1.3.5 showed up a couple of days later my first thougt was "WOW that was fast". What is the typical length of time from a package update being finalized to its showing up on the various update mirrors?
(In reply to Alvin Starr from comment #5) > What is the typical length of time from a package update being finalized to > its showing up on the various update mirrors? A couple of days. But, as Laine said, there isn't a libvirt 1.1.3 maintenance release yet that contains this bug fix. In the meantime you can try libvirt 1.2.4 from fedora virt preview, which has the fix: https://fedoraproject.org/wiki/Virtualization_Preview_Repository
libvirt-1.1.3.5-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libvirt-1.1.3.5-2.fc20
(In reply to Cole Robinson from comment #6) > (In reply to Alvin Starr from comment #5) > > What is the typical length of time from a package update being finalized to > > its showing up on the various update mirrors? > > A couple of days. > > But, as Laine said, there isn't a libvirt 1.1.3 maintenance release yet that > contains this bug fix. In the meantime you can try libvirt 1.2.4 from fedora > virt preview, which has the fix: > > https://fedoraproject.org/wiki/Virtualization_Preview_Repository I have patched rpms already so I am not too bugged by the delay in a maintenance release. I was sort of hoping to keep with RPMs that are as close to the default distribution as possible but I will give the preview repo a spin.
Package libvirt-1.1.3.5-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libvirt-1.1.3.5-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6586/libvirt-1.1.3.5-2.fc20 then log in and leave karma (feedback).
libvirt-1.1.3.5-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.