MacVTap seems not set up properly.

[mazzy89]

Description of problem

MacVTap seems not set up properly.

When I create a NET device of type MacVtap in this way:

	return qemu.NetDevice{
		Type:       qemu.MACVTAP,
		ID:         myobj.TAPIface.ID,
		Driver:     qemu.VirtioNetPCI,
		IFName:     myobj.TAPIface.Name,
		MACAddress: myobj.MacAddr,
		FDs:        []*os.File{myobj.TAPIface.VMFds},

		Script:     "no",
		DownScript: "no",
	}

I get the following output:

-netdev tap,id=macvtap4,fds=3 -device driver=virtio-net-pci,netdev=macvtap4,mac=ce:ca:44:23:96:5f,disable-modern=false,mq=on,vectors=4,romfile=

Expected result

Shouldn't I get also in the line the location of the tap device like 3<>/dev/tap5? in this way seems the macvtap does not work

Actual result

(replace this text with an explanation of what actually happened)

Further information

(replace this text with any extra information you think might be useful)

[devimc]

@mazzy89 - in this case fds=3 points to /dev/tap5, why are you expecting to see it in the cmdline?

[mazzy89]

yes. I saw all the examples on the web having the bash redirection 3<>/dev/tap5 so I thought it was somehow necessary. Unfortunately at the moment, macvtap does not work for me but it should not be then the case.

[mazzy89]

@devimc which Linux kernel module is required for Macvtap in the guest? is it virtio-net? do you know by chance?

[devimc]

@mazzy89 indeed, you need that module, take a look to the list of virtio and non-virtio modules that kata needs, maybe you are missing one https://github.com/kata-containers/kata-containers/tree/2.0-dev/tools/packaging/kernel/configs/fragments/common

[mazzy89]

Actually it work without without setting the redirection. All good here, closing and thanks for the support.