Your message dated Sat, 30 Oct 2010 18:56:26 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-libvirt-maintainers] Bug#601812: libvirt-bin: default 
network does not activate automatically
has caused the Debian Bug report #601812,
regarding libvirt-bin: default network does not activate automatically
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
601812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601812
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvirt-bin
Version: 0.8.4-1
Severity: important

Fresh installed virtual machine does not start due to this error.

When I try to start it i get this error:

Error starting domain: internal error Network 'default' is not active.
Details:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 808, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1296, in startup
    self._backend.create()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 333, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Network 'default' is not active.

If you add a new interface to the machine it saids:  
"virtual default network is not active, do you want to activate it now?"
(i've translated this so maybe is not exact)

After doing it you can delete de new interface and everithing works properly.
After discover this i realized that the only problem is that network does not 
start automátically and y discover in /etc/libvirt/qemu/networks/ that autostar 
folder is empty so i added a symbolic link to default.xml
ln -s /etc/libvirt/qemu/networks/default.xml 
/etc/libvirt/qemu/networks/autostart/default.xml

This solved the problem.  Now network interface starts automatically and the 
virtual machine boots without problem.
I guess that this is a bug and this symbolink link should be automatically 
added during the configuration of the package, but it's your call to decide it.

Thank you for your time
Iker

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (750, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libvirt-bin depends on:
ii  adduser                3.112             add and remove users and groups
ii  libavahi-client3       0.6.27-2          Avahi client library
ii  libavahi-common3       0.6.27-2          Avahi common library
ii  libblkid1              2.17.2-3.3        block device id library
ii  libc6                  2.11.2-6+squeeze1 Embedded GNU C Library: Shared lib
ii  libcap-ng0             0.6.4-1           An alternate posix capabilities li
ii  libdevmapper1.02.1     2:1.02.48-3       The Linux Kernel Device Mapper use
ii  libgcrypt11            1.4.5-2           LGPL Crypto library - runtime libr
ii  libgnutls26            2.8.6-1           the GNU TLS library - runtime libr
ii  libnl1                 1.1-5             library for dealing with netlink s
ii  libparted0debian1      2.3-2             The GNU Parted disk partitioning s
ii  libpciaccess0          0.12.0-1          Generic PCI access library for X
ii  libreadline6           6.1-3             GNU readline and history libraries
ii  libsasl2-2             2.1.23.dfsg1-6    Cyrus SASL - authentication abstra
ii  libudev0               163-2             libudev shared library
ii  libuuid1               2.17.2-3.3        Universally Unique ID library
ii  libvirt0               0.8.4-1           library for interfacing with diffe
ii  libxenstore3.0         4.0.1-1           Xenstore communications library fo
ii  libxml2                2.7.7.dfsg-4      GNOME XML library
ii  logrotate              3.7.8-6           Log rotation utility

Versions of packages libvirt-bin recommends:
ii  bridge-utils              1.4-5          Utilities for configuring the Linu
ii  dnsmasq-base              2.55-2         A small caching DNS proxy and DHCP
ii  gawk                      1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr
ii  iptables                  1.4.8-3        administration tools for packet fi
ii  libxml2-utils             2.7.7.dfsg-4   XML utilities
ii  netcat-openbsd            1.89-4         TCP/IP swiss army knife
ii  qemu                      0.12.5+dfsg-2  fast processor emulator
ii  qemu-kvm                  0.12.5+dfsg-4  Full virtualization on x86 hardwar

Versions of packages libvirt-bin suggests:
ii  policykit-1                   0.96-3     framework for managing administrat

-- no debconf information



--- End Message ---
--- Begin Message ---
On Sat, Oct 30, 2010 at 12:15:27AM +0200, Iker Salmón wrote:
> Package: libvirt-bin
> Version: 0.8.4-1
> Severity: important
> 
> Fresh installed virtual machine does not start due to this error.
This is done on purpose to not mess with any other nework setups. A

        virsh net-autostart default

activates the network. See README.Debian.
Cheers,
 -- Guido


--- End Message ---

Reply via email to