[Resolved] Can't install Windows 10 1809 as guest on FreeBSD

Discussions related to using VirtualBox on other (unsupported) hosts like FreeBSD.
Post Reply
R_Friemer
Posts: 2
Joined: 23. Jan 2019, 21:07

[Resolved] Can't install Windows 10 1809 as guest on FreeBSD

Post by R_Friemer »

Hello,

I'm using FreeBSD 12.0 and Virtualbox 5.2.24 r128122. I have 2 VMs, windows 7 and Linux Mint 19 running. On FreeBSD 11.2 all three VM have been running without problems but now Windows10 is not booting anymore.

I got this CPU
---<<BOOT>>---
Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-RELEASE-p2 GENERIC amd64
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
VT(vga): resolution 640x480
CPU: Intel(R) Xeon(R) CPU           W3690  @ 3.47GHz (3458.08-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x29ee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI>
  AMD Features=0x2c000800<SYSCALL,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 25769803776 (24576 MB)
avail memory = 24972435456 (23815 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <GBT    GBTUACPI>
FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs
FreeBSD/SMP: 1 package(s) x 6 core(s) x 2 hardware threads
...
The Kernel-Modules are installed and loaded.

In the message-Log I have theses messages about Vboxdrv
vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
I want to install Windows 10, so I've created a new VM with the same settings as Windows 7, but as Type I've chosen Windows10 and 64Bit.
  • 2 CPUs
  • 4GB RAM
  • NO PAE/NX
  • Default Paravirtualisation
  • VT-x/AMD-V activated
  • 2D Activated
  • 256MB For Graphics
  • Sata-Controller with Host I/O-Cache
  • Dyn. VDI-HDD Image with 88GB Capacity
  • Network-Settings are NAT
When I start the VM and VirtualBox is trying to boot from the Installation-iso of 1809 there comes up a Windows with Guru Mediation. In the Log-File I can find with Information but I can't find the fault.

Can somebody help me to get Windows 10 up and running? Where is the fault?

Kind Regards

Robert
Attachments
vbox.log
Log of Virtualbox 1
(127.52 KiB) Downloaded 152 times
Last edited by socratis on 15. Dec 2019, 12:09, edited 2 times in total.
Reason: Marked as [Resolved].
StephenKery
Posts: 1
Joined: 1. Feb 2019, 23:12

Re: Can't install Windows 10 1809 as guest on FreeBSD

Post by StephenKery »

Hi,
I am also facing the same issue mentioned here. When install windows 10 on FreeBSD 12.0 Virtualbox 5.2.24 r128122. I already had ubuntu 14.04 and windows 10. But now my windows 10 is not booting does anyone have solution?
R_Friemer
Posts: 2
Joined: 23. Jan 2019, 21:07

Re: Can't install Windows 10 1809 as guest on FreeBSD

Post by R_Friemer »

Hi,

Just to give a feedback. I have found a solution!

The problem lies under the OS in the BIOS. I had deactivated the NX (No-Execution) Function in the BIOS. I found with when I tried to upgrade my virtual Windows 7 to Windows 10.

So, for anyone who has the same Problem, check in the BIOS that NX is Activated.

I hope this helps.

Kind Regards

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

Re: Can't install Windows 10 1809 as guest on FreeBSD

Post by mpack »

Thanks for reporting back with a solution. People should however be aware that, AFAIK FreeBSD is not an officially supported host OS, so failures on that host will not usually generate much interest.
Dale
Posts: 1
Joined: 3. Jan 2018, 19:21

Re: Can't install Windows 10 1809 as guest on FreeBSD

Post by Dale »

If you mean virtualbox, it has had a freebsd package since 2010 and I understand is actively supported, although the forums will certainly show there have been issues. On the other hand, I gave up trying to get a vbox vm running on a T500 thinkpad running Linux mint.

Maybe it's my hardware, my web server is an 8? year old unbranded HP media server with a Intel 6600 dual-core 2.4G and 6G RAM running freebsd 11.3 (the VM headless server will take 2G). The failed LInux mint attempt was with an even holder T500 thinkpad with 4G RAM.

Meanwhile I've rebooted the host server and all is ok. Seems the kernel module failed (it may have been possible to reload the module with the server staying up, but that's beyond me.

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

Re: Can't install Windows 10 1809 as guest on FreeBSD

Post by mpack »

Dale wrote:If you mean virtualbox, it has had a freebsd package since 2010 and I understand is actively supported
If you can find FreeBSD listed in the Supported Host Operating Systems section of the user manual (1.4) then you're a better man than I. If it has third party support then that is not the business of these forums, which is for the official release only.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: [Resolved] Can't install Windows 10 1809 as guest on FreeBSD

Post by socratis »

Dale wrote:If you mean virtualbox, it has had a freebsd package since 2010
... compiled by and supported by the FreeBSD people, based on the Open Source Edition (OSE):
VirtualBox VM 5.2.24 r128122 freebsd.amd64 (Jan 17 2019 06:38:52) release log
00:00:00.762785 OS Product: FreeBSD
00:00:00.762792 OS Version: FreeBSD 12.0-RELEASE-p2 GENERIC
00:00:00.762811 Package type: BSD_64BITS_GENERIC (OSE)
But this wasn't even a VirtualBox specific build/fork issue to begin with, this was a hardware issue:
00:00:00.954646 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!
And since the OP has figured it out, marking as [Resolved].
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply