Recent content by GuiltyNL

I can confirm this is still an issue on v7.3.3

You could make somekind of ID check and when they don't conflict, allow a node with vm's join a cluster. I forgot about it, moved vm's around with some down time and now i wanted to setup my cluster. Which is failing, because two of three of my servers thave vm's already. Now I have to do a...

nvm

I'm installing 6.2 on a Gigabyte Dual EPYC 7302 server. I have one Ubuntu test VM on it and it seems to work well. What issues are you afraid for @andy77 ?

I'm happy my post still helps people out. @Batpenguin :cool:

Good, I had the same issue and this solved it for me.

I want to accept that offer @Proxmox India

Good to hear. Happy that I was able to help!

If you assign an IP to vmbr0 or vmbr1 on your Proxmox host, then that IP will be given to your host and not to your VM. Don't assign IP's on a vmbr bridge in your host. Ensure that the physical NIC you created the bridge on, is connected with a UTP LAN cable to the WAN port of your modem...

Do you want to offer both NIC's to your VM's too? If no, just create one bridge for your VM's and attach the 192.168.2.10 IP to the other NIC directly (without creating a bridge). No? :D:eek::rolleyes:

I suspect a misconfiguration. It should work like @WhiteStarEOF says.

You can try this, however I don't know it this unofficial package still works, but it's worth a try: http://xmodulo.com/access-amazon-cloud-drive-command-line-linux.html

Your modem has a switch, right? Just use his internal IP as gateway address on your Proxmox node. And you can create a virtual bridged adapter on top of your NIC in Proxmox to pass to your VM's.

But it gives you more information if you run it from the command line instead of the gui, doesn't it?

But it is taking a loooooong time. ;)