internal error Network 'default' is not active

Bug #981728 reported by Sasa Paporovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apport
New
Undecided
Unassigned
libvirt (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I am on Ubuntu12.04 64bit updated to 14.4.2012

A parallel installation of virtualbox 4.1.12 makes the internal network for qemu-kvm accessed with virt-manager unusable.

A have to remark that there is no start of virtualbox from my side. It is just installed and blocks qemu-kvm from working completly.

Additional:

On openSUSE platform they could coexist in this just installed way. Sure both are not able to run in parallel, but parallel install is o.K

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu13
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 14 18:29:13 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac (20120328)
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596
ProcEnviron:
 PATH=(custom, no username)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=00ec9d51-a52f-4879-b208-5bf9136b7e49 ro quiet splash vt.handoff=7
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 760GM -E51 (MS-7596)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd09/03/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7596:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn760GM-E51(MS-7596):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7596
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

I got on guest(saved state) starting attemped:

Fehler beim Wiederherstellen der Domäne: internal error Network 'default' is not active.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1120, in startup
    self._backend.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 551, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Network 'default' is not active.

The same with normal start of all guests.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Also after a complete removing of virtualbox it keeps like descibed obove with the same stacktrace

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

You may want to notify a other network issue virtualbox causes:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981723

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

May be that a give virtualbox to much wigth on this.

On creating a new guest I got on activating default network:

Virtuelles Netzwerk 'default' konnte nicht gestartet werden: internal error Child process (/usr/sbin/dnsmasq -u libvirt-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2

I have messed arround with orchestra and misconfigured the dhcp configuration during this.

This seems to affect also qemu-kvm.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

The full stacktrace:

Virtuelles Netzwerk 'default' konnte nicht gestartet werden: internal error Child process (/usr/sbin/dnsmasq -u libvirt-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/uihelpers.py", line 650, in validate_network
    virnet.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1652, in create
    if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirtError: internal error Child process (/usr/sbin/dnsmasq -u libvirt-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

I have "testdrive" given a run.

As far as I remember it uses kvm.

It works.

This intends that this report is like

https://bugs.launchpad.net/ubuntu/+source/orchestra/+bug/911873

says a virt-manager/libvirt problem with orchestra

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Refiling from qemu-kvm to virt-manager, because of comment #9

affects: qemu-kvm (Ubuntu) → virt-manager (Ubuntu)
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for reporting this bug.

Is libvirt actually running? what does 'sudo status libvirt-bin' show?

Can you show the result of:

dpkg -l | grep dnsmas
ps -ef | grep dnsmas
virsh net-list
virsh net-start default

And do 'apport-collect 981728' to cause libvirt debug information to be posted to this bug?

My guess is that another dnsmasq is running and keeping libvirt from starting its dnsmasq, as per bugs 231060 and 928524.

affects: virt-manager (Ubuntu) → libvirt (Ubuntu)
Changed in libvirt (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Q:Is libvirt actually running? what does 'sudo status libvirt-bin' show?

A:libvirt-bin start/running, process 1446

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Q:

Can you show the result of:

dpkg -l | grep dnsmas
ps -ef | grep dnsmas
virsh net-list
virsh net-start default

A:

user@userhost:~$ sudo status libvirt-bin
[sudo] password for user:
libvirt-bin start/running, process 1446
user@userhost:~$ dpkg -l | grep dnsmas
ii dnsmasq 2.59-4 Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-base 2.59-4 Small caching DNS proxy and DHCP/TFTP server
user@userhost:~$ ps -ef | grep dnsmas
dnsmasq 1262 1 0 10:54 ? 00:00:01 /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /var/run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new
user 22549 22406 0 18:30 pts/5 00:00:00 grep --color=auto dnsmas
user@userhost:~$ virsh net-list
Name Status Automatischer Start
-----------------------------------------

user@userhost:~$ virsh net-start default
Fehler: Abruf des Netzwerks 'default' scheiterte
Fehler: Network not found: no network with matching name 'default'

user@userhost:~$

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Doing apport-collect 981728 cuases a problem:

.
.
.
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...
Package libvirt not installed and no hook available, ignoring
user@userhost:~$

-----------------------------

libvirt-bin is installed. Semms to be a problem with apport?!

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

A reassign this to "libvirt-bin" fails. Launchpad switched back to the source package "libvirt", so I could not do apport-collect 981728.

Changed in libvirt (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 981728] Re: internal error Network 'default' is not active

> user@userhost:~$ virsh net-list
> Name Status Automatischer Start
> -----------------------------------------
>

What about 'virsh net-list --all'?

> user@userhost:~$ virsh net-start default
> Fehler: Abruf des Netzwerks 'default' scheiterte
> Fehler: Network not found: no network with matching name 'default'

Ok, the VMs which you were trying to start were assigned to
network 'default', but it looks like 'default' is not defined.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Q:

What about 'virsh net-list --all'?

A:

user@userhost:~$ virsh net-list --all
Name Status Automatischer Start
-----------------------------------------

user@userhost:~$ sudo virsh net-list --all
[sudo] password for user:
Name Status Automatischer Start
-----------------------------------------
default Inaktiv yes

user@userhost:~$

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

"Automatischer Start" means "automatic starting"

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

<quote>

Ok, the VMs which you were trying to start were assigned to
network 'default', but it looks like 'default' is not defined.

</quote>

Well, it is defined with comment #17.

Before installing orchestra(original I guess virtualbox) it works fine with default.

--------------------------

To mark it out: All guests are affected. Not only one.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

But sure there are all on "default" network.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Ok, then I still think this is a dup of bug 928524. Can you please

sudo stop libvirt-bin
sudo mv /var/log/libvirt/libvirtd.log /var/log/libvirt/libvirtd.log.1
sudo start libvirt-bin
net-start default

and then attach /var/log/libvirt/libvirtd.log to this bug?

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Little problem with net-start:

user@userhost:~$ sudo stop libvirt-bin
[sudo] password for user:
libvirt-bin stop/waiting
user@userhost:~$ sudo mv /var/log/libvirt/libvirtd.log /var/log/libvirt/libvirtd.log.1
user@userhost:~$ sudo start libvirt-bin
libvirt-bin start/running, process 18788
user@userhost:~$ net-start default
net-start: command not found
user@userhost:~$ sudo net-start-default
sudo: net-start-default: command not found
user@userhost:~$

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Sorry, I meant

sudo virsh net-start default

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

user@userhost:~$ sudo stop libvirt-bin
[sudo] password for user:
libvirt-bin stop/waiting
user@userhost:~$ sudo mv /var/log/libvirt/libvirtd.log /var/log/libvirt/libvirtd.log.1
user@userhost:~$ sudo start libvirt-bin
libvirt-bin start/running, process 18788
user@userhost:~$ net-start default
net-start: command not found
user@userhost:~$ sudo net-start-default
sudo: net-start-default: command not found
user@userhost:~$ sudo virsh net-start default
Fehler: Netzwerk default konnte nicht gestartet werden
Fehler: internal error Child process (/usr/sbin/dnsmasq -u libvirt-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2

user@userhost:~$

-----------------------------------

Fehler: Netzwerk default konnte nicht gestartet werden

-> Error:Network default could not be started.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

From libvirtd.log:

virCommandWait:2192 : internal error Child process (/usr/sbin/dnsmasq -u libvirt-dnsmasq

Please uninstall dnsmasq if possible. Marking this as a duplicate of bug 928524

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.