[Solved] Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
[Solved] Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
First of all, sorry for my bad English.
A month ago I got my first server (secondhand R710) and It is just for home use.
After Updating the bios and some other things, i Installed Ubuntu server as its main OS as it was the most suitable.
Although Ubuntu server is enough for most of my needs, I still need some applications that have a UI.
After installing Virtualbox I tried installing Windows 10, Windows 8, and Ubuntu. (https://www.virtualbox.org/manual/ch08.html) <- I increased --memory to 16384 and increased the storage from 10000 to 75000.
They all didn't work and surprisingly enough the all gave me a different error.
Windows 10: 0xc0000225
Windows 8 : 0xc000035a
and Ubuntu just gave me nothing more than a corrupted screen.
While trying to solve these issues I changed different things,
Enable Virtualization in Bios
change vm settings:
APIC on
IOAPIC on
apci on
nested paging on
vtx(something) on
but none of this worked.
I hope anyone knows any possible solution to get one of these vms to run.
Thanks already
A month ago I got my first server (secondhand R710) and It is just for home use.
After Updating the bios and some other things, i Installed Ubuntu server as its main OS as it was the most suitable.
Although Ubuntu server is enough for most of my needs, I still need some applications that have a UI.
After installing Virtualbox I tried installing Windows 10, Windows 8, and Ubuntu. (https://www.virtualbox.org/manual/ch08.html) <- I increased --memory to 16384 and increased the storage from 10000 to 75000.
They all didn't work and surprisingly enough the all gave me a different error.
Windows 10: 0xc0000225
Windows 8 : 0xc000035a
and Ubuntu just gave me nothing more than a corrupted screen.
While trying to solve these issues I changed different things,
Enable Virtualization in Bios
change vm settings:
APIC on
IOAPIC on
apci on
nested paging on
vtx(something) on
but none of this worked.
I hope anyone knows any possible solution to get one of these vms to run.
Thanks already
Last edited by socratis on 13. Jan 2019, 22:36, edited 1 time in total.
Reason: Marked as [Solved].
Reason: Marked as [Solved].
-
- Site Moderator
- Posts: 27329
- 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: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Pick one VM only. We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
- Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
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.
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.
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
I am trying this on a machine running Ubuntu server (No GUI) so I can't send you the VBox.log because I can't right click on anything because it has no GUI.
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Go to the directory containing the guest (~/VirtualBox VMs/...) and within there is a "Logs" directory where the VBox.log file can be found.
-Andy.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Thank you Andy, This is the first log file on the Windows 8 Guest which gives the 0xc000035a blue screen error.
- Attachments
-
- VBox.rar
- (14.39 KiB) Downloaded 14 times
-
- Site Moderator
- Posts: 27329
- 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: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Please create a new Win8.1 VM. Stick with the proposed defaults, do not change or deviate from them at a first pass. Try then...
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.
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.
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Do you mean https://www.virtualbox.org/manual/ch08.html as proposed defaults?
-
- Site Moderator
- Posts: 27329
- 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: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
I'm so sorry, I completely missed the fact that you're running this on a CLI-only host, so there's no "defaults" for you!Ruud14 wrote:I am trying this on a machine running Ubuntu server (No GUI
That means that you're creating the VM "by hand", with a series of VBoxManage commands, right? Do you have the "script" that you use to create the VM? Post it, either inline or as an attachment, and I'll take a look at it and see what's different from the defaults. To give you an idea, here's what a newly created VM has for a Win8.1:
Code: Select all
C:\Users\Socratis>VBoxManage showvminfo Ruud14
Name: Ruud14
Groups: /
Guest OS: Windows 8.1 (64-bit)
UUID: 81f33468-55e3-40d1-aa08-52afaf6d1adf
Config file: C:\Users\Public\VirtualBoxVMs\Ruud14\Ruud14.vbox
Snapshot folder: C:\Users\Public\VirtualBoxVMs\Ruud14\Snapshots
Log folder: C:\Users\Public\VirtualBoxVMs\Ruud14\Logs
Hardware UUID: 81f33468-55e3-40d1-aa08-52afaf6d1adf
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: disabled
VT-x VPID: enabled
VT-x unr. exec.: enabled
Paravirt. Provider: Default
Effective Paravirt. Prov.: HyperV
State: powered off (since 2019-01-12T08:04:35.104000000)
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): C:\Users\Public\VirtualBoxVMs\Ruud14\Ruud14.vdi (UUID: 47fa7fab-c22c-481a-89fe-0994502f43a6)
SATA (1, 0): Empty
NIC 1: MAC: 080027ACABBC, 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: DSOUND, Controller: HDA, Codec: STAC9221)
Audio playback: disabled
Audio capture: enabled
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: 0
Capture file: C:\Users\Public\VirtualBoxVMs\Ruud14\Ruud14.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.
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.
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
This is as close as I can get to what I entered when I created the vm:
and this is what my 'VBoxManage showvminfo "Windows8" ' looks like:
Code: Select all
VBoxManage createvm --name "Windows8" --ostype Windows81_64 --register
VBoxManage modifyvm "Windows8" --memory 16384 --acpi on --boot1 dvd --nic1 nat
VBoxManage createhd --filename "Windows8.vdi" --size 75000
VBoxManage storagectl "Windows8" --name "IDE Controller" --add ide --controller PIIX4
VBoxManage storageattach "Windows8" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "Windows8.vdi"
VBoxManage storageattach "Windows8" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium Win8.1_SingleLang_EnglishInternational_x64.iso
VBoxManage modifyvm "Windows8" --vrde on
VBoxManage modifyvm "Windows8" --apic on
VBoxManage modifyvm "Windows8" --ioapic on
VBoxHeadless --startvm "Windows8"
Code: Select all
Name: Windows8
Groups: /
Guest OS: Windows 8.1 (64-bit)
UUID: ffc810e9-368d-4936-ae6f-afc5636e7be8
Config file: /home/ruud/VirtualBox VMs/Windows8/Windows8.vbox
Snapshot folder: /home/ruud/VirtualBox VMs/Windows8/Snapshots
Log folder: /home/ruud/VirtualBox VMs/Windows8/Logs
Hardware UUID: ffc810e9-368d-4936-ae6f-afc5636e7be8
Memory size 16384MB
Page Fusion: disabled
VRAM size: 8MB
CPU exec cap: 100%
HPET: disabled
CPUProfile: host
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
PAE: enabled
Long Mode: disabled
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: DVD
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: disabled
VT-x VPID: enabled
VT-x unr. exec.: enabled
Paravirt. Provider: Default
Effective Paravirt. Prov.: HyperV
State: aborted (since 2019-01-11T15:26:21.000000000)
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): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
IDE Controller (0, 0): /home/ruud/Windows8.vdi (UUID: 2cc3a7e5-d53a-4c5b-8dc3-94ccebe7294e)
IDE Controller (0, 1): /home/ruud/Win8.1_SingleLang_EnglishInternational_x64.iso (UUID: c0e75d9f-be3e-4bce-8c8f-8ae244966514)
NIC 1: MAC: 08002758AE8F, 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: PS/2 Mouse
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: ALSA, Controller: AC97, Codec: STAC9700)
Audio playback: disabled
Audio capture: disabled
Clipboard Mode: disabled
Drag and drop Mode: disabled
VRDE: enabled (Address 0.0.0.0, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
Video redirection: disabled
VRDE property : TCP/Ports = "3389"
VRDE property : TCP/Address = <not set>
VRDE property : VideoChannel/Enabled = <not set>
VRDE property : VideoChannel/Quality = <not set>
VRDE property : VideoChannel/DownscaleProtection = <not set>
VRDE property : Client/DisableDisplay = <not set>
VRDE property : Client/DisableInput = <not set>
VRDE property : Client/DisableAudio = <not set>
VRDE property : Client/DisableUSB = <not set>
VRDE property : Client/DisableClipboard = <not set>
VRDE property : Client/DisableUpstreamAudio = <not set>
VRDE property : Client/DisableRDPDR = <not set>
VRDE property : H3DRedirect/Enabled = <not set>
VRDE property : Security/Method = <not set>
VRDE property : Security/ServerCertificate = <not set>
VRDE property : Security/ServerPrivateKey = <not set>
VRDE property : Security/CACertificate = <not set>
VRDE property : Audio/RateCorrectionMode = <not set>
VRDE property : Audio/LogPath = <not set>
OHCI USB: disabled
EHCI USB: disabled
xHCI USB: disabled
USB Device Filters:
<none>
Bandwidth groups: <none>
Shared folders:<none>
Capturing: not active
Capture audio: not active
Capture screens: 0
Capture file: /home/ruud/VirtualBox VMs/Windows8/Windows8.webm
Capture dimensions: 1024x768
Capture rate: 512kbps
Capture FPS: 25kbps
Capture options:
Guest:
Configured memory balloon size: 0MB
-
- Site Moderator
- Posts: 27329
- 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: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
I want you to add a couple more VBoxManage commands to your script. I separated each "modifyvm" command on it's own line, you can see easier what's going on...
[quote] VBoxManage createvm --name "Windows8" --ostype Windows81_64 --register VBoxManage modifyvm "Windows8" --memory 16384 VBoxManage modifyvm "Windows8" --acpi on VBoxManage modifyvm "Windows8" --boot1 dvd VBoxManage modifyvm "Windows8" --boot2 disk VBoxManage modifyvm "Windows8" --boot3 none VBoxManage modifyvm "Windows8" --nic1 nat VBoxManage modifyvm "Windows8" --vrde on VBoxManage modifyvm "Windows8" --apic on VBoxManage modifyvm "Windows8" --ioapic on VBoxManage modifyvm "Windows8" --longmode on VBoxManage modifyvm "Windows8" --vram 128 VBoxManage modifyvm "Windows8" --accelerate3d on VBoxManage modifyvm "Windows8" --accelerate2dvideo on VBoxManage modifyvm "Windows8" --usbxhci on VBoxManage modifyvm "Windows8" --mouse usbtablet VBoxManage createhd --filename "Windows8.vdi" --size 75000 VBoxManage storagectl "Windows8" --name "IDE Controller" --add ide --controller PIIX4 VBoxManage storageattach "Windows8" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "Windows8.vdi" VBoxManage storageattach "Windows8" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium Win8.1_SingleLang_EnglishInternational_x64.iso[/quote]The bold-underlined are the additional commands.
- Besides setting the DVD as your first boot device, set the HD as your 2nd option, and empty the 3rd one. It doesn't "look" right.
- The longmode is the one I think that's going to make the whole thing sing.
- The default for the VRAM of a new VM is 8 MB, not even enough to boot DOS (just kidding).
- 2D/3D acceleration never hurt anyone...
- If you have the Extension Pack installed, enable USB3 (xHCI) and a USB Tablet, instead of the default PS/2 mouse.
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.
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.
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Thank you Socratis.
I First tried adding the lines you mentioned to the existing Windows8 VM.
When using 'VBoxHeadless --startvm "Windows8" ' This gave the error: "Segmentation fault (core dumped)"
So I tried deleting the "Windows8" VM, reboot, and create a new Windows8 vm with the command order you mentioned.
This Still gave me the "Segmentation fault (core dumped)" error when trying to start the VM.
Finally I tried creating a Windows10 VM using the commands you mentioned but It still gives me the "Segmentation fault (core dumped)" error when trying to start the VM.
I Think one of the commands you added causes this error but I don't know which one
I First tried adding the lines you mentioned to the existing Windows8 VM.
When using 'VBoxHeadless --startvm "Windows8" ' This gave the error: "Segmentation fault (core dumped)"
So I tried deleting the "Windows8" VM, reboot, and create a new Windows8 vm with the command order you mentioned.
This Still gave me the "Segmentation fault (core dumped)" error when trying to start the VM.
Finally I tried creating a Windows10 VM using the commands you mentioned but It still gives me the "Segmentation fault (core dumped)" error when trying to start the VM.
I Think one of the commands you added causes this error but I don't know which one
-
- 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: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
As this is a text mode server without a GUI and the VMs will be started headless I'm not sure if the 2D/3D support works as usual.
Could you try again with these two lines set to "off"?
Could you try again with these two lines set to "off"?
Re: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Thank so you Martin and Socratis, It is working now.
Disabling the 2D/3D support fixed the "Segmentation fault (core dumped)" error.
Thank you both so much
Disabling the 2D/3D support fixed the "Segmentation fault (core dumped)" error.
Thank you both so much
-
- Site Moderator
- Posts: 27329
- 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: Can't get any 64-bit OS to run as guest on Ubuntu server 18.04.1
Martin wrote:without a GUI and the VMs will be started headless I'm not sure if the 2D/3D support works as usual
D'oh! I completely forgot about that condition!Ruud14 wrote:Disabling the 2D/3D support fixed the "Segmentation fault (core dumped)" error.
Thanks Martin for remembering and saving the day... Still, I think somehow that there should be a more "grateful" way to exit/quit, for those that don't know, or remember those little details.
Marking as [Solved].
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.
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.