Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When starting a virtual machine, the following error message is displayed: Error starting domain: internal error Network 'default' is not active. Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Network 'default' is not active. Version-Release number of selected component (if applicable): virt-manager-0.8.5-1.fc13.noarch libvirt-0.8.2-1.fc13.x86_64 How reproducible: Every time (on my machine) Steps to Reproduce: 1. Open virt-manager 2. select an existing virtual-machine 3. start that virtual machine Actual results: Error message Expected results: Virtual machine starts Additional info: I can work around this problem by creating a new virtual machine. One of the last steps in the virtual machine creation tells me that the Virtual Network 'default': NAT is inactive and offers to start it. After that, I can run any virtual machine just fine.
A workaround is to: # virsh net-start default # virsh net-autostart default But I am sure virt-manager could do the first for me instead of giving me a stack trace.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The default network should already be set to autostart when libvirt is installed. That said virt-manager could warn the user in this case that a network isn't started, similar to how we do with the new VM wizard. Moving to upstream tracker
*** Bug 901823 has been marked as a duplicate of this bug. ***
Nowadays we do offer to start a network when creating a new VM, but not when starting the VM. Libvirt will throw a clear error in this case that the resource is inactive. This should be a rare enough case that it doesn't warrant the code in virt-manager to offer to start the network/storage resource IMO, so closing as WONTFIX