[Solved] Installing Windows 10

Discussions related to using VirtualBox on Linux hosts.
curano
Posts: 40
Joined: 30. Jun 2016, 18:52
Primary OS: Fedora 18
VBox Version: OSE Fedora
Guest OSses: Windows 10

Re: Installing Windows 10

Post by curano »

I found the sha1 checksums on the Microsoft Website.

Both checksums are the same.
2DDE3A5BFA60B7F10CD38DBD544CF00A075F8908
The download is correct !!!

The basic question - what the heck is going on here...
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Installing Windows 10

Post by mpack »

Well, if there's nothing wrong with the ISO, then I guess that leaves something wrong on the host. Any unusual host software installed?, that might be using VT-x and not tidying up correctly after itself? And of course the lack of memory is always a concern.

Incidentally, there may be a clue in the log, just before the guru meditation :-
VBox.log wrote: 00:00:50.057073 IEM: wrmsr(0xc0000080,0x0`00000800) -> #GP(0)
This is a warning that somebody tried to write to a I/O register (0xc0000080), leading to a general protection fault. However the former doesn't look like a register number to me, it's obviously an exception number. I don't know if that's the guest bug, or just a consequence of triple faulting.
curano
Posts: 40
Joined: 30. Jun 2016, 18:52
Primary OS: Fedora 18
VBox Version: OSE Fedora
Guest OSses: Windows 10

Re: Installing Windows 10

Post by curano »

I simply don't what kind of software is using VT-x, so I can't answer that question.
Can you give me a hint, please ?

Thanks
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Installing Windows 10

Post by mpack »

I'm no expert on VT-x usage on Linux hosts. On Windows it would be other VM platforms, some antivirus app, system level debuggers.
Martin
Volunteer
Posts: 2561
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Win10, Linux, OS/2

Re: Installing Windows 10

Post by Martin »

Did you also try to set the guest to only two or three virtual CPUs, leaving some of your four physical CPU cores free for the host to handle the VM?
curano
Posts: 40
Joined: 30. Jun 2016, 18:52
Primary OS: Fedora 18
VBox Version: OSE Fedora
Guest OSses: Windows 10

Re: Installing Windows 10

Post by curano »

The guest is set to 1 virtual CPU only
Martin
Volunteer
Posts: 2561
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Win10, Linux, OS/2

Re: Installing Windows 10

Post by Martin »

Sorry, the first of your logs showed numcpus=4
curano
Posts: 40
Joined: 30. Jun 2016, 18:52
Primary OS: Fedora 18
VBox Version: OSE Fedora
Guest OSses: Windows 10

Re: Installing Windows 10

Post by curano »

Yup, but the latest shows 1 cpu, because I did set up a new guest without modifications
curano
Posts: 40
Joined: 30. Jun 2016, 18:52
Primary OS: Fedora 18
VBox Version: OSE Fedora
Guest OSses: Windows 10

Re: Installing Windows 10

Post by curano »

Just some news:

I installed Fedora 24 from scratch onto my laptop (my test computer).
After that I installed Virtualbox 5.0.24.
A guest Windows 10.
The installation of Windows 10 went smoothly without any troubles.

Fedora 24 installed on my Workstation is an upgrade from F21 -> F22 -> F23 to F24.
It seems that some stuff is not the same as with a fresh installation.

The errors have nothing to do with Virtualbox.

Thanks for your help!
Curano
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Installing Windows 10

Post by mpack »

Thanks for reporting back.
frank
Oracle Corporation
Posts: 3362
Joined: 7. Jun 2007, 09:11
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows
Location: Dresden, Germany
Contact:

Re: Installing Windows 10

Post by frank »

curano wrote:I mounted the ISO file directly.
Still the same problem.
I uploaded the logs again
Your host kernel does not support PAE / NX but your guest requires Windows 10. I think using a PAE kernel on the host should fix your problem.
Post Reply