Univention Bugzilla – Bug 35425
UVMM for UCS-4.0
Last modified: 2014-11-26 06:54:20 CET
univention-virtual-machine-manager-node # kvm
r52015 | Bug #35425: clone UVMM for UCS-4.0-0
r52016 | Bug #35425: Clone UVMM-node for UCS-4.0-0
r52024 | Bug #35425: Clone noVNC for UCS-4.0-0
r52026 | Bug #35425 UVMM: UCS-4.0 version bump
→ uses python2.6
r52034 | Bug #35425 noVNC: Fix python2.7 usage
*** Bug 35361 has been marked as a duplicate of this bug. ***
I've added a changelog for all migrated packages: r52983
Created attachment 6080 [details]
univention-virtual-machine-manager-daemon installs ok
univention-novnc installs ok
upon installing univention-virtual-machine-manager-node-kvm
an error occurs (see attached screenshot) and server is not reachable via network anymore
by setting ucr uvmm/kvm/bridge/autostart=manual eth0 and rebooting the server is accessible again
Running a KVM server with DHCP-client enabled is insane: For KVM we copied the Xen behavior to rename the physical interface "ethX" to "pethX", which allows us to create a bridge with that name "eth0" instead. As "dhclient" is still using the old name "eth0", it is now confused as the interface was renamed to "peth0" behind its back, leading to the network failure.
Long-term the rename-script should be removed.
For now I strongly recommend to reboot the server after installing KVM (or Xen) because of the network-bridge-dance.
(In reply to Philipp Hahn from comment #7)
> Long-term the rename-script should be removed.
That's Bug #33694.
FYI: post-installing u-v-m-n-kvm worked for me even with DHCP-client.
RFC: What was the exact setup you were testing?
it is working now.
i was using xen2 for testing, no other modules installed.
UCS 4.0-0 has been released:
If this error occurs again, please use "Clone This Bug".