Specifically – the bug is exposed by the IPv6 boot data that is stored in the firmware of a Generation 2 virtual machine. The effect of the bug is that the firmware state on a version 5.0, Generation 2 virtual machine from Windows Server 2012 R2 cannot boot on Windows Server 2019.
In the process we unfortunately exposed a bug. In Windows Server 2019 we made several changes to the virtual machine firmware (a topic that I plan to blog about another day). We have been digging into these issues and have identified the root cause. If the problem persists, contact Product Support. ‘Test VM 1’ was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support for the guest operating system.
‘Test VM 1’ has encountered a fatal error but a memory dump could not be generated.
People are seeing error messages like the following:Ĭritical 16:13:49 Hyper-V-Worker 18604 None In the last couple of weeks, we have been hearing reports from customers who are encountering problems after migrating virtual machines directly from Windows Server 2012 R2 to Windows Server 2019. My problem is that, I also have read several blogs and articles stating that is required for a VDI deployment when using RD Web to access the Win10 Vms plus the VDA which seems to be an overkill.UPDATE: This issue is now resolved in the cumulative update (KB4497934) In fact, I have implemented several times RD GW and RD Web to connect to physical/virtual servers that were not RDSH servers and I did not even needed to install the RD Licensing role. Seems that RDS CAL are only required when users connect to a RD Session Host server not when you connect to a VM running in a RD Virtualization Host. I have a question about RDS lisensing for a Windows 10 VDI deployment project using Windows Server 2019 Remote Desktop Virtualization Host role.Īs per this documentation: rds-client-access-license
0 kommentar(er)
