Hi everyone,
I'm new member, thanks for this forum and I'm sorry for my bad english.
Well, I installed Virtual Box in my Pc [Win10 64bit] and all looks like right.
I would like run Windos Server in virtual mode.
When I tryed to install "Windows Server eval 2019" it show a message: A critical error occurred while the virtual machine was running and the machine was stopped.
Virtual box advised to write to the forum attaching the log files, VBox.log and VBox.png ....
The "VBox.png" is 4Kb but the "VBox.log" file is 302Kb (Forum say me "too big") ... how can I do?
Can you help me?
Thank a lot
DnL
S.o.S.: a critical error occured.
Re: S.o.S.: a critical error occured.
Hi again to everyone,
I zipped both files [VBox.log and VBox.png] then now total weight is better ... 59Kb.
See image below: And in attachment you can find both files.
I need a solution for school ...
Thanks a lot who will want help me.
ciao
DnL
I zipped both files [VBox.log and VBox.png] then now total weight is better ... 59Kb.
See image below: And in attachment you can find both files.
I need a solution for school ...
Thanks a lot who will want help me.
ciao
DnL
- Attachments
-
- Logs (Vbox.lo+VBox.png).zip
- Here zip with VBox.log and VBox.png
- (58.62 KiB) Downloaded 5 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: S.o.S.: a critical error occured.
You're getting a triple fault when booting from the ISO, which usually indicates corruption of the ISO. Where did this come from?
Re: S.o.S.: a critical error occured.
Hi mpack, thanks for your reply.
I downloaded Iso file of WindowsServer [evaulation/trial version] by official Microsoft Windows site.
In attachment below, images of italian site and another of virtualBox folder
A my friend [schoolmate] did the same thing.
The file name is the same and its weight too.
Do you think it can be corrupt?
Tell me if you need others info
Thanks
DnL
I downloaded Iso file of WindowsServer [evaulation/trial version] by official Microsoft Windows site.
In attachment below, images of italian site and another of virtualBox folder
A my friend [schoolmate] did the same thing.
The file name is the same and its weight too.
Do you think it can be corrupt?
Tell me if you need others info
Thanks
DnL
-
fth0
- Volunteer
- Posts: 5690
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: S.o.S.: a critical error occured.
You're encountering a known bug (see VMs crash when VM OS Version set to Window 2019 for a detailed explanation). In the VM configuration, change General > Version to Windows 2016 (64-bit). This change is necessary, but possibly not enough:
Windows Server 2019 officially requires CPU capabilities that your CPU doesn't provide (EPT, Unrestricted Guest). If it insists in getting them, it won't be able to run on your host at all.
Windows Server 2019 officially requires CPU capabilities that your CPU doesn't provide (EPT, Unrestricted Guest). If it insists in getting them, it won't be able to run on your host at all.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: S.o.S.: a critical error occured.
One other thing, set the VM's System settings > Acceleration > Paravirtualization Interface to Hyper-V.
(This setting is not the Virtualbox-hobbling Hyper-V that is enabled or disabled on the host OS. It is a comm-channel between modern virtualization-aware OS's and the hypervisor.)
And 2019 is going to like 2 processors, not just 1.
(This setting is not the Virtualbox-hobbling Hyper-V that is enabled or disabled on the host OS. It is a comm-channel between modern virtualization-aware OS's and the hypervisor.)
And 2019 is going to like 2 processors, not just 1.
Re: S.o.S.: a critical error occured.
Hi, thanks to everyone fo your help!!!
Somethng happened.
1) I changed General > Version to Windows 2016 (64-bit). I reinstalled the Iso file arriving until the end of installation!!!
2) I changed the VM's System settings > Acceleration > Paravirtualization Interface to Hyper-V.
My computer is a bit old, I bought it in 2009 but it workin good until now.
It has 8Gb Ram and CPU is: Intel(R) Core(TM)2 QuadQ9300@ 2.50GHz.
I also had to enable virtualization in the bios.
Now looks like working.
I will make some tests.
Thank you so much for your time!!!!
DnL.
Somethng happened.
1) I changed General > Version to Windows 2016 (64-bit). I reinstalled the Iso file arriving until the end of installation!!!
2) I changed the VM's System settings > Acceleration > Paravirtualization Interface to Hyper-V.
My computer is a bit old, I bought it in 2009 but it workin good until now.
It has 8Gb Ram and CPU is: Intel(R) Core(TM)2 QuadQ9300@ 2.50GHz.
I also had to enable virtualization in the bios.
Now looks like working.
I will make some tests.
Thank you so much for your time!!!!
DnL.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: S.o.S.: a critical error occured.
Great! Glad you're up and running.