This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 279211 - Cannot restart fullvirt guest -- virDomainCreateLinux() failed Network 'default' not active
Cannot restart fullvirt guest -- virDomainCreateLinux() failed Network 'defau...
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Daniel Veillard
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-05 15:42 EDT by Matěj Cepl
Modified: 2008-04-04 12:05 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 12:05:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
copy of python backtrace; also on (852 bytes, text/plain)
2007-09-05 15:42 EDT, Matěj Cepl
no flags Details

  None (edit)
Description Matěj Cepl 2007-09-05 15:42:28 EDT
Description of problem:
I used xen on my computer (F7) before, but now I would like to try kvm instead
(graphic support under kernel-xen sucks). When trying to restart fullvirt guest
(host is x86_64, guest i386) using virtual-manager, I get the error mentioned in
summary (full Python backtrace is attached).

Version-Release number of selected component (if applicable):

How reproducible:
100% (tried four times)

Steps to Reproduce:
1.start virtual-manager -c qemu:///system on new
3.walk through the wizards as if creating new fullvirt guest (with hardware
acceleration) for CentOS 5, using local iso image, and "default" network.
Actual results:
error happens

Expected results:
starting CentOS 5 guest in VNC

Additional info:
Comment 1 Matěj Cepl 2007-09-05 15:42:28 EDT
Created attachment 187931 [details]
copy of python backtrace; also on
Comment 2 Daniel Berrange 2008-04-04 12:05:39 EDT
If the network isn't running, it merely needs to be started using virt-manager
UI, or 'virsh net-start'

Note You need to log in before you can comment on or make changes to this bug.