On 07.05.2015 13:21, R0b0t1 wrote:
> Unfortunately I don't think this produces VM interfaces that are
> visible outside of the subnet. I made some live changes a while ago
> (and need to figure out what they were - probably routing stuff). In
> any case, you should be able to create the tap device
# ip link
3: enp2s0:
5: tap0:
6: tap1:
7: br0:
Assign what was the host machine's IP to br0. The guests on tap0 and
tap1 should have IP addresses different from this, configured within
the guest.
# ip route
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.2
Now, the config tha
On 06.05.2015 23:14, Poison BL. wrote:
> If you need the VMs outwardly visible, I can't think of a way to do it
> without losing connection upon switching to the bridge (granted, I'm far
> from an expert on bridging under linux). If you're fine with the VMs being
> behind a NAT, and your kernel ha
On Wed, May 6, 2015 at 3:59 PM, Stefan G. Weichinger wrote:
>
> My task is to enable a (remote) server to run VMs via qemu/KVM.
>
> The server is configured to set up its eth0 via openrc but this isn't
> enough to run the VMs network.
>
> I tried macvtap but something didn't work, either libvirt
4 matches
Mail list logo
