Search results

The attached disks in Win10 only show up when the vioscsi driver is loaded. viostor doesn't work. The tutorials may have to be updated if this is the updated way to install Win10 https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers and https://pve.proxmox.com/wiki/Windows_10_guest_best_practices...

This is an old thread but I'll revive it for posterity. TLDR I encountered the same problem on my production cluster. The workaround is: run DNS servers outside of the Proxmox cluster or on iSCSI (and lose snapshots) or on local-lvm (and have limited HA). This way, at least the DNS servers can...

My Proxmox cluster had been in operation for 4 months when I encountered this error. It happened when I was mass-migrating disks from iSCSI to NFS. Cluster Details Proxmox version: 5.3 Storage: FreeNAS 11.2 serving iSCSI and NFS Problem I was switching the backing store of several VMs from...

Sorry I forgot to mention. The "/bin/ping" in PVE 5.3 itself doesn't permit a regular user to run it. It worked after I ran "setcap"

I confirm that this still occurs in PVE 5.3. I ran the following to fix it. setcap cap_net_raw+p /bin/ping

Thanks! Bug filed at https://bugzilla.proxmox.com/show_bug.cgi?id=1810

Hi guys, I setup a 3-node experimental cluster with LVM on iSCSI (FreeNAS) as storage. Live migration fails when the CloudInit drive is attached but it works fine without the CloudInit drive. Is this normal? Live migration with the CloudInit drive attached gives this error...

I'm putting this here so that others don't make the same mistake. In PVE's GUI, the iSCSI plugin (Datacenter > Storage > Add > iSCSI) doesn't offer a parameter to configure the username/password for Mutual CHAP authentication. I added the credentials to /etc/iscsi/iscsid.conf and tested with...