I got this error code: 0xc000021a every time I tried to even install this Guest OS: Windows 8.1(32 bit Version)
can you help me even install Windows 8.1 as Guest OS here?
if you're wondering, my Host OS was a 64-bit version of Windows 7
running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
ISTR that is the boot black screen error you get when you boot Windows 8.1 with an incorrect template. Check again that the correct OS version has been selected in the VM settings. In particular make sure you did not choose the 8.0 template, "Other Windows" or in fact anything else.
Btw, "even this" seems to be implying that "Windows 8.1 (32 bit)" is on the end of some kind of spectrum, though which one isn't clear to me. FYI, the requirements for Windows 8.1 (32bit) are essentially the same as Windows 8.1 (64 bit) and all later Windows. They are not the same as Windows 8.0 and earlier.
Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
No, I was not wondering about your host - that and other info (e.g. VirtualBox version) is available in the VM log (which btw should be provided as a matter of course, so we should not need to wonder). Note however that Windows 7 is no longer a supported host for VirtualBox 6.1.x, although I do not expect that is the reason for the current guest boot failure.
Btw, "even this" seems to be implying that "Windows 8.1 (32 bit)" is on the end of some kind of spectrum, though which one isn't clear to me. FYI, the requirements for Windows 8.1 (32bit) are essentially the same as Windows 8.1 (64 bit) and all later Windows. They are not the same as Windows 8.0 and earlier.
Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
No, I was not wondering about your host - that and other info (e.g. VirtualBox version) is available in the VM log (which btw should be provided as a matter of course, so we should not need to wonder). Note however that Windows 7 is no longer a supported host for VirtualBox 6.1.x, although I do not expect that is the reason for the current guest boot failure.
-
- Posts: 17
- Joined: 23. Jul 2021, 11:36
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 95, Ubuntu, Windows XP
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
I has saved "VBox.log" into a zip file and attached that zip file in another post of mine(in another thread I authored here in Virtualbox forum)mpack wrote: Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
Last edited by mpack on 22. Oct 2021, 18:57, edited 1 time in total.
Reason: Trim verbatim quote of previous post.
Reason: Trim verbatim quote of previous post.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
Please post it here again, to save your fellow unpaid forum volunteers from having to use their own time to hunt it down. Thanks!
-
- Posts: 17
- Joined: 23. Jul 2021, 11:36
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 95, Ubuntu, Windows XP
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
I has attached the file here tooscottgus1 wrote:Please post it here again, to save your fellow unpaid forum volunteers from having to use their own time to hunt it down. Thanks!
- Attachments
-
- .VirtualBox.zip
- repost of same file for this thread
- (156.63 KiB) Downloaded 14 times
-
- Volunteer
- Posts: 5102
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
It crashed out because there was not enough memory available. How much RAM have you allocated to the vm? You only have about 1G available.
Windows 8.1, like Windows 10, prefers at least 2G RAM and 2 processors.
Code: Select all
00:00:27.075720 Host RAM: 8062MB (7.8GB) total, 1117MB available
Code: Select all
00:00:55.211598 VM: Raising runtime error 'HostMemoryLow' (fFlags=0x2)
00:00:55.405464 Changing the VM state from 'RUNNING' to 'SUSPENDING'
Bill
-
- Posts: 17
- Joined: 23. Jul 2021, 11:36
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 95, Ubuntu, Windows XP
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
I tried raising the Guest RAM and tried 2 processor and this still happens(if Host still have enough memory)BillG wrote:It crashed out because there was not enough memory available. How much RAM have you allocated to the vm? You only have about 1G available.
Code: Select all
00:00:27.075720 Host RAM: 8062MB (7.8GB) total, 1117MB available
Windows 8.1, like Windows 10, prefers at least 2G RAM and 2 processors.Code: Select all
00:00:55.211598 VM: Raising runtime error 'HostMemoryLow' (fFlags=0x2) 00:00:55.405464 Changing the VM state from 'RUNNING' to 'SUSPENDING'
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
The VM's RAM was:
A new zipped vbox.log will be necessary for us to see what happened. (General concept: if a VM does not work after changing a setting, post a zipped vbox.log.)
Look in the log for this line, and the line Bill quoted: "Host RAM .... available". Together they will tell if available RAM is enough for the VM's set RAM.00:00:30.768187 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
A new zipped vbox.log will be necessary for us to see what happened. (General concept: if a VM does not work after changing a setting, post a zipped vbox.log.)
-
- Posts: 17
- Joined: 23. Jul 2021, 11:36
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 95, Ubuntu, Windows XP
Re: running Windows 8.1(32-bit) as guestOS using 64bit!Windows 7 SP1 for Host OS
I has uploaded newly zipped vbox.log file here againscottgus1 wrote:The VM's RAM was:Look in the log for this line, and the line Bill quoted: "Host RAM .... available". Together they will tell if available RAM is enough for the VM's set RAM.00:00:30.768187 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
A new zipped vbox.log will be necessary for us to see what happened. (General concept: if a VM does not work after changing a setting, post a zipped vbox.log.)
- Attachments
-
- .VirtualBox.zip
- updated the file
- (229.07 KiB) Downloaded 10 times