Hi, experiencing segfaults in VBoxDD.so when trying to restore a saved virtual machine (win11 guest). Anyone experiencing something similar? This seems new, was not happining until recent. Dropping the machine state and booting the machine makes it start up apparently fine.
You may run into issues if you sync a new version of virtualbox while a saved instance uses on older version.
Either see if you have the earlier version in your pacman cache /var/cache/pacman/pkg - then downgrade or discard the saved state - dataloss may result if you are kepping source files open.
Thought about that… so discarded state rebooted saved restored, but the issue seems repeatable also in this scenario. Cannot understand if it was triggered by the updade of some lib used by VirtualBox or some update in the guest.
In any case, don’t think it should ever segfault, so I reported it upstream.
I think that the issue is that I had a virtio storage attachment. Apparently, virtio is broken in vbox.
You think ? How did you reach that thought ? Source ?
Says who? How did you reach that conclusion ? Source ?
Are you referring to the possibility of attaching a qcow image ?
If so then it is even more important to so keep the system in sync.
Did ask in the VirtualBox forum and you create an issue with VirtualBox developers ?
Removing the virtio attachment, virtualbox does not segfault anymore. Seems a sufficient evidence for me.
Thank you for clarifying - that appears to be sufficient your case - although the conclusion may not be generally applicable - it is definitely worth a try in a troubleshooting situation.
To clarify better: apparently Virtualbox supports virtio attachments, so in the recent past I tried adding one and installing in a Win 11 guest the virtio drivers. This combination enables Win 11 to use a VDI image through the virtio attachment rather than the AHCI one and in principle should deliver a better performance due to the reduced overhead of paravirtualization over real hardware virtualization. As a matter of fact, there was no perceived benefit, so I moved the VDI disk back to the AHCI attachment. Doing so, I did not remove the virtio attachment, that remained there with no disk images attached to it. Some time later, I discovered that this combination was causing vboxdd.so to crash while resuming saved state. Removing the virtio attachment stopped the crashes completely. I reported the issue to VirtualBox (#22128 (Cannot restore Win 11 from saved state) – Oracle VirtualBox), let’s see how this develops.
Also found out that as of approximately one year ago, the vbox developers were saying:
[virtio-scsi] is still somewhat experimental […]. The code is still quite new, with a lot of changes in the generic support for virtio 1.0 and later with VirtualBox 7.0. What existed in 6.1 had a significantly different codebase, and not all of the changes were in the ‘right direction’.
The testing with virtio-scsi drivers other than the Linux ones (and even with the Linux ones over the full range of kernels which could deal with it) was so far limited.
See Status of virtio-scsi? - virtualbox.org, so the situation is probably still progressing and bugs are to be expected.
Closed as abandoned topic.