March 16Mar 16 Hello,I struggle with networking particularly for vm.At a time macvlan and bridging were causing issues.So I disabled bridging. (Bonding is also disabled). I htink it was around unraid 6.8In this config all was good for my vm and my dockers.I have one active vm (several others are down but are ok if enable them)I wanted to create a new vm but I’m unable to have it obtaining an ip. If setting a static ip it doesn't work either.When I create a vm I’m offered the choice of vibr0 or eth0 ( I have also eth0.x as I have enabled vlans)None of these options are ok.So I looked at the xml config of working vm and for the network I have that:<interface type='direct' trustGuestRxFilters='yes'> <mac address='52:54:00:11:1d:57'/> <source dev='vhost0' mode='bridge'/> <target dev='macvtap0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface>All my vm have the same network controller definition. Only mac_address and target dev differ.Note that the source dev is vhost0 in xml but in gui it’s vibr0.What network source should i use for my new vm?What is the correct xml definition for the network interface.
March 16Mar 16 Enabling bridging fot et0 should resolve the issue, then chosse br0 for the VM, macvlan is no longer a problem since 6.12.11
March 16Mar 16 Author thanks. I'll do that but i need time to evaluate because i have so much containers and docker networks.I got it working before i saw your answer. When i tried with eth0 as network source and e1000 for network type it worked. It's strange; when i install the same vm in proxmox it's ok with virtio network.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.