Bug 11252 - No green0phys network on VM
Summary: No green0phys network on VM
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: - Unknown - - Unknown -
Assignee: Jonatan Schlag
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-03 13:43 UTC by geh kah
Modified: 2017-05-28 15:48 UTC (History)
2 users (show)

See Also:


Attachments
libvirtd.log file (3.84 MB, text/plain)
2017-01-10 12:05 UTC, geh kah
Details
virtlogd.log (17.99 KB, text/plain)
2017-01-10 12:06 UTC, geh kah
Details

Note You need to log in before you can comment on or make changes to this bug.
Description geh kah 2016-11-03 13:43:47 UTC
I finally found out why my VMs on QEMU, hosted on a pcengines apu2b4, did not have any network connectivity (that means DHCP is not able to deliver an IPaddress to the VM)

The cause is pretty simple:

Whenever NO physical networkcable is connected to the GREEN nic on ipfire, the VMs won't have network.

Asap you connect a physical cable on the GREEN nic, the VM is available on network.

I checked it with several boards from pcengines. Problem exists always in the same way.

Please help to fix this issue.

BR

Geh Kah
Comment 1 Michael Tremer 2016-11-04 11:22:20 UTC
Well, what issue is there to fix? The MACVTAP bridge bridges virtual network interfaces with the phyisical network. Nothing more. Nothing less.
Comment 2 Jonatan Schlag 2016-11-21 16:40:32 UTC
Reopened, because of the fact that a lot of people complain about the design. 

This bug should be now used to implement a second network mode which has not the described limitation.

Regards Jonatan
Comment 3 Pablo78 2016-11-21 20:17:02 UTC
Hello,

i have a topic in ipfire forum where my virtual Machine loses connection if the physical Ethernet Inteface has not Link. On my Green LAN-Interface sporadically LAN-Devices online (PC...) but my VM has got a macvtap. 
In this constellation I can not use the VM

http://forum.ipfire.org/viewtopic.php?f=46&t=17700



Paul (Pablo78)
Comment 4 Jonatan Schlag 2016-12-31 16:46:52 UTC
Hi, 

I spend some time with Michael Tremer to fix this bug but I now found a solution.

1. Download and install the current version of the core update

for x86_64

http://nightly.ipfire.org/next/latest/x86_64/packages/core-upgrade-2.19-109.ipfire

or for i586

http://nightly.ipfire.org/next/latest/i586/packages/core-upgrade-2.19-109.ipfire

2. Change the mode for the zone to "bridge"

3. reboot.

4. In Virt-Manager reinstall your nics using: 

Name des gemeinsam verwendeten Gerätes angeben and then type in the name of the network zone in lowercase with an ending zero.

For example VM should be placed in the orange zone => orange0

5. Reboot the VMS that the changes take effect. (Maybe not necessary the nics can be hotplugged)

Everything should work.

This mode should also work with any physical devices that do not support MAC address changes. (Pablo78 that was your problem with orange?)

Report Problems here!!! Also, report when the solution works for you.

Regards Jonatan
Comment 5 geh kah 2017-01-04 07:25:10 UTC
Dear Jonathan

I just saw your solution yesterday late at night. I'm already on it to reinstall my APU for testing your advice. I wasnt able to find an instruction how to manually update the nightly core. May I have more luck today.

Thank you so much for all your efforts you did especially on new years eve, its much appreciated!!!

Ill post news asap I have them

Best Regards

Greg
Comment 6 Jonatan Schlag 2017-01-04 15:24:09 UTC
Hi Greg,

just install the core update manually with :


cd /opt/pakfire/tmp/
wget <the link goes here>
tar xvf core-upgrade-2.19-109.ipfire
./update.sh

and reboot and then do the changes described in my previous post. 

Regards Jonatan
Comment 7 geh kah 2017-01-04 20:56:25 UTC
Dear Jonathan

I did not get any ip address w/o the plugged in cable, after I reconfigured the NIC in virt-manager to "gemeinsam...." --> green0 

so I removed the NIC and added a new one. configured the nic the same way you adviced and now its dead :)

----------------
Fehler beim Starten der Domain: Unable to add bridge orange0 port vnet0: Operation not supported

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup
    self._backend.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 999, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to add bridge orange0 port vnet0: Operation not supported
-----------------

(i tried with orange0 as well)

BR Greg
Comment 8 Jonatan Schlag 2017-01-05 15:12:26 UTC
Dear Greg,

could your reboot your machine and post the output of 

ip link show

and 

brctl show

?

Could you also lock in the system log files if there are log messages regarding the network?

And please post your /var/ipfire/ethernet/settings file.

Thank you for testing

mfg Jonatan.

PS.: ORANGE_MODE=bridge is set in /var/ipfire/ethernet/settings. And please the macvtap mode is removed? ORANGE_MODE=bridge macvtap will not work!!
Comment 9 geh kah 2017-01-06 13:17:19 UTC
Dear Jonatan
ethernet.settings.file.output
-----------
CONFIG_TYPE=4
BLUE_DEV=blue0
BLUE_MACADDR=04:f0:21:1b:b1:d9
BLUE_DESCRIPTION='"pci: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)"'
BLUE_DRIVER=ath9k
RED_DEV=red0
RED_MACADDR=00:0d:b9:40:7e:c4
RED_DESCRIPTION='"pci: Intel Corporation I210 Gigabit Network Connection (rev 03)"'
RED_DRIVER=igb
ORANGE_DEV=orange0
ORANGE_MACADDR=00:0d:b9:40:7e:c5
ORANGE_DESCRIPTION='"pci: Intel Corporation I210 Gigabit Network Connection (rev 03)"'
ORANGE_DRIVER=igb
ORANGE_MODE=bridge
GREEN_DEV=green0
GREEN_MACADDR=00:0d:b9:40:7e:c6
GREEN_DESCRIPTION='"pci: Intel Corporation I210 Gigabit Network Connection (rev 03)"'
GREEN_DRIVER=igb
GREEN_MODE=bridge
--------------


ip link show
---------------
CONFIG_TYPE=4
BLUE_DEV=blue0
BLUE_MACADDR=04:f0:21:1b:b1:d9
BLUE_DESCRIPTION='"pci: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)"'
BLUE_DRIVER=ath9k
RED_DEV=red0
RED_MACADDR=00:0d:b9:40:7e:c4
RED_DESCRIPTION='"pci: Intel Corporation I210 Gigabit Network Connection (rev 03)"'
RED_DRIVER=igb
ORANGE_DEV=orange0
ORANGE_MACADDR=00:0d:b9:40:7e:c5
ORANGE_DESCRIPTION='"pci: Intel Corporation I210 Gigabit Network Connection (rev 03)"'
ORANGE_DRIVER=igb
ORANGE_MODE=bridge
GREEN_DEV=green0
GREEN_MACADDR=00:0d:b9:40:7e:c6
GREEN_DESCRIPTION='"pci: Intel Corporation I210 Gigabit Network Connection (rev 03)"'
GREEN_DRIVER=igb
GREEN_MODE=bridge
--------------------------

brctl show
------------
bridge name	bridge id		STP enabled	interfaces
green0		8000.000db9407ec6	no		greenphys0
							vnet0
orange0		8000.000db9407ec5	no		orangephys0
------------

or do you mean within the VM itself?

One more time I wanted to thank you for your services and the efforts. Very much appreciated Jonathan

Greg
Comment 10 geh kah 2017-01-06 13:25:25 UTC
sorry sorry

ip link show:
-------------
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: red0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:0d:b9:40:7e:c4 brd ff:ff:ff:ff:ff:ff
3: orangephys0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master orange0 state UP mode DEFAULT group default qlen 1000
    link/ether 00:0d:b9:40:7e:c5 brd ff:ff:ff:ff:ff:ff
4: greenphys0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master green0 state UP mode DEFAULT group default qlen 1000
    link/ether 00:0d:b9:40:7e:c6 brd ff:ff:ff:ff:ff:ff
5: green0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 00:0d:b9:40:7e:c6 brd ff:ff:ff:ff:ff:ff
6: blue0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 04:f0:21:1b:b1:d9 brd ff:ff:ff:ff:ff:ff
7: orange0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 00:0d:b9:40:7e:c5 brd ff:ff:ff:ff:ff:ff
9: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master green0 state UNKNOWN mode DEFAULT group default qlen 500
    link/ether fe:54:00:84:55:e6 brd ff:ff:ff:ff:ff:ff
----------------
Comment 11 Jonatan Schlag 2017-01-06 15:15:00 UTC
Dear Greg,

so far everything looks fine:

bridge name	bridge id		STP enabled	interfaces
green0		8000.000db9407ec6	no		greenphys0
							vnet0

A VM is attached to the green network and everything is working? (vnet0)

So could you also post

/var/log/messages

and set the #log_level = 3 in the /etc/libvirt/libvirtd.conf to 1
(log_level = 1) and remove the #.

The restart libvirt and try the start once again. And then post the content of /var/log/messages.

Regards Jonatan
Comment 12 geh kah 2017-01-10 12:05:29 UTC
Created attachment 490 [details]
libvirtd.log file

had to shrink it from 50mb to 4mb
Comment 13 geh kah 2017-01-10 12:06:10 UTC
[root@uefw003 ~]# grep "libvirt*" /var/log/messages
Jan 10 11:37:57 uefw003 sshd[10666]: Accepted password for libvirt-remote from 46.127.253.29 port 50982 ssh2
Jan 10 11:51:11 uefw003 sshd[4265]: Accepted password for libvirt-remote from 46.127.253.29 port 50984 ssh2
Jan 10 11:51:32 uefw003 sshd[4390]: Accepted password for libvirt-remote from 46.127.253.29 port 50985 ssh2
[root@uefw003 ~]#
Comment 14 geh kah 2017-01-10 12:06:42 UTC
Created attachment 491 [details]
virtlogd.log
Comment 15 Jonatan Schlag 2017-01-10 16:10:55 UTC
Dear Greg,

the logs are not so useful so I would like to have:

the libvirt log but with log level info and when the log is too big. Please post the 2000 lines around:

Unable to add bridge orange0 port vnet0: Operation not supported

This error or another must be in the log file when you try to start a VM.

Am I right when I Guess that it still not work?
Because in #9, the config looks fine?

Regards Jonatan
Comment 16 geh kah 2017-01-10 16:28:06 UTC
Dear Jonathan

I found out that my VM network configuration wasnt correct. I'm really sorry for the circumstances. I'm now on green_mode=bridge and a working network setup in my VM. the only problem now is: orange and green NICs on APU are still connected over a switch. I need to go home in a few hours and unplug them, to check the network configuration again.

Ill let you know this evening if its working or not

once again: Thank you so much for your efforts you did. 

best regards

greg
Comment 17 geh kah 2017-01-10 18:33:25 UTC
<3 Jonatan

Was all my fault. Your provided nightly was the solution.

I do not know how I can thank you more than giving this projects the donations than I can. Amazing work!!

Best Regards from Switzerland

Greg