Whonix-Workstation-XFCE Aborted error

sterile_crab · March 8, 2022, 1:08am

Out of the blue I’m unable to start my Workstation.

Everything vanilla except the default password.

Last thing I did was share a folder from guest to host and then delete.

Edit: Changing the storage to AHCI does nothing.

00:00:00.658099 SUP: Opened VBoxDDR0.r0 (/usr/lib/virtualbox/VBoxDDR0.r0) at 0xXXXXXXXXXXXXXXXX.
00:00:00.658201 CPUM: SetGuestCpuIdFeature: Enabled xAPIC
00:00:00.658358 IOAPIC: Using implementation 2.0! Chipset type ICH9
00:00:00.658389 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:00.658495 VMMDev: cbDefaultBudget: 523 339 328 (1f318640)
00:00:00.659330 Shared Folders service loaded
00:00:00.659554 Guest Control service loaded
00:00:00.674541 VGA: Using the 386+ BIOS image.
00:00:00.675439 VMSetError: /home/vbox/vbox-6.1.32/src/VBox/Devices/Storage/DrvVD.cpp(4670) int drvvdConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES
00:00:00.675447 VMSetError: DrvVD: Configuration error: keys incorrect at level 0
00:00:00.675547 AssertLogRel /home/vbox/vbox-6.1.32/src/VBox/Devices/Storage/DevLsiLogicSCSI.cpp(5544) int lsilogicR3Construct(PPDMDEVINS, int, PCFGMNODE):
00:00:00.675550 LsiLogic: Failed to attach Device0
00:00:00.675552 PDM: Failed to construct ‘lsilogicsas’/0! VERR_NOT_IMPLEMENTED (-12) - The request function is not implemented.

AHCI enabled

00:00:00.657363 SUP: Opened VBoxDDR0.r0 (/usr/lib/virtualbox/VBoxDDR0.r0) at 0xXXXXXXXXXXXXXXXX.
00:00:00.657363 CPUM: SetGuestCpuIdFeature: Enabled xAPIC
00:00:00.657363 IOAPIC: Using implementation 2.0! Chipset type ICH9
00:00:00.657363 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:00.657363 VMMDev: cbDefaultBudget: 523 339 328 (1f318640)
00:00:00.658866 Shared Folders service loaded
00:00:00.659084 Guest Control service loaded
00:00:00.674863 VGA: Using the 386+ BIOS image.
00:00:00.675851 DrvVD: Flushes will be ignored
00:00:00.675859 DrvVD: Async flushes will be passed to the disk
00:00:00.677150 VD: VDInit finished with VINF_SUCCESS
00:00:00.677233 AIOMgr: Endpoint for file ‘/var/home/sterile_crab/VirtualBox VMs/Whonix-Workstation-XFCE/Whonix-XFCE-15.0.1.5.1-disk002.vdi’ (flags 000c0723) created successfully
00:00:00.677819 VD: Opening the disk took 709904 ns
00:00:00.677866 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 209715200
00:00:00.677926 AHCI: Port1: No driver attached
00:00:00.677931 AHCI: Port2: No driver attached
00:00:00.677933 AHCI: Port3: No driver attached
00:00:00.677935 AHCI: Port4: No driver attached
00:00:00.677936 AHCI: Port5: No driver attached
00:00:00.677938 AHCI: Port6: No driver attached
00:00:00.677940 AHCI: Port7: No driver attached
00:00:00.677942 AHCI: Port8: No driver attached
00:00:00.677944 AHCI: Port9: No driver attached
00:00:00.677946 AHCI: Port10: No driver attached
00:00:00.677948 AHCI: Port11: No driver attached
00:00:00.677950 AHCI: Port12: No driver attached
00:00:00.677952 AHCI: Port13: No driver attached
00:00:00.677954 AHCI: Port14: No driver attached
00:00:00.677956 AHCI: Port15: No driver attached
00:00:00.677967 AHCI#0: Reset the HBA
00:00:00.677969 VD#0: Cancelling all active requests
00:00:00.678056 AssertLogRel /home/vbox/vbox-6.1.32/src/VBox/Devices/Storage/DevLsiLogicSCSI.cpp(5544) int lsilogicR3Construct(PPDMDEVINS, int, PCFGMNODE):
00:00:00.678065 LsiLogic: Failed to attach Device0
00:00:00.678067 PDM: Failed to construct ‘lsilogicsas’/0! VERR_PDM_CFG_MISSING_DRIVER_NAME (-2822) - The attached driver configuration is missing the ‘Driver’ attribute.
00:00:00.678087 VMSetError: /home/vbox/vbox-6.1.32/src/VBox/VMM/VMMR3/PDMDevice.cpp(484) int pdmR3DevInit(PVM); rc=VERR_PDM_CFG_MISSING_DRIVER_NAME
00:00:00.678088 VMSetError: Failed to construct device ‘lsilogicsas’ instance #0

Patrick · March 8, 2022, 10:20am

See:
Aborted Status

(Whonix is based on Kicksecure.)

sterile_crab · March 8, 2022, 3:57pm

I wouldn’t be making this thread if this worked.

Unless, of course, basically saying “sorry, not Whonix problem” is your idea of giving support.

What a waste of time.

Patrick · March 9, 2022, 9:46am

Technical background:

I cannot troubleshot this because I cannot reproduce this issue. And I haven’t written the application source code that is throwing that error message. Developing / troubleshooting VirtualBox is outside my skillset. Developing a solution based on / using VirtualBox doesn’t make me a VirtualBox developer.

The most I could do is copy/paste your report to the VirtualBox forums and perhaps to the VirtualBox issue tracker. Acting kinda as a human proxy. But that would be a bit pointless since I couldn’t answer any follow-up questions.

The most I could help with is reviewing any support request drafts and rewrite for clarify to increase chances of getting understood/fixed by upstream.