Topics

Networking from UOS


Ross Burton
 

My SOS has the acrn bridge stuff running:

root@bob:~# ifconfig
acrn-br0 Link encap:Ethernet HWaddr 1E:49:6F:F4:3F:8D
inet addr:192.168.1.178 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1c49:6fff:fef4:3f8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:900 errors:0 dropped:0 overruns:0 frame:0
TX packets:172 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130183 (127.1 KiB) TX bytes:58055 (56.6 KiB)

acrn_tap0 Link encap:Ethernet HWaddr 7E:F5:65:D3:E2:94
inet addr:169.254.158.193 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::7cf5:65ff:fed3:e294/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:131958 (128.8 KiB)

But when I start Clear (27230) I have no networking. Should it just
work if I pass -s 4,virtio-net,acrn_tap0 to acrn-dm with a Clear
guest?

Ross


Geoffroy Van Cutsem
 

Hi Ross,

How did you set these up?

The network set-up when you install ACRN in Clear Linux is controlled by the 4 systemd files located here: https://github.com/projectacrn/acrn-hypervisor/tree/master/tools/acrnbridge. Are you using systemd in your SOS image, and if so, do you have these files installed?

The bridge should have both the Ethernet and TAP interfaces connected to it, is that the case for you (what does "brctl show" return)? On my ACRN set-up the acrn_tap0 interface does not have an IP address assigned to it, and my UOS does. I'm wondering in your case if the TAP interface was correctly attached to the bridge.

Thanks,
Geoffroy


On Mon, Feb 4, 2019 at 05:13 PM, Ross Burton wrote:
My SOS has the acrn bridge stuff running:

root@bob:~# ifconfig
acrn-br0 Link encap:Ethernet HWaddr 1E:49:6F:F4:3F:8D
inet addr:192.168.1.178 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1c49:6fff:fef4:3f8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:900 errors:0 dropped:0 overruns:0 frame:0
TX packets:172 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130183 (127.1 KiB) TX bytes:58055 (56.6 KiB)

acrn_tap0 Link encap:Ethernet HWaddr 7E:F5:65:D3:E2:94
inet addr:169.254.158.193 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::7cf5:65ff:fed3:e294/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:131958 (128.8 KiB)

But when I start Clear (27230) I have no networking. Should it just
work if I pass -s 4,virtio-net,acrn_tap0 to acrn-dm with a Clear
guest?

Ross


Ross Burton
 

Yes, I'm using the network files for networkd from acrnbridge. It all
appears to be doing the right thing on the host, but the Clear UOS
doesn't seem to find any networking devices.

On the host:

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master acrn-br0 qlen 1000
link/ether 54:b2:03:0f:4e:13 brd ff:ff:ff:ff:ff:ff
4: acrn_tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
pfifo_fast master acrn-br0 qlen 1000
link/ether ba:aa:e4:4d:06:2a brd ff:ff:ff:ff:ff:ff
5: acrn-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
link/ether 1e:49:6f:f4:3f:8d brd ff:ff:ff:ff:ff:ff

$ brctl show
bridge name bridge id STP enabled interfaces
acrn-br0 8000.1e496ff43f8d no acrn_tap0 eno1

Ross


Ross

On Mon, 4 Feb 2019 at 17:01, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:

Hi Ross,

How did you set these up?

The network set-up when you install ACRN in Clear Linux is controlled by the 4 systemd files located here: https://github.com/projectacrn/acrn-hypervisor/tree/master/tools/acrnbridge. Are you using systemd in your SOS image, and if so, do you have these files installed?

The bridge should have both the Ethernet and TAP interfaces connected to it, is that the case for you (what does "brctl show" return)? On my ACRN set-up the acrn_tap0 interface does not have an IP address assigned to it, and my UOS does. I'm wondering in your case if the TAP interface was correctly attached to the bridge.

Thanks,
Geoffroy

On Mon, Feb 4, 2019 at 05:13 PM, Ross Burton wrote:

My SOS has the acrn bridge stuff running:

root@bob:~# ifconfig
acrn-br0 Link encap:Ethernet HWaddr 1E:49:6F:F4:3F:8D
inet addr:192.168.1.178 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1c49:6fff:fef4:3f8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:900 errors:0 dropped:0 overruns:0 frame:0
TX packets:172 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130183 (127.1 KiB) TX bytes:58055 (56.6 KiB)

acrn_tap0 Link encap:Ethernet HWaddr 7E:F5:65:D3:E2:94
inet addr:169.254.158.193 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::7cf5:65ff:fed3:e294/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:131958 (128.8 KiB)

But when I start Clear (27230) I have no networking. Should it just
work if I pass -s 4,virtio-net,acrn_tap0 to acrn-dm with a Clear
guest?

Ross


Geoffroy Van Cutsem
 

I had missed that in your original email, but I think the correct parameter to be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the tap name).

Were you ever able to run this Clear Linux image as a UOS on ACRN previously?

Geoffroy


On Mon, Feb 4, 2019 at 06:47 PM, Ross Burton wrote:
Yes, I'm using the network files for networkd from acrnbridge. It all
appears to be doing the right thing on the host, but the Clear UOS
doesn't seem to find any networking devices.

On the host:

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master acrn-br0 qlen 1000
link/ether 54:b2:03:0f:4e:13 brd ff:ff:ff:ff:ff:ff
4: acrn_tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
pfifo_fast master acrn-br0 qlen 1000
link/ether ba:aa:e4:4d:06:2a brd ff:ff:ff:ff:ff:ff
5: acrn-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
link/ether 1e:49:6f:f4:3f:8d brd ff:ff:ff:ff:ff:ff

$ brctl show
bridge name bridge id STP enabled interfaces
acrn-br0 8000.1e496ff43f8d no acrn_tap0 eno1

Ross


Ross

On Mon, 4 Feb 2019 at 17:01, Geoffroy Van Cutsem
<geoffroy.vancutsem@...> wrote:

Hi Ross,

How did you set these up?

The network set-up when you install ACRN in Clear Linux is controlled by the 4 systemd files located here: https://github.com/projectacrn/acrn-hypervisor/tree/master/tools/acrnbridge. Are you using systemd in your SOS image, and if so, do you have these files installed?

The bridge should have both the Ethernet and TAP interfaces connected to it, is that the case for you (what does "brctl show" return)? On my ACRN set-up the acrn_tap0 interface does not have an IP address assigned to it, and my UOS does. I'm wondering in your case if the TAP interface was correctly attached to the bridge.

Thanks,
Geoffroy

On Mon, Feb 4, 2019 at 05:13 PM, Ross Burton wrote:

My SOS has the acrn bridge stuff running:

root@bob:~# ifconfig
acrn-br0 Link encap:Ethernet HWaddr 1E:49:6F:F4:3F:8D
inet addr:192.168.1.178 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1c49:6fff:fef4:3f8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:900 errors:0 dropped:0 overruns:0 frame:0
TX packets:172 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130183 (127.1 KiB) TX bytes:58055 (56.6 KiB)

acrn_tap0 Link encap:Ethernet HWaddr 7E:F5:65:D3:E2:94
inet addr:169.254.158.193 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::7cf5:65ff:fed3:e294/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:131958 (128.8 KiB)

But when I start Clear (27230) I have no networking. Should it just
work if I pass -s 4,virtio-net,acrn_tap0 to acrn-dm with a Clear
guest?

Ross


Geoffroy Van Cutsem
 

On Mon, Feb 4, 2019 at 09:59 PM, Geoffroy Van Cutsem wrote:
I had missed that in your original email, but I think the correct parameter to be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the tap name).
Confirmed, acrn-dm will automatically add "acrn_" to the tap name you give it - see https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel/hw/pci/virtio/virtio_net.c#L667


Ross Burton
 

On Mon, 4 Feb 2019 at 21:16, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:
I had missed that in your original email, but I think the correct parameter to be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the tap name).

Confirmed, acrn-dm will automatically add "acrn_" to the tap name you give it - see https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel/hw/pci/virtio/virtio_net.c#L667
That seems... unobvious.

Ross


Geoffroy Van Cutsem
 

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-
users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Monday, February 4, 2019 10:21 PM
To: acrn-users@lists.projectacrn.org
Subject: Re: [acrn-users] Networking from UOS

On Mon, 4 Feb 2019 at 21:16, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:
I had missed that in your original email, but I think the correct parameter to
be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the
tap name).

Confirmed, acrn-dm will automatically add "acrn_" to the tap name you
give it - see
https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel
/hw/pci/virtio/virtio_net.c#L667
That seems... unobvious.
No disagreement here. I don't actually recall if that was discussed and if there were any reason for doing it this way. Hopefully, someone from the engineering team can enlighten us.

Geoffroy


Ross Burton
 

On Mon, 4 Feb 2019 at 21:31, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:
Confirmed, acrn-dm will automatically add "acrn_" to the tap name you
give it - see
https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel
/hw/pci/virtio/virtio_net.c#L667
That seems... unobvious.
No disagreement here. I don't actually recall if that was discussed and if there were any reason for doing it this way. Hopefully, someone from the engineering team can enlighten us.
I'd advocate for principle of least surprise: if the user says the
virtio tap device is called tap24, look for a device called tap24...

Ross


Eddie Dong
 

This week is CNY holiday, and almost entire team are in holidays.. Thanks Ross & Geoff!

-----Original Message-----
From: acrn-users@lists.projectacrn.org
[mailto:acrn-users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Tuesday, February 5, 2019 5:34 AM
To: acrn-users@lists.projectacrn.org
Subject: Re: [acrn-users] Networking from UOS

On Mon, 4 Feb 2019 at 21:31, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:
Confirmed, acrn-dm will automatically add "acrn_" to the tap name
you give it - see
https://github.com/projectacrn/acrn-hypervisor/blob/master/devicem
odel
/hw/pci/virtio/virtio_net.c#L667
That seems... unobvious.
No disagreement here. I don't actually recall if that was discussed and if
there were any reason for doing it this way. Hopefully, someone from the
engineering team can enlighten us.

I'd advocate for principle of least surprise: if the user says the virtio tap
device is called tap24, look for a device called tap24...

Ross


Ross Burton
 

Fixed: a combination of using the right TAP name and ensuring the
guest had the right kernel modules: the Clear KVM image doesn't ship
the IOT kernel modules, and I missed the bit of the getting started
guide where they're copied into the image.

Ross

On Mon, 4 Feb 2019 at 21:16, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:

On Mon, Feb 4, 2019 at 09:59 PM, Geoffroy Van Cutsem wrote:

I had missed that in your original email, but I think the correct parameter to be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the tap name).

Confirmed, acrn-dm will automatically add "acrn_" to the tap name you give it - see https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel/hw/pci/virtio/virtio_net.c#L667


Geoffroy Van Cutsem
 

Great stuff - thanks for the update Ross!

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-
users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Tuesday, February 5, 2019 12:31 PM
To: acrn-users@lists.projectacrn.org
Subject: Re: [acrn-users] Networking from UOS

Fixed: a combination of using the right TAP name and ensuring the guest had
the right kernel modules: the Clear KVM image doesn't ship the IOT kernel
modules, and I missed the bit of the getting started guide where they're copied
into the image.

Ross

On Mon, 4 Feb 2019 at 21:16, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:

On Mon, Feb 4, 2019 at 09:59 PM, Geoffroy Van Cutsem wrote:

I had missed that in your original email, but I think the correct parameter to
be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_" part from the
tap name).

Confirmed, acrn-dm will automatically add "acrn_" to the tap name you
give it - see
https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel
/hw/pci/virtio/virtio_net.c#L667


Wang, Hongbo
 

Thanks!
Our ACRN team will follow up to check if any improvement needed.


Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@intel.com

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-users@lists.projectacrn.org]
On Behalf Of Geoffroy Van Cutsem
Sent: Tuesday, February 5, 2019 9:03 PM
To: acrn-users@lists.projectacrn.org
Subject: Re: [acrn-users] Networking from UOS

Great stuff - thanks for the update Ross!

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-
users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Tuesday, February 5, 2019 12:31 PM
To: acrn-users@lists.projectacrn.org
Subject: Re: [acrn-users] Networking from UOS

Fixed: a combination of using the right TAP name and ensuring the
guest had the right kernel modules: the Clear KVM image doesn't ship
the IOT kernel modules, and I missed the bit of the getting started
guide where they're copied into the image.

Ross

On Mon, 4 Feb 2019 at 21:16, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:

On Mon, Feb 4, 2019 at 09:59 PM, Geoffroy Van Cutsem wrote:

I had missed that in your original email, but I think the correct
parameter to
be given to acrn-dm is "-s 4,virtio-net,tap0" (so drop the "acrn_"
part from the tap name).

Confirmed, acrn-dm will automatically add "acrn_" to the tap name
you give it - see
https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemod
el
/hw/pci/virtio/virtio_net.c#L667