ilarion

I have similar problem mine get started and canceled 4 times. and the parity check history shows only two of them. For 4 days my disk was spinning for 19 hrs, i didn't canceled. And the logs doesn't tell anything. x99-diagnostics-20230728-2136.zip PS: So today was the same thing happened.. so after more checking i found where the problem was. Who in the right mind will use "Every day" literally in the context of other settings and the specific task. Here "Every Day" should mean "Any day" - of the "Last week". And interestingly this is the only options that doesn't have an explanation.

Try seabios and ovmf, try different type of disk controller emulation (normaly sata works for vbox but....) you can try ide,virtio, scsi...use latest q35... PS: from this blog if you open there xml you can see that they use ide controller for the disk emulation.

Today plugin finish with error for one of my VMs. The error is: 2022-09-05 06:05:06 information: able to perform snapshot for disk /mnt/user/domains/win10/C_windows.qcow2 on win10. use_snapshots is 1. vm_state is running. vdisk_type is qcow2 2022-09-05 06:05:06 information: qemu agent found. enabling quiesce on snapshot. error: operation failed: failed to format image: 'Could not resize image: Failed to grow the L1 table: Invalid argument' 2022-09-05 06:05:08 failure: snapshot command failed on C_windows.snap for win10. 2022-09-05 06:05:08 warning: snapshot_fallback is 1. attempting backup for win10 using fallback method. 2022-09-05 06:05:08 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2022-09-05 06:05:08 infomration: win10 is running. vm desired state is shut off. Domain 'win10' is being shutdown Google doesn't want to talk to me this time... Can someone cast some light on this for me ? It was the path to the vdisk from the xml, strangly it was working with mnt/user till now, cat figure it out what change. I have 2 other VMs that still work with /mnt/user and not /mnt/disk/.

Try to disconnect all other usb devices. It is pretty common to have a bad usb device that brings down hole usb bus or a mose that have a short in the cable that only shorts in some of the movements. Also a lot of cheepo wireless keyboard mouse receivers hang after some time and mess the usb buss.

Because you didn't have loaded windows. Windows doesn't boot without gpu.... The thing is that most of this videos are not relevant anymore. A lot of things change. The thing you have to do for the gpu to not been used by unraid and to be bind to vfio driver is. Unraid GUI>TOOLS>System Devices>mark the check box of the device>click on bind to vfio>reboot.

So before all that did you try to bind gpu to vfio from system devices menu ? Because 'video=efifb:off' was a thing that was necessary like 3-4 years ago. And for the black screen if you use qlx adapter and your gpu as the second adapter on installation. You will be able to finish driver installation trough VNC screen. And i am pretty sure that if you use csm it will work too. Using uefi with some of the popular hba cards that everyone sims to use with unraid now will result in hangup on host boot. I thing the key to your success was upgrading to 6.10 because when i upgrade to 6.10 most of the tinkering things i have to do in the past to get working gpu pastrought was not necessary anymore.

Did you try this ?

So from what i remember in the past this was working ok. But i didn't use for some time. So now i want to hibernate my windows VM again but on resume i get this 4 errors in "Event Viewer" Windows failed to resume from hibernate with error status 0xC000007B. ********************************************************************* The previous system shutdown at 6:39:07 PM on ‎9/‎2/‎2022 was unexpected. ************************************************************************* Dump file creation failed due to error during dump creation. ************************************************************ The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. I have two Windows 10 VMs with usb pastrought and gpu pastrought. This was working in the past but for some reason now is not. The only thing except multiple unraid and Q35 updates that is changed by me from the past is that i move from "raw/img/virtio" to "qcow2/img/scsi" : <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains/win10/C_windows.qcow2' index='3'/> <backingStore/> <target dev='hdc' bus='scsi' rotation_rate='1'/> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> This is the output from pwrcfg: PS C:\Windows\system32> powercfg /A The following sleep states are available on this system: Standby (S3) Hibernate Hybrid Sleep The following sleep states are not available on this system: Standby (S1) The system firmware does not support this standby state. Standby (S2) The system firmware does not support this standby state. Standby (S0 Low Power Idle) The system firmware does not support this standby state. Fast Startup This action is disabled in the current system policy. So does someone have any suggestions? PS: xml from one of my VMs

It is some kind of bug. It is happening every time when updating docker container from community apps menu and not from docker menu.... If you force update it after from docker menu it becomes OK again.

ppl go - people normally do. Do you have some kind of motion interpolation or soap opera effect , or motion smoothing on you monitor ?

Just put <boot order='1'/> somewhere between <hostdev> </hostdev>

Yes i understand that your mboard doesn't have UEFI and it is only BIOS. I was talking about that from what i read OVMF has better communication than SEABIOS with real hardware overall. > (something that i don't detect...) that is what i have in mind, the thing about raid controller was separate thought. And yep maybe some formatting will express my thoughts accurate. PS: Long i stopped become frustrated on forums because first expressing your thoughts with words especially in writing form without visual contact of any mannerism is difficult thing, and second if it is not your native language.... which english is not mine..

The UEFI part is that your VM is better on OVMF and that is not in correlation with what type of bios you use bare metal. From what i read OVMF have more optimized communication with real hardware. As for editing problems with the Unraid GUI and XML form. If you want GUI you can use Virt-Manager docker from APPS > it is standard VM linux manager and doesn't bleach your xml when editing with it. AS for power saving 6.11 bring the new amd-pst driver for rizen, but from testing and from reading it is garbage for desktop it cut the performance too much.

Do you have 100Hz on baremetal? nad from nvidia screenshot that you post you doesn't have all the menus, i read your xml and saw that you use 5cores and ppl go about that odd numbers a representative for VM maybe that is why kvm hidden doesn't work for you.

yep something went wrong when posting ...