Jryski

I made the move to IPVLAN i also made these changes... Host access to custom networks: Enabled Preserve user defined networks: Yes All issues have ceased. This is not an ideal solution, but it's working for me for now. I'm now at 48 hours stable and error free for the first time in months. I'm not sure why they call this issue resolved in this version, as it's clearly still an issue, but I'm stable for now. Thanks for the help along the way.

I made the move to IPVLAN, I also have ubiquiti gear etc etc. i also made these changes... Host access to custom networks: Enabled Preserve user defined networks: Yes I've yet to have any issues yet personally and all issues have ceased. This is not an ideal solution, but it's working for me for now. I'm now at 48 hours stable and error free for the first time in months.

I've been having this same behavior. Sometimes hours, sometimes a day or 2 between crashes. I'm seeing a lot of trace calls in my logs, I'm beginning to think the fix they thought they had for the macvlan issue wasn't a fix. I had zero problems in 6.11.5, but after moving into 6.12.5 this began. I've run memtest, swapped components, removed everything not necessary... I'll be following this and I have a similar post in the forums ongoing.

Thanks, I will try that and report back.

I finally feel like I've found something in the logs, attaching for anyone who might understand what I'm seeing. Syslog Errors.txt

Well, after running memtest and getting passes, rebuilding the docker image, checking the SMART on all drives, changing all BIOS settings to recommended setting, removing the XMP profile on the RAM, it's still freezing. I've checked all the logs and all I see is mover running, mover completes and nothing else is written to the logs, the server simply stops responding. I've had this happen while under load and while idle. The flash drive is only 3 months old, I had it fail on me a few months ago. I'm at a loss here.

SAMSUNG MUF-32AB/AM FIT Plus 32GB

While scrubbing the Syslog for personal details, I found this. I'm exploring the potential that this is the cause, and will be changing "typical idle current" as I've read this can cause random stability issues. If this is the case I will post for posterity.

This server has been stable for 2-3 years, no changes to hardware or configuration since this began. The server goes unresponsive from all remote connectivity. I'm not sure about local, I'm waiting for another failure top verify if anything is accessible locally, I was running headless. Dockers stop responding, UI, SSH, all completely dead. A restart brings it back up. I'm including the Diagnostic from just after the last 2 failures and recovery. I don't see anything in the logs, but I'm hoping there's a clue in the files. ASRock X570 Taichi ryzen 9 5950x 128 GiB DDR4 GSKILL Memory 6.12.4 unimatrixzero-diagnostics-20231207-1722.zip unimatrixzero-diagnostics-20231205-1604.zip

Same issue in DISKPART, it fails due to "i/o errors" wondering if it has something to do with the fact that the drive is being passed as an entire controller, but also the xml refers to it as a generic PCI device, not a SCSI controller? Grasping at straws. At this point, I'm ready to call this non-working until the updates are here. I can see the drive, but no luck making changes. The VM also takes 10 minutes to get to the windows installer screen, and hangs at each step. I've attempted to limit the cores down to 1 which was a workaround in the past, as well as reduce the ram down to minimum required for windows 11 to allow the install. Despite all our effort, I believe it's time to wait for official support.

I will update if I can get this working via whatever means. Thanks again for all the information, I'll update this post after the next libvert/qemu update with how I update the XML. I tell you what though, I REALLY wish they'd add a toggle to make the XML sticky when a GUI change is made... Thanks again for all the work.

Windows throws an error "We couldn't create a new partition error: 0xfdd10070" This is the first time I've got this particular passthrough working, This nvme controller sm2262 has been an issue all along, samsung NVME I had in it before worked fine.

May have put my party hat on too soon. I can see the drive now in the VM, but so far I can't make any changes to it, so no creating partitions or formatting, or installing windows.

That did it. I'm super impressed. I've included the diagnostics with the VM running, your last edits worked perfectly... this post should get stickied, as I know I'm not alone in trying to do this. Thank you for all the help. unimatrixzero-diagnostics-20220322-1404.zip

Certainly unimatrixzero-diagnostics-20220322-1259.zip