Search results

hi Fiona, i did some experiment and revert driver back to virtio-win-0.1.229.iso had resolved all troubles :O

Hi, i have problem with a VM (Windows 20019 with SQLServer) Proxmox 8.1.4 6.5.11-8-pve Windows 2019 datacenter with virtio 0.1.248 and all updates until 20240717 VM get unrensponsive while backup ( thaw and unthaw), so i decided to use Freeze/thaw guest filesystems on backup for consistency on...

add "localtime: 0" to vm conf and poweroff and restart VM

It seems that sometihing changed after i appplied suggested modificaiton. i just reboot all my vdi with Windows 2019 and all get ok (163 VM with Windows 2019, some with uptime since 17-7-2022)

Hi, i just shutdown (poweroff) and restart all my VM with Windows 2019 and suggested modification (localtime:0) how long before shutdown -r on all VM to see if workaround works ? ( 1 weeks ? ) VM start without spice audio agent (itsnt a problem for me but ...) audio: Could not init `spice'...

aghh

I'dont know, i did change manually editing /etc/pve/qemu-server/*conf its very quicker

i just apply modification to all my 160 VM (Windows 2019 datacenter) that have same behaviour, live migrate to and from to another cluster member (it took some hour), but we have to wait some day to have feedback cluster, 3 supermicro Intel(R) Xeon(R) Gold 6226R CPU @ 2.90GHz, kernel...

I upgraded a customer from 5.4.1 cluster two nodes and DRBD (stock opensource drbd not Linbit subscription) In September i did a test installation with 3 VM and proxmox 5.4 to 6.0) and all well done Now i upgraded production system (i had to wait ok from customer damn it ...) and with kernel...

Hi Aaron, after your answer i tried backup and confirm that also backup stopped to work :( now i have to shutdown and restart all VM

since upgrade to proxmox 6 i had some problem that randomly occurs on vm i cannot run console from web interface, this happen only on some vm and only on a server of my 3 node cluster servers are identical and with the same proxmox upgraded version i tried to analyze and the problem is that qmp...

Hi Tom, i did another test on another client that has server with Sata disk and 04:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05)a) i crated same VM (Centos7 last update, qemu agent, virtio-scsi and disk on local directory /var/lib/vz/images) running...

Hi Dmulk, we use NFS, but we couldnt use iscsi because with iSCSI i think that you cannot take snapshot, iSCSI in a cluster is used as block device with LVM

Hi Tom, we did another test on another customer cluster with two server (supermicro) storage NFS Qnap test with centos 7 last updated Different proxmox and kernel version pve-manager/4.4-24/08ba4d2d (running kernel: 4.4.134-1-pve) same behaviour !!! :O 172.17.1.1:/NFSSamba on...

yes, persist, i did all test with last proxmox release and last kernel suggested by Tom i'm waiting for suggestion or for another test by Tom until fix be found/done i stop to use snapshot with ram and limits others snapshot

i run previously test after that upgrade of course

Hi tom I did the upgrade that you suggested me wget wget http://download.proxmox.com/debian/pve/dists/stretch/pvetest/binary-amd64/pve-kernel-4.15.18-7-pve_4.15.18-27_amd64.deb dpkg -i pve-kernel-4.15.18-7-pve_4.15.18-27_amd64.deb now on running machine dpkg -l | grep kernel ii...

hi Tom, i did some test, the problem arise on snapshot with ram (previously i did a mistake check live vm with qemu-img) test on updated proxmox with kernel that you suggest storage Netapp 9.3, connected with double 10GBE ethernet connected via switch HP host 3 server dell 256gb ecc registered...

Hi Tom, i tried new kernel but things get worse now corrupt also with snapshot without ram i tried only one time tomorrow i'll do extensive check strange things: on many test ne test , i toke snapshot and qemu-img report ERROR .... do a chkdsk on windows 2012 windows 2012 report no problem...

Ok, i'll empty a server on cluster and try with a single VM