[WorksForMe] Not reading 64bit processor type

[zera]

Hi, I am trying to setup Windows Server 2016 on my Ubutnu Server LTS 16 and I am having issues configuring everything. The windows installation file wont start. Can I please get a hand?
The server I am using is Dell R710 2U (2x Xeon E7540-QC-2.40GHz)

Code: Select all

File: \windows\system32\boot\windload.exe
Status: 0xc000035a
Info: This 64-bit application couldn’t load because your PC doesn’t have a 64-bit processor

My VM settings are below

Code: Select all

Name:            Server2016
Groups:          /
Guest OS:        Other Windows (64-bit)
UUID:            0a03ccf1-0e33-4f26-91f5-1f5acba07157
Config file:     /var/vbox/Server2016/Server2016.vbox
Snapshot folder: /var/vbox/Server2016/Snapshots
Log folder:      /var/vbox/Server2016/Logs
Hardware UUID:   0a03ccf1-0e33-4f26-91f5-1f5acba07157
Memory size:     1024MB
Page Fusion:     off
VRAM size:       8MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          off
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:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: None
State:           aborted (since 2018-08-25T00:18:53.596000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            Server2016_SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      30
Storage Controller Bootable (0):        on
Server2016_SATA (0, 0): /home/zera/junk/WindowsServer.iso (UUID: 2956ea0f-0fcf-4f3f-a6e4-7b893c693fe4)
Server2016_SATA (1, 0): /var/box/Server2016.vdi (UUID: d812503d-b5fb-4b1b-bb80-829df7378e23)
NIC 1:           MAC: 080027766A1A, 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)
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:            enabled (Address 0.0.0.0, Ports 5001, MultiConn: off, ReuseSingleConn: off, Authentication type: external)
Video redirection: disabled
VRDE property: TCP/Ports  = "5001"
VRDE property: TCP/Address = <not set>
USB:             disabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

Video capturing:    not active
Capture screens:    0
Capture file:       /var/vbox/Server2016/Server2016.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB

[andyp73]

Can I please get a hand?

The VBox.log file from you attempt at installing Windows Server 2016 may be enlightening. With the guest shutdown, right-click on the guest in VirtualBox Manager and select "Show log..." zip the first log file and post it here.

-Andy.

[zera]

Hi Andy, I am not using a desktop environment, but I have attached the first log file in the Log directory of my server.
Thanks

[socratis]

VirtualBox VM 5.1.38_Ubuntu r122592 linux.amd64 (Jul 10 2018 10:40:22) release log

It looks like you're using the distro's fork version of VirtualBox, and a rather old one, 5.1.x is not supported. You can either ask in their forums for help, or completely remove/uninstall/delete/purge their version and install the official version from the Downloads section of VirtualBox.

You can even add VirtualBox as a repository, so you could use your traditional install/upgrade/uninstall tools.

00:00:02.687098 Guest OS type: 'WindowsNT_64'

You've selected "Other Windows (64-bit)" as your guest version. You should change it to "Windows 2016 (64-bit)", that's what you're trying to install, isn't it?

00:00:02.692566 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.

But, that's your biggest problem. Apparently your CPU isn't capable enough to do what you want. What's the output of:

• 
  VBoxManage list hostinfo

[zera]

Thats a great amount of help thanks. Ill install the official one now, wasn't aware of the previous version. Also, I changed WindowsNT after trying Other Windows (64) to see if it would fix anything. Will update once I've setup the proper version.

---------------------------------------------------
Edit: I reinstalled it using the correct installation. I created a new VM but I cant seem to power it on.

Code: Select all

Waiting for VM "WindowsServer" to power on...
VBoxManage: error: The virtual machine 'WindowsServer' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

VMInfo

Code: Select all

zera@home:~$ sudo VBoxManage showvminfo WindowsServer
Name:            WindowsServer
Groups:          /
Guest OS:        Windows 2016 (64-bit)
UUID:            68e8fa5d-7993-4469-aa2a-779b8364898d
Config file:     /var/wbox/WindowsServer/WindowsServer.vbox
Snapshot folder: /var/wbox/WindowsServer/Snapshots
Log folder:      /var/wbox/WindowsServer/Logs
Hardware UUID:   68e8fa5d-7993-4469-aa2a-779b8364898d
Memory size:     2048MB
Page Fusion:     off
VRAM size:       8MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          off
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:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: None
State:           powered off (since 2018-08-26T21:43:23.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            WindowsServer_SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      30
Storage Controller Bootable (0):        on
WindowsServer_SATA (0, 0): /home/zera/junk/WindowsServer.iso (UUID: 2956ea0f-0fcf-4f3f-a6e4-7b893c693fe4)
WindowsServer_SATA (1, 0): /var/wbox/WindowsServer.vdi (UUID: 16ce58f4-f1b1-42b4-afce-65335694a9e0)
NIC 1:           MAC: 080027240E4D, 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 5001, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
Video redirection: disabled
USB:             disabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

Capturing:          not active
Capture audio:      not active
Capture screens:    0
Capture file:       /var/wbox/WindowsServer/WindowsServer.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25
Capture options:

Guest:

Configured memory balloon size:      0 MB

And my directory for the VM

Code: Select all

zera@home:~$ sudo tree /var/wbox
/var/wbox
├── WindowsServer
│   ├── WindowsServer.vbox
│   └── WindowsServer.vbox-prev
└── WindowsServer.vdi

1 directory, 3 files

[zera]

Ok disregard my last post I fixed that issue by reinstalling again. I am having issues connecting to the vdre. Last time I did it I was able to open VNC viewer and connect the the port. I chose port 5001. It just stays stuck at connecting on my client. No output on the Headless

My output:

Code: Select all

Oracle VM VirtualBox Headless Interface 5.2.18
(C) 2008-2018 Oracle Corporation
All rights reserved.

VRDE server is listening on port 5001.

Here is my settings

Code: Select all

Name:            WS
Groups:          /
Guest OS:        Windows 2016 (64-bit)
UUID:            63ccd519-a7e1-4c3a-aa0b-5d0d3a86b112
Config file:     /var/vbox/WS/WS.vbox
Snapshot folder: /var/vbox/WS/Snapshots
Log folder:      /var/vbox/WS/Logs
Hardware UUID:   63ccd519-a7e1-4c3a-aa0b-5d0d3a86b112
Memory size:     2048MB
Page Fusion:     off
VRAM size:       8MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          off
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:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: None
State:           powered off (since 2018-08-26T23:32:54.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            WS_SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      30
Storage Controller Bootable (0):        on
WS_SATA (0, 0): /home/zera/junk/WindowsServer.iso (UUID: 2956ea0f-0fcf-4f3f-a6e4-7b893c693fe4)
WS_SATA (1, 0): /var/vbox/WS.vdi (UUID: 45638d0f-58c9-416d-b629-d37b205d8a0b)
NIC 1:           MAC: 08002781ADE2, 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 5001, MultiConn: off, ReuseSingleConn: off, Authentication type: external)
Video redirection: disabled
VRDE property: TCP/Ports  = "5001"
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>
USB:             disabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

Capturing:          not active
Capture audio:      not active
Capture screens:    0
Capture file:       /var/vbox/WS/WS.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25
Capture options:

Guest:

Configured memory balloon size:      0 MB

[socratis]

Are you actually on a headless server, or are you doing this as an exercise? Because if you are on a headless, you started from a dive in the deep waters...

As for my hostinfo output: <random_site>

Please edit your message, delete the link, replace it with the actual text. We shouldn't be going hunting on 3rd party sites, to see a picture, when a nice copy/paste would do a 1000-fold better job. In this case a few words are worth 1000 pictures...

I created a new VM but I cant seem to power it on. I used <random_blog>

Why? Do you have something against the User Manual? First of all, are you actually on a headless server? I would first try to do a "normal" installation, familiarize myself with the software and the terminology, and then go for the advanced, command-line VM creation. But, if you insist, read 7.1.3 Step by step: creating a virtual machine on a headless server from the User Manual.

My output:

Always include your "input" with your output, so that we have a better picture.

I chose port 5001.

Why?

Config file:     /var/vbox/

Why? Just because the blog said so? At least it didn't say '/root/vbox'...


PS. You don't have to include the "showvminfo" every time, only if asked. The VBox.log is a more important piece of information, but it's not needed yet.

Edit: Why have we moved to the RDP server? Your problem does not match your thread's title. For RDP problems open a new thread with an appropriate title. 1 issue per thread, 1 thread per issue.

[zera]

I am using a headless server. I've worked with VM's before but always with a GUI. I will reset a new virtual machine using the steps and create a post if I still have the VRDE issues. I will also update this thread if I have the issue I originally posted.

[socratis]

I will reset a new virtual machine using the steps and create a post if I still have the VRDE issues.

Just to "reset" things... The title of the thread has nothing to do with RDP, it's called "Not reading 64bit processor type". Has this been resolved? If yes (at least that's my understanding from the "Windows 2016 (64-bit)" guest), we can mark the thread as [Solved] and then you could open a new thread specifically about your RDP issue.

One thread per issue, one issue per thread, preferably matching the thread's title...

[zera]

I am still having this issue:

File: \windows\system32\boot\windload.exe
Status: 0xc000035a
Info: This 64-bit application couldn’t load because your PC doesn’t have a 64-bit processor

Any suggestions on what I can try? Let me know if I need to attach files.

[socratis]

1) I'm still waiting from the "VBoxManage list hostinfo".
2) I have no clue what winload is or is not. It's not a VirtualBox related program.

[zera]

1) I'm still waiting from the "VBoxManage list hostinfo".
2) I have no clue what winload is or is not. It's not a VirtualBox related program.

Here is my hostinfo

Code: Select all

Host Information:

Host time: 2018-09-01T00:51:27.936000000Z
Processor online count: 16
Processor count: 16
Processor online core count: 8
Processor core count: 8
Processor supports HW virtualization: no
Processor supports PAE: yes
Processor supports long mode: yes
Processor supports nested paging: no
Processor#0 speed: 2395 MHz
Processor#0 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#1 speed: 2395 MHz
Processor#1 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#2 speed: 2395 MHz
Processor#2 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#3 speed: 2395 MHz
Processor#3 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#4 speed: 2395 MHz
Processor#4 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#5 speed: 2395 MHz
Processor#5 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#6 speed: 2395 MHz
Processor#6 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#7 speed: 2395 MHz
Processor#7 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#8 speed: 2395 MHz
Processor#8 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#9 speed: 2395 MHz
Processor#9 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#10 speed: 2395 MHz
Processor#10 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#11 speed: 2395 MHz
Processor#11 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#12 speed: 2395 MHz
Processor#12 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#13 speed: 2395 MHz
Processor#13 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#14 speed: 2395 MHz
Processor#14 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Processor#15 speed: 2395 MHz
Processor#15 description: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
Memory size: 7963 MByte
Memory available: 6342 MByte
Operating system: Linux
Operating system version: 4.4.0-134-generic

[zera]

I answered myself in that command wow. Mark as resolved

[socratis]

If anything, I'll mark this as [Puzzling]...

Processor supports HW virtualization: no
Processor#0 description: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz

Your Xeon E5620 definitely supports virtualization, so I don't know why VirtualBox says that it doesn't. Something not right here...

File: \windows\system32\boot\windload.exe

I answered myself in that command wow.

I looked for "\windows\system32\boot\windload.exe" and apparently you had an extra "d" in there. I don't know what you were trying to do (honestly), or why that command was even an issue.

I'll mark this as [WorksForMe] since 1) the problem is really fuzzy, not well defined, and 2) you mentioned that whatever the problem was, you managed to fix it.

[mpack]

If anything, I'll mark this as [Puzzling]...

Processor supports HW virtualization: no
Processor#0 description: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz

Your Xeon E5620 definitely supports virtualization, so I don't know why VirtualBox says that it doesn't. Something not right here...

The OP seems to be conspiring to provide the minimum information possible (e.g. a 63 line log file), but my guess would be that the host is a VM of some sort. Xen perhaps.