https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
c
Can you attempt to ssh from the new VM to an existing VM on the same subnet? Maybe something is blocking ping/icmp traffic
g
from the VM I can’t reach anything on the same subnet, and no firewall on VM - so weird.
and can see mac-address on my switches
for VM
c
If you spin up 2 Linux vms on harvester, can you ssh into both of them? Can they ping each other?
g
let me try that w8
yes those VMs can ping each other
VM networks are just VLAN tagged
whut now it works
I don’t get it
let me kill other VM
will spin one more up to see if that works
new VM also works, first VM (where it did’nt work) have this “VirtualMachine generation is 2, but latest observed generation is 1”
two new ones don’t
maybe related - will kill all VMs and try again
ok. the first VM only works when second VM has been added - using same template - this is SO weird
both VMs are running on same node
let me try another switch I guess
ok was related to VM networks, default cluster network is untagged vlan 100 and swith port config is: vlan trunk native 100 vlan trunk allowed all I then created a VM network with tagged 100 but for some weird reason it started working when > 1 VM was created. I now changed to untagged and it works as expected
c
Nice weird. I've seen the networking take a min when creating vms on harvester but if your able to ssh into the node, I'd think the networking is setup
g
yes that worked fine with ssh, but nothing back on same subnet - until VM #2 was added, really weird. But thanks for chipping in
I look forward to try more Harvester 🙂
c
Nice no problem I'm a big fan of harvester so far in my homelab. Pretty quick and easy to setup and using rancher it's cool to setup clusters with it. Good luck with everything!
g
Thank you 🙂
w
Re "VirtualMachine generation is 2" see https://github.com/harvester/harvester/issues/6844
🙌 1
5 Views
Open in Slack
PreviousNext
Powered by