Search results

You can also create a VM with pfsense or opnsense. You can configure dhcp for every network or if you prefer a dhcp on a NET and a dhcp relay on the others NET.

Yes sorry is a Ubuntu kernel. If you need to backup all VM I think the best is the PBS solution.

The Proxmox (PVE) is a debian kernel; I do not think that the backup software you have mentioned, can backup all the PVE. But if you want to backup all the VM on the PVE, the right metod could be the PBS; you can also restore sigle file or directories (of the Vm's) fron the PBS backup.

Try to disable the firewall on the VM to make other tests. From your VM you can ping the pve and viceversa?

Hi, Have you checked in the hidden devices on device manager? Remove any other virtio network card reference and try to reinstall again, try to use the last version virtio-win-0.1.240.iso regards,

Hi, You can use BalenaEtcher, it's so easy, regards,

Hello, on what hardware is Proxmox installed? How many network interfaces do you have? EF

May be you already know that: If you plan to use the file system ZFS you have to not use the raid controller. Anyway Proxmox, normaly can detect the HDD on the controller raid, so is a HW/drivers problem. I do not know the Hrdware-raid you are using, is a zerochannel? May be is a compatibility...

with fdisk on sdb1 you have the same result?

Probably the boot partition work, but I think you lose the rest of yor disk. You can try with a live distibution and try to mount the file system on the HDD, but probably I don't know a solution for this. Sorry.

mabe you louse your partitions if you try fdisk /dev/sda then p ?

what is the result of fsck /dev/sad1?

What if you attach the HDD on the MB controller?

proxmox-kernel-6.2.16-12-pve available in the pve-enterprise repository

using Qemu 7.0

The issue was a setting in QEMU (kernel and firmware were not involved) that didn't reset a variable and would result in an overflow after almost a month of running. This problem only affected Windows, which would generate the spinning dot at reboot.

In theory there is no difference but in fact the DHCP is a systme server that can have problemes. So to try with a static address is only a metod to exclude DHCP problems. Please tell us exatly what is non working.

Yes, you can add nodes with no OSD but be carefull for NIC configuration to avoid bottlenek. My tip is to configure NIC for node with no OSDs using the same NIC configuration of the other nodes with OSD

the configuration seem to be correct, but I am not sure for the configuration in dhcp, can you try with iface vmbr0 inet static? then address 192.168.x.y/24 (or similar)? vlan are tagged or untagged?

try to configure also the DMARC