See the attached pictures for the information.
Created attachment 174951 [details] hyperv-fail0
Created attachment 174952 [details] hyperv-fail1
Created attachment 174953 [details] hyperv-fail2
Created attachment 174954 [details] hostinfo
Created attachment 174955 [details] exported hyperv machine
How to reproduce: * choose a V2 version of new Hyper-V VM * insert an installer built from latest 10-STABLE (2016.06.19.) or a 11.0-RC3 * boot it * it's failed with a lost installer medium * then it's spam the console with vm_pager related broken panic messages
It would be really nice to generate a new 10-STABLE snapshot officially too.
Try turning off Secure Boot in the VM Security settings.
Actually, no, this isn't the problem. The installer is being detached during boot, which is what is causing the vm_pager() console spam.
Use gen1 VM, gen2 VM is not really supported yet.
Sure, with V1 working better, but there are still some issues. See the newly attached screenshot.
Created attachment 174989 [details] hyperv-warn1
This was at the end of the installer, when it shuts down.
Hongjiang, Dexuan, please help check the host info and configure. I never hit the the last warning.
(In reply to Sepherosa Ziehau from comment #14) I installed 10.3 (FreeBSD-10.3-RELEASE-amd64-dvd1.iso) on my Win10 last week. My VM worked fine without the issue in Comment 12.
I installed FreeBSD11 RC3 on my windows 10 Enterprise, and I did not see that warning. Could you please check whether your windows 10 version?
Created attachment 174992 [details] systeminfo cmd snapshot
Created attachment 174993 [details] workable windows 10 systeminfo
PS C:\Users\Training> [System.Environment]::OSVersion.Version Major Minor Build Revision ----- ----- ----- -------- 10 0 10586 0
Hotfix(s): 9 Hotfix(s) Installed. [01]: KB3116278 [02]: KB3124200 [03]: KB3150513 [04]: KB3161102 [05]: KB3172729 [06]: KB3173428 [07]: KB3181403 [08]: KB3188128 [09]: KB3185614
Created attachment 174995 [details] hyperv-warn2 It's reproducible. 1. boot 2. select install 3. select 4. f11r; ok 5. select src and test too; ok 6. auto (ufs); ok 7. enter 8. enter 9. select gpt; enter 10. enter 11. enter 12. on config passwd; a; enter; a; enter 13. enter 14. select no; enter 15. select no; enter 16. end; enter 17. enter 18. enter 19. enter 20. enter 21. enter 22. enter 23. on add user accounts; no; enter 24. enter 25. enter 26. on manual config...; yes; enter 27. init 0; enter
I followed your steps, but I cannot see any issues. Could you please try the VHDX https://honzhancustomer.blob.core.windows.net/freebsd11rc3issues/FreeBSD11RC3.vhdx on your machine? That is my newly installed VHDX on windows 10.
login user: root login passwd: User@123
Another VHDX was created on win2012R2 with the same login account https://honzhancustomer.blob.core.windows.net/freebsd11rc3issues/f11r_2012r2.vhdx
This messages comes at the end of the installer, and not at the end of normal installed instance.
(In reply to fbsd from comment #25) All right. Do you encounter any issue when you restart the machine after installation?
Not really, I just see this error message. Otherwise seems like the system is fully working with V1 install.
delete the following VHDX since they are not used. https://honzhancustomer.blob.core.windows.net/freebsd11rc3issues/FreeBSD11RC3.vhdx https://honzhancustomer.blob.core.windows.net/freebsd11rc3issues/f11r_2012r2.vhdx
11-STABLE works perfectly for me in a Gen 2 VM on Windows 10
Given comment #27, is there anything left to work on for this bug still or can it be closed?
(In reply to John Baldwin from comment #30) This is a bug opened 1.5 years ago. We have made a lot of fixes to the storage driver since then, and we also improved the support of Hyper-V Generation-2 FreeBSD VM a lot since then. It would be great if fbsd@hmamail.com can re-test this bug and I expect this bug doesn't exist any more. In case there is no response from fbsd@hmamail.com for a long period of time (say, 1 month?), I suggest we close the bug in 1 month.
Never got a confirm from the reporter, but it's been two months since it was requested.