I'm trying to test the network hotplug functionality with ka

When running with CLH as the VMM, the error log looks like this: <div class="snipp

Looks like CLH doesn't support hotplugging of network devices: <div class="Box Box

yep, perfect, just as I was hoping. thanks again <a class="user-mention notranslate" d

Network hotplug issues with firecracker about runtime HOT 7 CLOSED

networkop commented on July 20, 2024

Network hotplug issues with firecracker

from runtime.

Comments (7)

networkop commented on July 20, 2024

When running with CLH as the VMM, the error log looks like this:

May 03 11:00:48 xps kata-runtime[307307]: time="2021-05-03T11:00:48.402362277+01:00" level=error msg="add interface failed" arch=amd64 command=kata-network container=dc15d5bb0e3a3d9274227d329e818d2039a3f4c4f07d26a8c0d4b294e595ea72 error="cannot hotplug device: unsupported device type '2'" name=kata-runtime pid=307307 resulting-interface="<nil>" sandbox=dc15d5bb0e3a3d9274227d329e818d2039a3f4c4f07d26a8c0d4b294e595ea72 source=runtime
May 03 11:00:48 xps kata-runtime[307307]: time="2021-05-03T11:00:48.402420499+01:00" level=error msg="cannot hotplug device: unsupported device type '2'" arch=amd64 command=kata-network container=dc15d5bb0e3a3d9274227d329e818d2039a3f4c4f07d26a8c0d4b294e595ea72 name=kata-runtime pid=307307 sandbox=dc15d5bb0e3a3d9274227d329e818d2039a3f4c4f07d26a8c0d4b294e595ea72 source=runtime
May 03 11:00:48 xps kata-netmon[306894]: time="2021-05-03T11:00:48.404259786+01:00" level=fatal msg="handleEvents()" error="exit status 1" name=kata-netmon pid=306894 sandbox=dc15d5bb0e3a3d9274227d329e818d2039a3f4c4f07d26a8c0d4b294e595ea72 source=netmon

from runtime.

networkop commented on July 20, 2024

Looks like CLH doesn't support hotplugging of network devices:

runtime/virtcontainers/clh.go

Line 471 in 59e2273

 return nil, fmt.Errorf("cannot hotplug device: unsupported device type '%v'", devType) 

from runtime.

networkop commented on July 20, 2024

Ha, looks like FC doesn't support it either

runtime/virtcontainers/fc.go

Line 1042 in 59e2273

 return nil, fmt.Errorf("Could not hot add device: unsupported device: %v, type: %v", 

from runtime.

networkop commented on July 20, 2024

So, I guess this is by design, so feel free to close this issue.
I'm just curious if it's possible to avoid hotplugging and connect multiple network interfaces before FC VM starts.. Is this possible?

from runtime.

egernst commented on July 20, 2024

It’s been a while… but I believe you can create a runc container, add a second interface to it, and then create a kata container that uses the net of the first runc container. This’ll result in a kata container running with two interfaces at boot, rather than relying in hotplug.

from runtime.

egernst commented on July 20, 2024

See https://gist.github.com/egernst/0c8acf60d5aa4b6ab9d36517580c760a#launching-clear-container-with-two-vhost-user-interfaces

from runtime.

networkop commented on July 20, 2024

yep, perfect, just as I was hoping. thanks again @egernst 👍

from runtime.

Recommend Projects