https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #24 from Mark Linimon ---
^Triage: correct assignment. Discussed with: koobs@.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #23 from Phillip R. Jaenke ---
This continues to reproduce on 12.2-RELEASE but does not reproduce on
13.0-RELEASE with ESXi build 17551050. Note that it WILL reproduce on 13 with
some ESXi builds below 17551050, not sure which.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
ru...@verweg.com changed:
What|Removed |Added
CC||ru...@verweg.com
--- Comment #22
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #21 from Dan Kotowski ---
UEFI boot is now functioning normally with 12.2-STABLE r369049 on VMware
Workstation 16.1.0 build-17198959.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #20 from Daniel Morante ---
Created attachment 221977
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=221977&action=edit
Sample VMX file
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #19 from Daniel Morante ---
Here's what I'm observing:
VMWare Workstation: 15.5.7 build-17171714
Host: Windows 7 Enterprise, 64-bit 6.1.7601, Service Pack 1
Guest OS ISO: FreeBSD-12.2-RELEASE-amd64-bootonly.iso
1) Create a new
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #18 from Hongbo He ---
In addition to comment #17, I've just tried purging NVRAM with 12.2 RC3 (Which
TrueNAS 12.0 shipped as it's kernel) with no luck.
12.2-RELEASE will boot as normal while 12.2 RC3 will result in a reboot(n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #17 from Hongbo He ---
(In reply to Christian Ullrich from comment #13)
> 6. Delete the VM's .nvram file.
That's interesting!
Besides the trick that entering the EFI shell before boot, I've tried removing
the VM's .nvram file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
Yuri Pankov changed:
What|Removed |Added
CC||yur...@yuripv.dev
--- Comment #16 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #15 from Christian Ullrich ---
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 bo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #14 from Richard Wai ---
I am using the "lsilogic" SCSI controller.
I wonder if the very act of making any configuration change at all is what
makes the difference..
--
You are receiving this mail because:
You are the assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #13 from Christian Ullrich ---
I cannot reproduce the SCSI/NVMe behavior in 16.1; it fails with either
configuration. Which type of SCSI controller did you use?
However, I noticed something else potentially interesting.
It has
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #12 from Richard Wai ---
I just happened on something very interesting.
My previous post about it working since the latest Workstation 15 update is
misleading.
It turns out that if I attempt to boot from an (emulated) NVMe dri
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #11 from Christian Ullrich ---
Created attachment 219851
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219851&action=edit
VMware workstation log, slightly edited
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #10 from Christian Ullrich ---
Created attachment 219850
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219850&action=edit
Screenshot
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #9 from Warner Losh ---
can someone share the error messages and/or a screen shot of the failure?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #8 from Christian Ullrich ---
It still fails with the same message on Workstation 16.1.0 build-17198959,
released on the same day (2020-11-19) as 15.5.7 mentioned above.
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
Richard Wai changed:
What|Removed |Added
CC||rich...@annexi-strayline.co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
Dan Kotowski changed:
What|Removed |Added
CC||dan.kotowski@a9development.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
hehon...@mail.com changed:
What|Removed |Added
CC||hehon...@mail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #4 from Phillip R. Jaenke ---
(In reply to Roger Leigh from comment #3)
Yep, confirmed now this is not AMD-specific. Reproduced on a BabyDragon Gen.5
and a BabyDragon Gen.3.
Looking over things more closely, I am far more confid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #3 from Roger Leigh ---
Note this isn't AMD-specific. I've also reproduced on a Mac Mini (Intel) with
VMware Fusion. Screenshot and detailed logs are attached to
https://communities.vmware.com/thread/643481
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #2 from Phillip R. Jaenke ---
(In reply to Warner Losh from comment #1)
Unfortunately, this is in a restricted environment, so no luck this time.
*Fortunately*, the reproduction is relatively easy.
1) Needs AMD Ryzen, Threadrip
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
--- Comment #1 from Warner Losh ---
Any chance I could get remote access to the environment that causes problems?
--
You are receiving this mail because:
You are the assignee for the bug.
___
fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
Phillip R. Jaenke changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
Bug ID: 250580
Summary: VMware UEFI guests crash in virtual hardware after
r366691
Product: Base System
Version: Unspecified
Hardware: amd64
OS: Any
27 matches
Mail list logo
