Date: Mon, 23 Nov 2020 07:14:50 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 250580] VMware UEFI guests crash in virtual hardware after r366691 Message-ID: <bug-250580-227-fKI5njIb6f@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250580-227@https.bugs.freebsd.org/bugzilla/> References: <bug-250580-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250580 --- Comment #15 from Christian Ullrich <chris@chrullrich.net> --- A hard disk installation also boots successfully after deleting the .nvram file, but the system clock setting is lost, i.e. unless the host is in UTC,= the VM will be in the wrong time zone after booting. This can be worked around = by adding rtc.diffFromUTC =3D 0 to the .vmx file. Source: https://www.vmware.com/files/pdf/techpaper/Timekeeping-In-VirtualMachines.p= df, page 10. There does not appear to be a lot of other important data in the EFI NVRAM = on VMware. In cases where the automatically selected hard disk boot option is = the right one, deleting the .nvram file may be a usable workaround. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250580-227-fKI5njIb6f>