Opened 20 months ago
Last modified 16 months ago
#21574 new defect
Windows 11 guests do not boot and try auto repair on 7.0.x, x>=4
| Reported by: | lorien_an_old_one | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox-7.0.6 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
Dear Users
It appears that my Windows 11 guests do not boot once I have updated to 7.0.4 or higher fedora versions of VirtualBox (use VB for fc36, although I run fc37)
In fact, once 7.0,4 or higher is installed the guests start claiming that need to do an auto repair, which fails of course. Once one gets back to 7.0.2 everything starts running again. The funny thing is that if I use a saved state WIN11 guest it can run, once you keep saving its state. In more detail: How the bug showed itself. A virtual machine runs codes (when host is idle) that do molecular dynamics trajectories (exe from fortran compiled with gcc). The vb was modified for avoiding the summer time change of last weekend which would make an unwanted jump to the file name stamps. Ideas for stopping summer time change were implemented as read from the web (followed blindly, hopefully with no error).
For the example described here by the attached logs(links), a vb 7.0.2 was installed and a demo machine was saved and retrieved. Saved state under 7.0.2 and installed 7.0.6 which worked when state was recovered. Machine was ended normally but it can not restart when 7.0.6 is installed where it goes to auto repair. Then reinstalled 7.0.2 and things became normal (however, I lost the state and all my in memory computed data).
The zip files (VBox log files) and some that I copied as the machine was running exist here
https://forums.virtualbox.org/download/file.php?id=49481
https://forums.virtualbox.org/download/file.php?id=49485
Best to all developers and users
Attachments (1)
Change History (2)
by , 16 months ago
VBOX log file when the same machine (used to run with VBOX 7.0.2 under fedora 37, or 6.x under fedora 38) is being used with 7.0.10 under fc38
Dear Users
The new VirtualBox 7.0.10 (158379) version running on Fedora 38 does have the same issues regorted in the original listing, not being shared by the older 6.1.46 version.
So I guess that it may be worthwhile being investigated as a bug.