[Bug 1119088] New: KVM guest start at boot failure
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088 Bug ID: 1119088 Summary: KVM guest start at boot failure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs@forge.provo.novell.com Reporter: philip.raets@telenet.be QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 792364 --> http://bugzilla.opensuse.org/attachment.cgi?id=792364&action=edit detailed boot log situation: I have a virtual machine in KVM with a windows install. The network is bridged with a bridge in NetworkManager. The machine is configured to autostart at boot. After the latest update of Samba the machine doesn't start at boot anymore. I can start it after logging in on the host. The host is my computer connected to a windows AD domain and I login with a domain user through winbind. I also have a samba share on the host. Why I suspect the samba update is because I had a previous bug with samba and winbind not starting at boot, because the network wasn't up, which prevented me from logging on to the computer. With testing of newer samba packages, the above events occured (virtual machine not starting at boot). Now there was an update of samba (to samba 4.9.3) and the virtual machine doesn't start at boot anymore. logs are attached. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c1
--- Comment #1 from Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c2
--- Comment #2 from Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c3
--- Comment #3 from Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c4
--- Comment #4 from Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c5
--- Comment #5 from Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c13
--- Comment #13 from Philip Raets
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c14
Jonathan Kang
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088
http://bugzilla.opensuse.org/show_bug.cgi?id=1119088#c15
--- Comment #15 from Jonathan Kang
Created attachment 792600 [details] bootlog snapshot 20181204
I've installed tumbleweed-cli so I could get back to previous snapshots. I went back to 20181204, because then it was still working.
I rebooted after installing, and the vm started at boot.
I then started upgrading to the next snapshot and rebooted to find out exactly when this started happening.
I've upgraded to all newer snapshots, but the vm keeps starting at boot now with NetworkManager. I don't know what happened.
Now I'm back at the latest snapshot (20181211).
Attached is the bootlog for 20181204
It could be some misconfiguration and it got fixed when you up/downgrade the system? That's odd. Anyway, glad that it works. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com