![]() ![]() It was set to GPT instead of MBR so I enabled UEFI again in the BIOS to be able to install Windows on it and boot from it. I then decided to re-install my harddisc that came with the system. No more green turtle! I had to disable UEFI in the BIOS and set things to Legacy support to make things work. When I booted from this new installation, systeminfo.exe was displaying the correct hypervisor information and Virtualbox was working correctly on my HP Z440. I was able to re-install Windows 10 on a spare disc that had a MBR partition. If I ever find out what service/app/process is acting as a hypervisor that is causing the problem I will post another reply. When I bought this Workstation I had in mind to use it for virtualization work, so it's a pitty it's not working. My laptop is company managed so it's a little behind with updates, but when my laptop is updated to 20H2 and it breaks Virtualbox, I'll let you know.įor now I can use my laptop as a workaround. got some new updates today it's now build 19042.844. The only real difference is that my laptop has version 1909 of Windows 10 Pro and my workstation has 20H2. On my Workstation I installed LibreOffice, but I can't imagine that is causing the issue. I did have Visual Studio and Node.JS with some plugins for Angular, so I did uninstall those and visual studio completely, But that did not make any difference.įor the rest almost all software I use on my workstation is also on my Laptop and on my laptop Virtualbox is working without problems. Hi, I did the procedure again followed by a 'shutdown -s -t 2' but the green turtle is still there. When I check this setting after shutdown with command dcdedit it still says it is off: Yes, the system was completely shutdown several times. Working on HP Laptop.zip Working on HP laptop Logs (72.14 KiB) Downloaded 4 times NOT Working on HP Workstation Logs.zip Not working HP Workstation logs (67.61 KiB) Downloaded 5 timesī1tm4p75 wrote:I also altered the Windows boot loader with the command: bcdedit /set hypervisorlaunchtype offĭid you make sure that you did a complete shutdown / reboot? (disable fast startup or hold shift key while clicking 'reboot' on the Start menu) If there is someone who has a Quadro M4000 that runs Linux VM's without issues, please let me know. I hope anyone can spot something in the logfiles that I overlooked. It's running with the latest drivers v457.9 Worth to mention: I'm using the latest virtualbox version, My Z440 has a Nvidia Quadro M4000, and I suspect that might have something to do with it. So, my question, why is it working on my laptop, but not on my workstation? I attached the log files of both the working and the not working environments. I created the Kali VM with default settings just like I did on my workstation and there it boots like a charm! ova file to my HP omnibook laptop and installed Virtualbox there. ![]() I then installed Fedora 33 to see if another Linux version would work, but there the same issue appears, blank screen with blinking underscore. Turns out that I can run Windows 7 and Windows 10 VM's without problems. Than I came up with the idea to create other Windows and Linux VM's on my Z440 to see if that would work. ![]() Ofcourse I searched this forum and tried all suggestions. It loads Grub and then I see the menu where I can choose Kali GNU/Linux, when I make my choice, (or wait for timeout) the screen turns black with a blinking underscore and next nothing happens. To my surprise this Linux version is not booting on my new HP Z440 Workstation. On my old Workstation I had Virtualbox running and without problems I could work with the Kali Linux. I want to use this workstation mostly for virtualization, so it's a bit sad that I now can't get thing to work. So last week I bought a 'new' refurbished HP Workstation Z440 with 10 cores and 32 Gb memory after my old Dell T5400 Workstation died. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |