Search results

No problems so far after switching from virtio to sata.

I think I have the same problem on an "ancient" Proxmox VE 3.4 server. The strange thing is that it started happening not long ago. Most likely after moving the VM between storages (from one ZFS pool to another). It may be that I changed the virtual storage adapter. It now is "sata" for the boot...

OK so that got me thinking - and I realized my basic mistake: I defined the firewall rules for the host (ending up in /etc/pve/firewall/cluster.fw). I didn't realize the VMs have their own firewall settings. OK so that is what I am looking for! Turns out I missed another gem in the manual...

So this is the configuration on the host: root@h128:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 ... 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000 link/ether...

Hi, I can secure my Proxmox 5.0 host with the new (for me) firewall feature just fine - great! What I am missing now is a way to also protect my VMs that are on a bridge (Hetzner additional subnet setup) with the host having one of the subnet IPs. AFAIK, packets coming in for a VM are filtered...

"Me too." I am trying to avoid the other dominant virtualization solutions and stick with Proxmox VE 3.4. Trying to install it on a Lenovo x3500 M5 (basically a x3550 in a tower case instead of rack-mounted) with the built-in ServerRAID M5210 and ZFS. In fact, the installer runs in UEFI mode...