Windows 10 Guest on Linux host dies seconds after boot
Re: Windows 10 Guest on Linux host dies seconds after boot
I am experiencing the same problem with Fedora 36 host, 6.1.34vbox, and win10 guest. Tried reinstalling win10, getting the same results.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 10 Guest on Linux host dies seconds after boot
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Windows 10 guest doesn't start on Linux Host
Having the same issue. Host Fedora 36, vbox 6.1.34, trying to install guest Win10 (2H21). Will not complete the install.
Portion of log... deleted; only full logs can help
Portion of log... deleted; only full logs can help
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 10 Guest on Linux host dies seconds after boot
Merged topics. Duplicate posts are a no-no.
Please post a full log like you did before: viewtopic.php?f=3&t=95905&p=464909#p464909
Please post a full log like you did before: viewtopic.php?f=3&t=95905&p=464909#p464909
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows 10 Guest on Linux host dies seconds after boot
Just to be sure: Did you install VirtualBox 6.1.34 from Oracle or from Fedora, and if it was the former, was it the Fedora 36 specific variant, which only is available for a few weeks now?
Re: Windows 10 Guest on Linux host dies seconds after boot
Installed VirtualBox-6.1-6.1.34_20220514_fedora36-2.x86_64.rpm
Full log attached
Full log attached
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows 10 Guest on Linux host dies seconds after boot
I noticed that this file was a pre-test build, and it probably should be the same as in the current VirtualBox-6.1-6.1.34_150636_fedora36-2.x86_64.rpm file. Just in case, uninstall the former and install the latter (from Download VirtualBox for Linux Hosts.bmaring wrote:Installed VirtualBox-6.1-6.1.34_20220514_fedora36-2.x86_64.rpm
You either didn't zip the log file or something else went wrong. Please try again.bmaring wrote:Full log attached
Re: Windows 10 Guest on Linux host dies seconds after boot
zipped file attached
- Attachments
-
- vboxlog1.zip
- (27.26 KiB) Downloaded 17 times
Re: Windows 10 Guest on Linux host dies seconds after boot
Turns out that the log sent is for VirtualBox-6.1-6.1.34_150636_fedora36-2.x86_64.rpm
Attached is the log for VirtualBox-6.1-6.1.34_20220514_fedora36-2.x86_64.rpm is attached
Attached is the log for VirtualBox-6.1-6.1.34_20220514_fedora36-2.x86_64.rpm is attached
- Attachments
-
- vboxlog2.zip
- (28.81 KiB) Downloaded 14 times
Re: Windows 10 Guest on Linux host dies seconds after boot
by the way, I initially installed vbox using VirtualBox-6.1.34-150636-Linux_amd64.run. It worked fine for a couple of weeks, then fedora updated the kernel to 5.17.12-300.fc36.x86_64 and Microsoft updated windows 10 2H21. That installation stopped working about the same time.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 10 Guest on Linux host dies seconds after boot
The log does not appear to me to show any problems in the Virtualbox 'hardware'. It is possible that something has gone wrong in the VM drive file that has damaged the VM OS beyond recovery.
Try copying the drive file from your backups, to see if an earlier backup of the VM can run. Also, try starting a new VM with a new download of the Windows 10 installer ISO.
Try copying the drive file from your backups, to see if an earlier backup of the VM can run. Also, try starting a new VM with a new download of the Windows 10 installer ISO.
Re: Windows 10 Guest on Linux host dies seconds after boot
I can confirm the kernel update to 5.17.12 seems to be the problem, 5.17.11 is fine. Using fedora 36 host, w7 guest, on amd (desktop) & intel (2xlaptop). Indeed nothing special in the vbox logs, just windows programs on the guest dying within a few sec/min. 5.17.11 -> 12 changelog is mostly a cleanup of random, could that be related?bmaring wrote:by the way, I initially installed vbox using VirtualBox-6.1.34-150636-Linux_amd64.run. It worked fine for a couple of weeks, then fedora updated the kernel to 5.17.12-300.fc36.x86_64 and Microsoft updated windows 10 2H21. That installation stopped working about the same time.
Re: Windows 10 Guest on Linux host dies seconds after boot
Fedora kernels 5.17.12-300.fc36.x86_64 and 5.17.13-300.fc36.x86_64 are both non-functional with VirtualBox 6.1.34, regardless what the guest is (in my case the guests are all Linux as well).
Booting from 5.17.11-300.fc36.x86_64 makes everything work, including those VMs non-functioning under the later kernels, so the VMs don't sustain damage. Feels like memory corruption to me because running updates in the guest gives a lot of hash failures. Dragging windows on the screen causes the DM to crash a lot also.
Booting from 5.17.11-300.fc36.x86_64 makes everything work, including those VMs non-functioning under the later kernels, so the VMs don't sustain damage. Feels like memory corruption to me because running updates in the guest gives a lot of hash failures. Dragging windows on the screen causes the DM to crash a lot also.
Re: Windows 10 Guest on Linux host dies seconds after boot
Thank you, thank you, thank you. Booting from kernel 5.17.11 works like it has for the last 5 years.
Re: Windows 10 Guest on Linux host dies seconds after boot
Hello,
I can confirm this issue on Debian Linux.
Host OS: Debian Linux/SID
Host Kernel: 5.18.0-1
Host VirtualBox: 6.1.34-dfsg-3
Guest OS: Windows 10
Troubleshooting step 1:
- Disable Audio
- Disable Oracle Extention
- Changing memory / CPU settings
no luck so far
Troubleshooting step 2:
- Install Windows 11
- Default values used ( Enable Audio, Oracle Extension)
- No Mem / CPU changes
no luck so far
As Debian SID get's often updates, i went through the old apt logfiles. As other mentioned this could be Kernel related, i checked then the logfiles.
root@debian:/var/log/apt# dpkg -l |grep 'linux-image*' |tail -n 5
rc linux-image-5.17.0-1-amd64 5.17.3-1 amd64 Linux 5.17 for 64-bit PCs (signed)
rc linux-image-5.17.0-2-amd64 5.17.6-1+b1 amd64 Linux 5.17 for 64-bit PCs (signed)
ii linux-image-5.17.0-3-amd64 5.17.11-1 amd64 Linux 5.17 for 64-bit PCs (signed)
ii linux-image-5.18.0-1-amd64 5.18.2-1 amd64 Linux 5.18 for 64-bit PCs (signed)
ii linux-image-amd64 5.18.2-1 amd64 Linux for 64-bit PCs (meta-package)
[2022-06-06] Accepted Linux 5.18.2-1 package was accepted in SID branch 6th of June.
Kernel Release changes: h***s://tracker.debian[.]org/news/1331686/accepted-linux-5182-1-source-into-unstable-unstable
Kernel Release upstream information: h***s://tracker.debian[.]org/pkg/linux
I can't test 5.19.x as it just landed as RC in experimental tree.
Solution - booting into Kernel 5.17.0-X
Guest OS Win10/11 are stable again - Tested with Extension etc.
As this issue occurs in different Distributions ( Debian, Red Hat )...I guess Virtual Box Devs should take a deeper look into the code ?
Greetings,
Henrik
I can confirm this issue on Debian Linux.
Host OS: Debian Linux/SID
Host Kernel: 5.18.0-1
Host VirtualBox: 6.1.34-dfsg-3
Guest OS: Windows 10
Troubleshooting step 1:
- Disable Audio
- Disable Oracle Extention
- Changing memory / CPU settings
no luck so far
Troubleshooting step 2:
- Install Windows 11
- Default values used ( Enable Audio, Oracle Extension)
- No Mem / CPU changes
no luck so far
As Debian SID get's often updates, i went through the old apt logfiles. As other mentioned this could be Kernel related, i checked then the logfiles.
root@debian:/var/log/apt# dpkg -l |grep 'linux-image*' |tail -n 5
rc linux-image-5.17.0-1-amd64 5.17.3-1 amd64 Linux 5.17 for 64-bit PCs (signed)
rc linux-image-5.17.0-2-amd64 5.17.6-1+b1 amd64 Linux 5.17 for 64-bit PCs (signed)
ii linux-image-5.17.0-3-amd64 5.17.11-1 amd64 Linux 5.17 for 64-bit PCs (signed)
ii linux-image-5.18.0-1-amd64 5.18.2-1 amd64 Linux 5.18 for 64-bit PCs (signed)
ii linux-image-amd64 5.18.2-1 amd64 Linux for 64-bit PCs (meta-package)
[2022-06-06] Accepted Linux 5.18.2-1 package was accepted in SID branch 6th of June.
Kernel Release changes: h***s://tracker.debian[.]org/news/1331686/accepted-linux-5182-1-source-into-unstable-unstable
Kernel Release upstream information: h***s://tracker.debian[.]org/pkg/linux
I can't test 5.19.x as it just landed as RC in experimental tree.
Solution - booting into Kernel 5.17.0-X
Guest OS Win10/11 are stable again - Tested with Extension etc.
As this issue occurs in different Distributions ( Debian, Red Hat )...I guess Virtual Box Devs should take a deeper look into the code ?
Greetings,
Henrik