Recent content by BORNXenon

At what point are you getting the error? I always set up my windows with only a single cd drive and I've never had an issue, is it possibly because the Windows ISO is in the second cd drive and not the first? Here is the config from one of my Windows 2019 vms. agent: 1 boot...

UPDATE: A month on now since the changes and still no freezes, looking good! :)

UPDATE: 2 weeks on and no more freezes. I'm hesitant to say it, but looks like the issue may be solved. Of the 3 things I did (AV update, Windows update, Async IO), I'm pretty sure that it was changing the Async IO to native that fixed it. The reason I say this is that I installed another...

No freeze at 10am today. This may just be because I rebooted the VM, or it may be that one of the things I did yesterday has solved the issue, I will wait and see! So, what I did: Updated the Trend AntiVirus Security Server software that runs on this VM to the latest patch. Installed all the...

Thanks, I've been keeping my eye on that thread and seen the various issues some people have experienced, as this cluster is in production, I'd rather not use it as a testbed! I'm still not convinced that the issue isn't with the VM itself. This particular VM has been running without issue...

Todays syslog... Feb 15 09:17:52 mrpve2 ceph-osd[3161]: 2022-02-15T09:17:52.799+0000 7fa37ba17700 -1 osd.6 pg_epoch: 11989 pg[3.ed( v 11989'4124822 (11971'4121884,11989'4124822] local-lis/les=11859/11860 n=446 ec=827/54 lis/c=11859/11859 les/c/f=11860/11860/0 sis=11859) [6,3,12] r=0 lpr=11859...

First thing I would do is remove the WinTV card and see if it boots up. On my home server I use a HDHomeRun, it's a network attached TV tuner so I don't have the pass-through problem, my Plex VM just picks it up from the network. Might be a better option for you when you get your server back up.

Ah, OP didn't explicitly state he had a cluster and I didn't pick up on it (that will teach me to skim read!). That being said, I have my clusters configured using the aforementioned VM options, my DC's are 1 and 2 in the start order and I've never had an issue. Of course I don't routinely shut...

In the VM 'Options' you can set 'Start at boot' and also the 'Start/Shutdown order'. This should do what you need.

PVE version details: root@mrpve2:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-10 pve-kernel-5.13: 7.1-7 pve-kernel-5.11: 7.0-10 pve-kernel-5.4: 6.4-5 pve-kernel-5.13.19-4-pve: 5.13.19-9...

Unfortunately the issue is not solved. 10am today and the VM has frozen, although it doesn't appear to have been for as long as previous. VM 102 qmp command failed - VM 102 qmp command 'guest-network-get-interfaces' failed - got timeout VM 102 qmp command failed - VM 102 qmp command 'guest-ping'...

2 days on and no further freezes. I'll keep an eye on it all next week and if the issue is solved and there are no further issues, I'll update my other cluster!

Cluster upgraded with no issue, I'll keep a close eye on the VM and report back. Incidentally, is it worth changing the Async I/O? I've seen it recommended in several threads but I don't like changing things when I don't know what it will do!

Upgrading now, will report back! :)

I do have backup jobs set for this server, but they don't run until 7pm. The freezing has occurred today at 10am, 11am, 12pm but interestingly not at 1pm. VM Config: qm config 102 agent: 1 boot: order=scsi0;ide2;net0 cores: 4 ide2: none,media=cdrom machine: pc-i440fx-6.0 memory: 8192 name...