Thank you so much. I’m in the middle of moving my office to the basement so I’ll try later but that looks like it should work. I tried reading some of the results but so many just say it should work. This looks very promising.
2 Likes
Sounds like you already may have a solution for this but if still having issues you could also try Multipass.
Its a tool made by Canonical (The people behind Ubuntu) for quickly spinning up Ubuntu VMs really easily with one line commands and so on. Similar to LXD in that regard. Really easy to use.
1 Like
Ok thanks, I’ll try that as well. I started to make progress with the online installer mentioned before then I needed to move my office. Just getting online now. The only issue I had was with the above installer from @AnotherDev was that once it got to installing the network and getting updates it wouldn’t find any connection even though the vm was setup to use the bridge.
1 Like
That’s progress.
If you have iproute2 installed… Does ip addr show your host has an address on that bridge interface?
Does bridge link show you have both your physical interface and your tap interface from your VM added to the bridge?
(I don’t know how many network interfaces your server has or how they’re set up, but guessing since you mentioned a home environment that you only have a single nic, that is not connected to bridge as it should be, and that your host is using it directly. I’m also guessing there’s nothing on that bridge other than your one lonely VM and that’s why you’re having issues. Your physical interface should be connected to the bridge, your host should not use the physical interface directly, and should set up its own networking through the bridge interface)
I’ll add that now and check. I have a feeling your right about the interface. I have the one eth that’s on the server and I setup a static ip address to the bridge. I used the new netplan that’s on ubuntu and have the hardware enp4s0 set to not recieve an address and setup a bridge (br0) to get the address. The install of the kvm setup a virtual bridge as well (virbr0) but I told it to use the br0 as it’s source.
Ok so ip addr results are:
Blockquote
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
link/ether 70:85:c2:d8:ee:59 brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0a:4d:b5:a0:6c:8b brd ff:ff:ff:ff:ff:ff
inet 10.56.57.169/24 brd 10.56.57.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::84d:b5ff:fea0:6c8b/64 scope link
valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:96:34:df:7d brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:96ff:fe34:df7d/64 scope link
valid_lft forever preferred_lft forever
11: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 52:54:00:bc:9f:d6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
12: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:bc:9f:d6 brd ff:ff:ff:ff:ff:ff
15: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:d2:d0:0b brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fed2:d00b/64 scope link
valid_lft forever preferred_lft forever
17: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master virbr0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:1a:ed:a7 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe1a:eda7/64 scope link
valid_lft forever preferred_lft forever
Bridge Link shows:
2: enp4s0 state UP : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 19
12: virbr0-nic state DOWN : <BROADCAST,MULTICAST> mtu 1500 master virbr0 state disabled priority 32 cost 100
15: vnet0 state UNKNOWN : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
17: vnet1 state UNKNOWN : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master virbr0 state forwarding priority 32 cost 100
Ok so after much thinking and reading I’m sure I’m over thinking things lol. What I need to do is setup the server to act like an unmanaged router so my uplink would be the physical nic and every virtual nic I create should get either an ip from dhcp or a static one. So am I correct to assume I should use netplan to setup the a bridge using the hardware interface and then setup virtual nics to use the bridge as it’s source? I’m just trying to think logically at this point. I just wish it was easier for what I want to achieve lol
I haven’t heard about netplan before you mentioned it today, from glancing over the website it seems to just be a frontend to network manager.
I can see you have br0 set up to contain a physical interface, and you have an ip on br0.
I see vnet0 is part of br0 as well, assuming that’s a tap interface that goes to your VM, that one should be getting an address from 10.56.57.0/24 range, same as your host. … if that’s not happening, dhcp traffic that works over udp ports 67/68 is getting droppe. You’d need to inspect the network traffic using tcpdump to figure out where, and then look at iptables and other stuff to figure out why?
virbr0 contains: virbr0-nic and vnet1 and is disconnected from the world, unless you setup routing on your machine.
next steps would typically be to look at tcpdump of various interfaces, and look at iptables rules, maybe even add some narrow -j LOG rules that will cause the kernel to log a message when it finds a machine packet.
if, on the other hand you want to turn your host into a layer 3 router, that’s definitely another apprach you could take, but then your upstream router your host is connected to will need to have a routing table entry so that it knows to send packets for your virbr0 subnet to your host.
Just to update my progress. I went back and reinstalled everything from scratch and setup the server. I have my nic not set to any address but I have a br0 setup with the static ip for my server. Everything there works. I then used the combined script to install ubuntu desktop via the web using the network bridge virbr0 this successfully connected to the ubuntu mirrors and is currently installing. Hopefully I’ll be able to further assign an ip address to the vm and login with a remote desktop.
Ok so major progress. I ditched the online install with the --location tab and used the --cdrom tab. This coupled with editing qemu config file and allowing both vnc and spice to use 0.0.0.0 and setting user/group to root (might not be necessary) I was able to start the vm and I also switched from putty to mobaxterm as it has more advanced features. This combo resulted in a few of the common error outputs but a new window opened showing the spice vm graphics and is installing. Now to tweak the settings and get something usable. Thanks all for the help. I think I finally have it.