Search results

You can edit the topic and put the solved tag (big orange button) left of the topic's description.

I'm out of ideas then. You can check if the cdrom is the first device in the boot order, but if it is, that's how it always works.

Yes. Please refer to the documentation before you go on. https://pve.proxmox.com/wiki/PCI(e)_Passthrough

It's possible. Best practice is to check the checksum after downloading, which is usually provided next to the iso. Maybe do this first or give it another shot with a download.

Is the iso bootable? This usually works out of the box.

Did you start it? Maybe start with a fresh VM if you already configured stuff.

The second one isn't of any help. The controller probably is named differently, so you have to search thoroughly, without any greps.

On the command line enter lspci and look for your nvme card. That is the PCI device that you give to the machine in the hardware tab.

You create a new VM and will automatically be asked which iso to use.

You can maybe give one of the remaining nodes two votes, so that quorum is restored. I'm not sure though if that is possible in a non-quorate cluster. Or you setup a qdevice for the cluster and a ceph arbiter device. However, I'm also not sure if this works while being non-quorate.

Delete the gateway line in vmbr1.10 Is vlan 10 coming in tagged on that 10GbE nic?

Then why did you enter 192.168.100.2 in the interfaces file? It has to be the address that IT gave you. As mentioned, eno1 doesn't get an address itself in that scenario, only vmbr0.

It's not possible to set vmbr0 to DHCP and receive an address in an inappropriate subnet. There is either a misconfiguration in your DHCP server or your router (which is most of the time the same device) and most probably your proxmox host. Please do yourself a favor and read about basic ip...

Read about the zfs special devices, those help a lot with this use case.

A cluster over WAN is a bad idea in general.

You have to reboot the machine in order for the changes to take effect.

Well, this obviously can't work. Eno1 is the underlying network port for vmbr0, but it's address is in a different subnet than vmbr0. So I assume your router is routing 192.168.3.0/24 and not 192.168.100.0/24. I suggest to switch to dhcp on vmbr0 for once just to see what address it gets...

Well, do you experience problems? Right now it looks like everything should work.

How do you measure performance?

Looks fine on Proxmox side. Are there routing problems?