Solaris VM will not boot

[Titan-69]

I copied the virtualbox harddrive file containing solaris 10 from an older pc to the new server running windows server 2022. I added the harddisk to the virtualbox on the new server and when I try to boot it just keeps looping.
As a test, I downloaded the solaris 10 virtualbox template from oracle and imported it on the new machine into virtualbox. I tried booting it up and it does the same thing, it just keeps looping and flashing some text and rebooting. I was able to capture the text and I attached the picture along with the vb log file of the machine. I have tried setting it to 1 cpu, tried different memory amounts from 4gb to 8gb.
I have verified the hyper-v is disabled.
I also download the solaris 10 iso dvd and tried to install solaris and as soon as it boots it restarts as well.

[mpack]

Howto: Move a VM.

[Titan-69]

Thanks for the info, I did do the manual move and it had the same behavior.
I don't think it has anything to do with the movement of the VM as I am not even able to boot the template from oracle or even install solaris 10 from the dvd iso.
It almost seems like there is something on the server. I looked through the logs and the only error that I see is the following:
ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

I see that error 3 times in the log.

[paulson]

I copied the virtualbox harddrive file containing solaris 10 from an older pc to the new server running windows server 2022.

I suspect that this is a case of the host CPU being too new for the guest OS. The VBox.log file shows
the host CPU is:

Code: Select all

00:00:05.090539 Full Name:                       "Intel(R) Xeon(R) Silver 4314 CPU @ 2.40GHz"

which https://www.cpu-world.com/CPUs/Xeon/Int ... 04314.html shows is part of
the Ice Lake family. I don't think Solaris 10 supports Intel CPUs beyond the Haswell microarchitecture.
What you can try is to change which CPU capabilities from the host are presented to the guest using:

Code: Select all

$ VBoxManage modifyvm <VM name> --cpu-profile ...

To see the list of CPU profiles you can run the following command:

Code: Select all

$ VBoxManage list cpu-profiles

Another forum user created the following table showing further details
about some of the CPU profiles:

Code: Select all

CPU                   Date     Class      Family
--------------------------------------------------------
Xeon X5482 3.20GHz    Q4'07    Server     Harpertown
Core i7-2635QM        Q1'11    Mobile     Sandy Bridge
Core i7-3960X         Q4'11    Desktop    Sandy Bridge E
Core i5-3570          Q2'12    Desktop    Ivy Bridge
Core i7-5600U         Q1'15    Mobile     Broadwell
Core i7-6700K         Q3'15    Desktop    Skylake

So thus maybe give the Ivy Bridge profile a try using the following:

Code: Select all

$ VBoxManage VBoxManage modifyvm Solaris10_1-13 --cpu-profile "Intel Core i5-3570"

to see if that helps. If that doesn't work try the Sandy Bridge ones next.

The following errors in the VBox.log file:

ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

are harmless.

[Titan-69]

Thanks for the info.
The cpu was the problem. It was keeping the install from running as well.
I had to use the sandy bridge to get it up and going.
Thanks again.