Date: Tue, 01 Sep 2015 17:49:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 202687] UEFI boot doesn't work on VMware virtual machines due to device path is broken Message-ID: <bug-202687-27103-HyJpYRpVoJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202687-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-202687-27103@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=202687 Ed Maste <emaste@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #1 from Ed Maste <emaste@freebsd.org> --- > This issue was also found in FreeBSD 10.1 release. > > Based on our developer's investigation with FreeBSD 10.1 release, it was found that the bootloader corrupted one of our device path, which looked like this: That is a different issue and should be fixed by the change in PR 197641 (but please confirm). That change is in FreeBSD 10.2. I suspect you are running into another set of issues which have been fixed in HEAD and stable/10, but did not make it in time for 10.2-RELEASE. See PR 191564 and related PRs for the details of those issues -- can you please retest with a stable/10 or HEAD snapshot? -- 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-202687-27103-HyJpYRpVoJ>