Did you check whether...
- ...the file system of your Hyper-V VM is alright?
- ...the physical HDD or SSD disk where your Hyper-V VM is located is free of errors?
- ...there is enough free space on the partition or slice of the physical disk?
- ...the virtual disk's consistency is fine (by using Test-VHD on the host)?
I am not an Hyper-V expert, but as the errors occur at such an early step of booting your Solaris VM, they might be very well related to a an error relating the physical disk or the logical virtual disk and might be tracked down and solved by looking the your Windows VM host.
File system of vm is ok
The physical disk is of the hypervisor is ok
There is plenty of space on the partition
The Test-VHD has turned up "true", so disk is usable
The version of Solaris you are running (11.0) is quite old and unpatched. Do you have a specific reason for not upgrading to 11.4 (SRU 10)? Maybe -assuming that this was a bug- it has been fixed in the meantime...
What you could try to do:
- Have you tried to assign only one CPU core to your virtual machine?
- Have you tried to add "-v" to GRUB's boot menu entry (https://docs.oracle.com/cd/E26502_01/html/E28983/glyas.html? Do you see more output then?
- Have you tried to boot from a boot stick or boot CD/DVD and tried to import the ZFS zpool from there?
I've already tried with 1 vCPU, same result.
I've tried adding the -v to the GRUB's boot menu entry, it gives some additional info
But it seems like the same warnings/errors
As for booting from CD and import the ZFS zpool....I have no idea how to do that.
I know some basic Linux but have no experience with SolOS
I've read through several documents (https://docs.oracle.com/cd/E19253-01/819-5461/gjpna/index.html ) but I don't even see the failsafe mode in GRUB...
I did notice that the VHD of the VM is a dynamically expanding disk set to 40GB...and it did reach the size of 40GB. So maybe that's what's been giving the errors?
I expanded the disk on the hypervisor to 50GB but I have no idea how to expand it in SolOS pre-boot.
Documentation is very unclear.
I know what the problem is. It is not about a broken installation, but a Windows update, which is related to Hyper-V.
You probably have one of these update installed on the Hyper-V host. If you uninstall these, your virtual machine will boot properly.
That looks likely, I remember getting the same errors with 11.4 GA, having to use VirtualBox for my experiment.
Really? I was just about upgrading my Solaris 11.0 to 11.4, hoping it will survive Windows updates. :-(
Everything was fine until 3 months ago, HyperV host was up to date. Than a new Windows update screwed up everything.
I'll do a quick check on my computer (Windows 10 Enterprise 1903 18362.295) with 11.4.
This seems a bug at Microsoft's side, because it happens on all versions of Solaris.
This is 2019.04 OpenIndiana (illumos):
This is OpenSolaris build 134 (produces more errors later, as in the previous pictures; Solaris 10 Update 11 does the exact same output):
This is Solaris 9 (after this the \|/- symbol just spins and nothing happens):
This Solaris Device Configuration Assistant warning and the doubled IDE controller also may be of interest, although it is likely this is a different problem (Solaris 9 is older than Hyper-V, after all):
(note that I have only one IDE controller with a HD and CD/ROM that shows two times)
Edit: As you can see at the last picture at least on my setup the problematic device is the CD-ROM drive. Maybe (assuming you have the same setup) you could try to prevent the issue by removing it from the virtual machine (I can't try it, because I don't have any version of Solaris installed).
Edit 2: The first sentence is actually incorrect. Solaris 8 boots
I tried to remove the virtual DVDROM from my Solaris 11.1, but the problem is the same.
I'd like to keep my Hyper-V hosts updated, so I need some solution. I found out to create a Windows 2016 VM on my Windows 2016 host, make a nested virtualization, so the Solaris could run under a virtual Windows 2016 hyperv server. In this case I can keep my physical host servers updated.
Ah, I see, it is probably the IDE controller itself rather than the DVD-ROM. At this point I would try to contact Microsoft since the problem is probably on their side considering all versions from Solaris 9 to 11.4 have this problem (the question obviously is whether they would help you at all, since Solaris is not supported on Hyper-V).
Hi, somebody find solution?