Hello, Am Mittwoch, 11. Dezember 2013, 11:15:11 schrieb Jim Fehlig: > Günther J. Niederwimmer wrote: > > Am Mittwoch, 11. Dezember 2013, 09:57:21 schrieb Jim Fehlig: > >> Günther J. Niederwimmer wrote: > >>> Am Mittwoch, 11. Dezember 2013, 08:41:10 schrieb Jim Fehlig: > >>>>>>> after the update from 9-10. 12.13 I have lost all my Client in KVM. > >>>>>> > >>>>>> Update of what from where? > >>>>> > >>>>> only from the Update channel, 13.1 > >>>>> > >>>>> I mean udev and systemd Update and... > >> > >> I just applied the latest updates (which included udev, systemd, etc.) > >> to one of my 13.1 test machines, rebooted, and see that all of my VMs > >> are still there. > > > > I have this packets. > > > > bbs:~ # rpm -qa | grep libvirt > > libvirt-python-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-network-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-interface-1.1.2-2.5.1.x86_64 > > libvirt-client-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-nwfilter-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-nodedev-1.1.2-2.5.1.x86_64 > > libvirt-daemon-qemu-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-storage-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-secret-1.1.2-2.5.1.x86_64 > > libvirt-daemon-driver-qemu-1.1.2-2.5.1.x86_64 > > libvirt-daemon-1.1.2-2.5.1.x86_64 > > Looks sane. I suppose we should continue with this in bugzilla. When > starting libvirtd, any output to syslog/journalctl would be helpful.
I found the mistake ;) after the reboot the *.xml files are broken ?. I one line I have a missing "/" at the end of the line a "virsh define xxxx.xml" tell me the problem in the XML file, I repair the Files and I can define again the KVM client, afterward I make a 'virsh edit xxxx' with no error. I can start again my KVM Cients ;). Why the xml files are broken I can't say :(. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
