Am 03.10.2013 11:49, schrieb Stefan G. Weichinger: > Am 03.10.2013 11:45, schrieb Stefan G. Weichinger: > >>> Are you running stp. I was having a problem that when I did anything to >>> libvirt it would disconnect the bridge and stp reconfigured. Turning it >>> off fixed it (am using openvswitch) >> >> Could you specify where to turn that off? I don't know stp ... sorry. > > Ah, it's a bridge "feature" ;-) > > I assume I should turn it off on the KVM server. Will do now. > >
No change: I get Fehler beim Anwenden von Ă„nderungen: Interner Fehler: Client Socket ist geschlossen Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/details.py", line 2022, in config_apply ret = self.config_disk_apply(key) File "/usr/share/virt-manager/virtManager/details.py", line 2323, in config_disk_apply return self._change_config_helper(df, da, hf, ha) File "/usr/share/virt-manager/virtManager/details.py", line 2566, in _change_config_helper self.vm.refresh_xml() File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 115, in refresh_xml self._xml = self._XMLDesc(self._active_xml_flags) File "/usr/share/virt-manager/virtManager/domain.py", line 924, in _XMLDesc return self._backend.XMLDesc(flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 400, in XMLDesc if ret is None: raise libvirtError ('virDomainGetXMLDesc() failed', dom=self) libvirtError: Interner Fehler: Client Socket ist geschlossen (german parts in there ...) and still the libvirtd[5742]: No response from client 0x7fa8060eef10 after 5 keepalive messages in 31 seconds on the server.