[[6.10] TimeMachine backups continue to fail "failed to attach using diskimages2" "operation not supported by device"]

11 minutes ago, wgstarks said:

I originally fixed my issue by re-installing macOS. It’s an easy process. The user experience is really no different than installing an update. Just takes a few minutes longer since it’s installing the entire OS rather than just the modified software. Same as what the combo updates did before Apple discontinued them.

I just wish that had solved the issue for me. I've even done it twice with no success. 

[[6.10] TimeMachine backups continue to fail "failed to attach using diskimages2" "operation not supported by device"]

14 hours ago, wgstarks said:

I would suggest posting in the support thread for the docker. Just click the docker name and select support.

I actually have, assuming the URL "Support" takes me to is correct:

 

[[6.10] TimeMachine backups continue to fail "failed to attach using diskimages2" "operation not supported by device"]

I've also been chasing this issue down. The docker container fails for me with the error:

Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading}

I updated unRAID from 6.9.2 to 6.10.0 at the same time I updated macOS to 12.4, so I'm not sure which broke it.

I've also done a reinstall of macOS from the recovery menu (rebooting holding a key combo, etc) to no avail.

[Nested VM not possible]

When I go to make the change in the <cpu> section, I receive an error saying, "XML error: Non-empty feature list specified without CPU model"

 

My section is: 

  <cpu>
    <topology sockets='1' cores='5' threads='1'/>
    <feature policy='require' name='vmx'/>
  </cpu>

 

[Nested VM not possible]

No worries, thank you!

So, just to be sure, I'd add the kvm-intel.nested=1  in the Unraid OS section, so it's exactly as below?

kernel /bzimage
append initrd=/bzroot kvm-intel.nested=1

But then where do you go to edit the VM's CPU section? LIke, where are the config files for them? I'm assuming /etc/libvirt/qemu/VMName.xml, correct?

[Nested VM not possible]

@jonp Just wondering if you were able to reproduce this issue in your lab or not. I know it's been crazy with the 6.8 version coming up, but I'm just curious.