Page 1 of 1

[Solved] Windows 10 nativ and raw guest no longer boots as nativ

Posted: 28. Oct 2018, 10:44
by jibbel
Hello,

i used to have windows 7 on my laptop with opensuse. I could run windows 7 native and in a virtualbox with the raw disk image.
I upgraded now to windows 10. But if I started Windows 10 once in Virtualbox and installed the guest additions i can no longer start windows native. Windows always wants to start the repair tool. But starting in VirtualBox is still always fine. Maybe i should mention that i have some problems with displaying in the correct resolution, since i have a 4K display.

Host:
UHD Display 4K
Nvidia GTX 1070
16GB RAM
Intel 8200K 12 Core
Samsung EVO 970 500GB Nvme
uname -a
4.12.14-lp150.12.22-default #1 SMP Sat Oct 13 05:05:16 UTC 2018 (09415e8) x86_64 x86_64 x86_64 GNU/Linux

VirtualBox -h
Oracle VM VirtualBox Manager 5.2.18_SUSE
Guest:
Windows 10 with Guest additions 5.2.18 installed
Samsung SSD 970 Evo 500GB
Shared Folder and drag and drop is deaktivated
8 GB RAM
6 Core
Chipset PIIX3
PS/2 Mouse
Boot order only SDD and optical with AHCI
IO-APIC and EFI are aktivated
parallisation is predefined
vt-x and nesting paging is aktivated
graphic card is set to 256MB with 3D and 2D aktivated
remote controll and recording is deaktivated
Audio, usb and seriell are disabled

please help me
thank you

Re: Windows 10 nativ and raw guest no longer boots as nativ

Posted: 3. Nov 2018, 17:32
by jibbel
hello,

does nobody have the same problem like me?
I turned now secureboot off, and i will reinstall windows 10 maybe this will help.

i will post further information here

jibbel

Re: Windows 10 nativ and raw guest no longer boots as nativ

Posted: 8. Nov 2018, 10:10
by jibbel
Hello,

the solution is the following:

1, Disable Secureboot and intel rapid technology
2. Install Linux
3. Create physical vmdk
4. install windows on physical drive from virtual box
5. install guest additions
6. boot windows
7. install windows driver

Re: Windows 10 nativ and raw guest no longer boots as nativ

Posted: 8. Nov 2018, 10:36
by socratis
jibbel,
It's not that nobody wanted to offer any advice, it's that 1) your setup is not common, 2) due to the intrinsic danger of using rawdisk access on partitions, a lot of people (including yours truly) will steer away of giving potentially dangerous advice.

So, in the end you had to re-install the whole thing from scratch? That sounds like the ultimate "nuke the whole thing" workaround! ;)

One remark that I have is that you are using the SUSE fork of VirtualBox, not the official one:
jibbel wrote:
Oracle VM VirtualBox Manager 5.2.18_SUSE
You should completely remove/uninstall/delete/purge their version and install the official version from the Linux Downloads section of VirtualBox.

Thanks for the feedback and for your solution. Marking as [Solved].