Fedora 33 64 bit host - win10 64 guest - constant reboots
Fedora 33 64 bit host - win10 64 guest - constant reboots
Hello,
For some reason, I am getting constant rebooting in the windows 10 guest on my machine.
kmod-VirtualBox-5.8.6-201.fc32.x86_64-6.1.14-1.fc32.x86_64
VirtualBox-6.1.14-2.fc32.x86_64
VirtualBox-server-6.1.14-2.fc32.x86_64
akmod-VirtualBox-6.1.14-1.fc32.x86_64
kmod-VirtualBox-5.7.15-200.fc32.x86_64-6.1.14-1.fc32.x86_64
VirtualBox-kmodsrc-6.1.14-2.fc32.noarch
Not much information. Usually no BSOD, just constant reboots.
Any ideas?
For some reason, I am getting constant rebooting in the windows 10 guest on my machine.
kmod-VirtualBox-5.8.6-201.fc32.x86_64-6.1.14-1.fc32.x86_64
VirtualBox-6.1.14-2.fc32.x86_64
VirtualBox-server-6.1.14-2.fc32.x86_64
akmod-VirtualBox-6.1.14-1.fc32.x86_64
kmod-VirtualBox-5.7.15-200.fc32.x86_64-6.1.14-1.fc32.x86_64
VirtualBox-kmodsrc-6.1.14-2.fc32.noarch
Not much information. Usually no BSOD, just constant reboots.
Any ideas?
Last edited by H0wdy on 6. Nov 2020, 15:37, edited 1 time in total.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.
Right-click the guest in the main Virtualbox window's guest 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 guest in the main Virtualbox window's guest 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.
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
I think this includes it.
Last edited by mpack on 14. Sep 2020, 11:48, edited 1 time in total.
Reason: Deleted partial log.
Reason: Deleted partial log.
-
- Posts: 8
- Joined: 15. Jul 2020, 05:18
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
I have the exact same issue, I posted awhile ago also with logs. Running Fedora 32 64 bit as well, constant reboots with windows 10 and windows server 2016/2019, I have tried every setting and adjustment change possible. No dice. Linux guests are completely fine. I can run windows guests in vmware and kvm without issue. Only VirtualBox has issues.H0wdy wrote: For some reason, I am getting constant rebooting in the windows 10 guest on my machine.
Last edited by mpack on 14. Sep 2020, 11:49, edited 2 times in total.
Reason: Trim unnecessary verbatim quote.
Reason: Trim unnecessary verbatim quote.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
@Howdy, please review again the instructions you were given. We want a zip of the entire log, not an unzipped extract of some bit you think might be relevant.
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
Here you go.
- Attachments
-
- Windows 10-2020-09-13-11-06-53.log.zip
- (35.04 KiB) Downloaded 26 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
@Howdy.
More on the crash.
Anyway the crash is happening in the guest, the VM just detects it via the Hyper-v paravirtualization API. Hard to say more without knowing precisely what the VM was doing at the moment of the crash.
3D acceleration disabled so probably not a graphics driver problem.
You are also maxing out your cores: 4 cores available, all assigned to the VM. Not good from a stability POV. There should be no more than 2 cores assigned to the VM.
I don't like the fact that you only gave 64MB graphics RAM and then allocated a 1920x956 virtual display size. Increase graphics RAM to 128MB.
I would watch that host RAM too, you are allocating 2048MB + 64MB, which is a large fraction of the 2784MB available. I would free up some RAM before launching any VMs, or add more RAM to the host.
This is not VirtualBox. This is someone else's build from the VirtualBox sources. Looks like it wasn't done right.00:00:00.956670 VirtualBox VM 6.1.14_RPMFusion r140239 linux.amd64 (Sep 8 2020 00:00:00) release log
More on the crash.
Strange to see a data misalignment error on Intel architecture. Perhaps some of the SIMD or GPU instructions are alignment sensitive.00:25:23.191787 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8030fee25c3 P3=0xffff8909169eec64 P4=0x7010008004002001
00:25:23.210409 GIMHv: BugCheck 1e {ffffffff80000002, fffff8030fee25c3, ffff8909169eec64, 7010008004002001}
00:25:23.210410 KMODE_EXCEPTION_NOT_HANDLED
00:25:23.210411 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:25:23.210411 P2: fffff8030fee25c3 - EIP/RIP
00:25:23.210412 P3: ffff8909169eec64 - Xcpt param #0
00:25:23.210412 P4: 7010008004002001 - Xcpt param #1
00:25:26.235016 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
Anyway the crash is happening in the guest, the VM just detects it via the Hyper-v paravirtualization API. Hard to say more without knowing precisely what the VM was doing at the moment of the crash.
3D acceleration disabled so probably not a graphics driver problem.
You are also maxing out your cores: 4 cores available, all assigned to the VM. Not good from a stability POV. There should be no more than 2 cores assigned to the VM.
I don't like the fact that you only gave 64MB graphics RAM and then allocated a 1920x956 virtual display size. Increase graphics RAM to 128MB.
I would watch that host RAM too, you are allocating 2048MB + 64MB, which is a large fraction of the 2784MB available. I would free up some RAM before launching any VMs, or add more RAM to the host.
-
- 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: Fedora 32 64 bit host - win10 64 guest - constant reboots
Update the VirtualBox Guest Additions from 6.1.4 to 6.1.14.H0wdy wrote:Any ideas?
I don't know much about Windows kernel-mode driver programming, but it seems that 8-byte long data types (e.g. __int64) must be aligned on 4-byte boundaries: Avoiding Misalignment of Fixed-Precision Data Types.mpack wrote:Strange to see a data misalignment error on Intel architecture.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
It has long been the case on Intel architecture that there's a penalty for misaligned I/O, basically because it has to do two bus transfers and stitch the result together. But unlike (say) ARM architecture, AFAIK there's still no hardware exception for misaligned access. Of course I'm talking about the CPU. It's quite possible that peripheral hardware, in particular DMA, would error out on misaligned access.
Hard to see how the latter issue could arise in a VM tho. I'm thinking an error in the build, not directing the compiler to use the proper alignments.
Hard to see how the latter issue could arise in a VM tho. I'm thinking an error in the build, not directing the compiler to use the proper alignments.
-
- 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: Fedora 32 64 bit host - win10 64 guest - constant reboots
As far as I understand the Microsoft documentation I linked to, it's a software generated exception, e.g. ProbeForRead/ProbeForWrite checking the alignment of a given pointer to a user data buffer that is given to a kernel-mode driver.
I'd guess an uninitialized user data buffer pointer, which is given to a kernel-mode driver, could be enough to trigger this.
I'd guess an uninitialized user data buffer pointer, which is given to a kernel-mode driver, could be enough to trigger this.
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
I'm still having this issue. Any ideas?
I even switched to the one straight from here:
https://www.virtualbox.org/wiki/Downloads
May have something to do with "kernel security check failure?"
I even switched to the one straight from here:
https://www.virtualbox.org/wiki/Downloads
May have something to do with "kernel security check failure?"
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Fedora 32 64 bit host - win10 64 guest - constant reboots
Re-post an up-to-date log as instructed above.H0wdy wrote:Any ideas?
I even switched to the one straight from here:
Re: Fedora 33 64 bit host - win10 64 guest - constant reboots
Upgraded to Fedora 33, still happening.
See log.
See log.
- Attachments
-
- log.txt.zip
- (26.54 KiB) Downloaded 23 times
Re: Fedora 33 64 bit host - win10 64 guest - constant reboots
I confirm this exact issue occurs on Ubuntu Linux 20.04.1 with hwe kernel 5.8.0-36-generic and Virtualbox 6.1.16-140961~Ubuntu~eoan installed through the official repositories virtualbox apt repositories for Ubuntu focal.
This problem occurs even with a virgin installation of Windows 10 (guest). It does not occur with the non-hwe Ubuntu 20.04.1 kernel 5.4.
My error log:
This problem occurs even with a virgin installation of Windows 10 (guest). It does not occur with the non-hwe Ubuntu 20.04.1 kernel 5.4.
My error log:
Code: Select all
00:21:26.789581 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8065acd7d93 P3=0xffffe0077a4663bb P4=0x7010008004002001
00:21:26.789648 GIMHv: BugCheck 1e {ffffffff80000002, fffff8065acd7d93, ffffe0077a4663bb, 7010008004002001}
00:21:26.789649 KMODE_EXCEPTION_NOT_HANDLED
00:21:26.789649 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:21:26.789649 P2: fffff8065acd7d93 - EIP/RIP
00:21:26.789649 P3: ffffe0077a4663bb - Xcpt param #0
00:21:26.789649 P4: 7010008004002001 - Xcpt param #1
00:21:30.726903 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
Re: Fedora 33 64 bit host - win10 64 guest - constant reboots
I have been having the same issues with a Win10 Pro 64 guest. I am running Pop!_OS 20.04 LTS. I was running the VirtualBox 6.14 that is in the Ubuntu repositories but switched to the Official VirtualBox repositories and installed 6.16. I still had issues with random reboots of my Win10 Pro guest. They would happen about 5 minutes or so after the VM was launched. Nothing was running other than Windows Explorer and I would get the error message KMODE_EXCEPTION_NOT_HANDLED (just like Macy previously posted). The odd thing was I have a Win7 Pro VM that would run just fine as well as a WinXP VM. Those VM's ran without random reboots at all. I looked at the Win7 VM settings to see if there was a difference and I discovered one.
In the Settings --> System --> Acceleration. The Win10 guest had the Paravirtualization Interface set to Default and the Win7 guest had it set to Legacy. I tried Hyper-V and it would still reboot. I switched to Legacy (like Win7) and I'm not having the reboots happen. I can boot the machine and it won't reboot after 5 minutes of the VM starting. I will notice a reboot/reset of the VM if my system goes to Suspend (which I suspect is the expected behaviour).
I have tried running some apps (don't have much since it's a relatively fresh install) and no reboots noticed. I'm attaching a screenshot of the setting I used. Maybe changing this setting will help you.
In the Settings --> System --> Acceleration. The Win10 guest had the Paravirtualization Interface set to Default and the Win7 guest had it set to Legacy. I tried Hyper-V and it would still reboot. I switched to Legacy (like Win7) and I'm not having the reboots happen. I can boot the machine and it won't reboot after 5 minutes of the VM starting. I will notice a reboot/reset of the VM if my system goes to Suspend (which I suspect is the expected behaviour).
I have tried running some apps (don't have much since it's a relatively fresh install) and no reboots noticed. I'm attaching a screenshot of the setting I used. Maybe changing this setting will help you.