[opensuse] KVM fails to autostart guest
I have a kvm virtual machine hosted in Tumbleweed, with bridged network setup. I have set the guest to autostart when the host boots. Unfortunately, after reboot of the host, the virtual machine is not started. Looking at the log files, libvirt fails to start it, because the bridged network interface is not ready when it tries to start the guest: libvirtd[1403]: 2012-06-20 13:23:49.833+0000: 1485: error : qemuAutostartDomain:177 : Failed to autostart VM 'testguest': Cannot get interface MTU on 'br0': No such device I can see that the interface br0 is started after that. So, this is possible bug, and I'll report it so it can be fixed, but meanwhile, where should I change the startup order of the services, so libvirt is invoked after fully working network? I'm not familiar with the new (not init.d) startup process. -- Svetoslav Milenov (Sunny) Artificial Intelligence is no match for natural stupidity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I ended up modifying /lib/systemd/system/libvirtd.service: In the [Unit] section I added the line: After=network.target I guess upon update it may get overwritten, but until then ... it works. On Wed, Jun 20, 2012 at 8:39 AM, Sunny <sloncho@gmail.com> wrote:
I have a kvm virtual machine hosted in Tumbleweed, with bridged network setup. I have set the guest to autostart when the host boots.
Unfortunately, after reboot of the host, the virtual machine is not started.
Looking at the log files, libvirt fails to start it, because the bridged network interface is not ready when it tries to start the guest:
libvirtd[1403]: 2012-06-20 13:23:49.833+0000: 1485: error : qemuAutostartDomain:177 : Failed to autostart VM 'testguest': Cannot get interface MTU on 'br0': No such device
I can see that the interface br0 is started after that.
So, this is possible bug, and I'll report it so it can be fixed, but meanwhile, where should I change the startup order of the services, so libvirt is invoked after fully working network? I'm not familiar with the new (not init.d) startup process.
-- Svetoslav Milenov (Sunny)
Artificial Intelligence is no match for natural stupidity.
-- Svetoslav Milenov (Sunny) Artificial Intelligence is no match for natural stupidity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jul 09, 2012 at 08:12:59AM -0500, Sunny wrote:
I ended up modifying /lib/systemd/system/libvirtd.service:
In the [Unit] section I added the line: After=network.target
I guess upon update it may get overwritten, but until then ... it works.
To get this working on the long run you need to file a defect report and point to your solution. Else this will stay broken till others report it. As you have at least a work around solution it looks like others would benefit from your work. Please report the bug ID as a clickable URL back to this thread. Better would be you follow the instruction to the Open Build Service available from http://en.openSUSE.org/openSUSE:Build_Service_Collaboration and submit the required changes back via this way. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
I have published the bug and the workaround here: https://bugzilla.novell.com/show_bug.cgi?id=767932 Isn't this the supposed way? I'm not sure how the defect tracking works after Novell was sold. On Tue, Jul 10, 2012 at 3:03 AM, Lars Müller <lmuelle@suse.com> wrote:
On Mon, Jul 09, 2012 at 08:12:59AM -0500, Sunny wrote:
I ended up modifying /lib/systemd/system/libvirtd.service:
In the [Unit] section I added the line: After=network.target
I guess upon update it may get overwritten, but until then ... it works.
To get this working on the long run you need to file a defect report and point to your solution. Else this will stay broken till others report it.
As you have at least a work around solution it looks like others would benefit from your work.
Please report the bug ID as a clickable URL back to this thread.
Better would be you follow the instruction to the Open Build Service available from http://en.openSUSE.org/openSUSE:Build_Service_Collaboration and submit the required changes back via this way.
Cheers,
Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-- Svetoslav Milenov (Sunny) Artificial Intelligence is no match for natural stupidity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jul 10, 2012 at 08:46:52AM -0500, Sunny wrote:
I have published the bug and the workaround here: https://bugzilla.novell.com/show_bug.cgi?id=767932
Isn't this the supposed way? I'm not sure how the defect tracking works after Novell was sold.
That's still the correct mechanism for openSUSE. I've added a comment to ensure we'll see this change in openSUSE 12.2. If you like to see this fixed for 12.1 too please add your comment in bugzilla too. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (2)
-
Lars Müller -
Sunny