Fedora Server 30 with Windows Server 2019 Guest Bluescreen

Discussions related to using VirtualBox on Linux hosts.
Post Reply
COM8
Posts: 2
Joined: 5. Sep 2019, 17:40

Fedora Server 30 with Windows Server 2019 Guest Bluescreen

Post by COM8 »

I want to switched from a Debian 9 host with Windows Server 2016 as guest to a Fedora 30 Server with a Windows Server 2019 guest.

The problem:
When I try to install Windows Server 2019 the installation progress fails at a random point with a bluescreen.
The VM runs without any problems if you just wait at the install menu. But as soon as I start the process I can be sure I will see a bluescreen in the next 5 minutes.

My setup:
  • CPU: i5-4210H
  • RAM: 8 GB
  • OS (Host): Fedora Server 30
  • OS (Guest): Windows Server 2019

Code: Select all

VBoxManage createvm --name "WindowsServer2019" --ostype  Windows2016_64 --register
VBoxManage modifyvm "WindowsServer2019" --memory 4096 --cpus 2 --acpi on --boot1 dvd --nic1 nat
VBoxManage createhd --filename "WinServer2019.vdi" --size 100000
VBoxManage storagectl "WindowsServer2019" --name "IDE Controller" --add ide --controller PIIX4
VBoxManage storageattach "WindowsServer2019" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "WinServer2019.vdi"
VBoxManage storageattach "WindowsServer2019" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium /root/wServer.iso
VBoxManage modifyvm "WindowsServer2019" --vrde on
What I have tried:
* Switching between VBox versions:
  • VirtualBox-5.2-5.2.32_132073_fedora29-1.x86_64
  • VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64
* Switching between Windows Server 2019 builds
* Searching in VBox logs for obvious errors/warnings

I've included 2 bugreport archives and how can I fix this?
Attachments
2019-09-05-15-12-00-bugreport.tgz
(5.38 KiB) Downloaded 10 times
2019-09-01-14-43-21-bugreport.tgz
(6.62 KiB) Downloaded 10 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Fedora Server 30 with Windows Server 2019 Guest Bluescreen

Post by socratis »

In order for the VBoxBugReport to be useful (one of them, don't need two BTW), you need to include the VM name, i.e.:
  • VBoxBugReport "WindowsServer2019.vbox"
00:00:00.000835 main VirtualBox XPCOM Server 6.0.10 r132072 linux.amd64 (Jul 12 2019 11:20:18) release log
6.0.12 is out, you might want to upgrade.

What I usually do when I want to replicate a VM with the use of VBoxManage and the CLI alone ("<VM1>"), I first create a VM using the GUI ("<VM2>"), and then compare the output of:
  • VBoxManage showvminfo "<VM1>"
    VBoxManage showvminfo "<VM2>"
If they don't match, I make the appropriate adjustments to the VM1 creation script. Here's what a default Win2016-64 should look like:

Code: Select all

$ VBoxManage showvminfo Win2019
Name:                        Win2019
Groups:                      /
Guest OS:                    Windows 2016 (64-bit)
UUID:                        db30d520-6acd-4152-8f60-90d188dd0952
Config file:                 /Users/Shared/VirtualBox/Machines/Win2019/Win2019.vbox
Snapshot folder:             /Users/Shared/VirtualBox/Machines/Win2019/Snapshots
Log folder:                  /Users/Shared/VirtualBox/Machines/Win2019/Logs
Hardware UUID:               db30d520-6acd-4152-8f60-90d188dd0952
Memory size                  2048MB
Page Fusion:                 disabled
VRAM size:                   128MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              1
PAE:                         disabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      disabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               Floppy
Boot Device 2:               DVD
Boot Device 3:               HardDisk
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         local time
Hardw. virt.ext:             enabled
Nested Paging:               enabled
Large Pages:                 enabled
VT-x VPID:                   enabled
VT-x unr. exec.:             enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   None
State:                       powered off (since 2019-09-05T19:43:59.746000000)
Monitor count:               1
3D Acceleration:             disabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:          
Teleporter Password:         
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:       
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:            
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
SATA (0, 0): /Users/Shared/VirtualBox/Machines/Win2019/Win2019.vdi (UUID: 24889f3c-2c6f-4d8e-a7d4-61d4051f60bd)
SATA (1, 0): Empty
NIC 1:                       MAC: 0800277A4701, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:                       disabled
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
Pointing Device:             USB Tablet
Keyboard Device:             PS/2 Keyboard
UART 1:                      disabled
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       enabled (Driver: CoreAudio, Controller: HDA, Codec: STAC9221)
Audio playback:              enabled
Audio capture:               disabled
Clipboard Mode:              disabled
Drag and drop Mode:          disabled
VRDE:                        disabled
OHCI USB:                    disabled
EHCI USB:                    disabled
xHCI USB:                    enabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:<none>

Capturing:                   not active
Capture audio:               not active
Capture screens:             
Capture file:                /Users/Shared/VirtualBox/Machines/Win2019/Win2019.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:             

Guest:

Configured memory balloon size: 0MB
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.
COM8
Posts: 2
Joined: 5. Sep 2019, 17:40

Re: Fedora Server 30 with Windows Server 2019 Guest Bluescreen

Post by COM8 »

Ok thanks for your reply.
The following things I've tried without success:
  • Updated to 6.0.12
  • Created a Windows Server 2019 VM on my Fedora 30 Workstation notebook (worked) and compared&updated settings
I also created a new bug report.
Btw. I'm getting always a "SYSTEM SERVICE EXCEPTION" bluescreen.
Attachments
2019-09-06-13-12-48-bugreport.tgz
Output of VBoxBugReport "WindowsServer2019"
(36.5 KiB) Downloaded 9 times
Post Reply