Bug 242106 - [panic] zfree(0xe4e9690,8224): wild pointer during install from 12.1R amd64 ISO in Parallels VM
Summary: [panic] zfree(0xe4e9690,8224): wild pointer during install from 12.1R amd64 I...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-virtualization (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-20 12:03 UTC by Dave Cottlehuber
Modified: 2020-10-05 13:13 UTC (History)
4 users (show)

See Also:


Attachments
parallels vm boot screen (117.88 KB, image/png)
2019-11-20 12:03 UTC, Dave Cottlehuber
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Cottlehuber freebsd_committer 2019-11-20 12:03:24 UTC
Created attachment 209278 [details]
parallels vm boot screen

..
FreeBSD/x86 bootstrap loader revision 1.1
cd0: read 1 sector(s) from 8094719 to 0xffffe000 (8x8000): 0x1

panic: zfree(0xe4e9690,8224): wild pointer
--> Press a key on the console to reboot <--

- Parallels v15
- sha of downloaded images matches
- happens with mini iso and full iso
- doesn't matter if I use SATA or IDE connection in vm
- doesn't matter if I change emulation/hypervisor engine in vm
Comment 1 Ken Rachynski 2020-01-06 20:04:37 UTC
I reported this to Parallels and received the following reply:

"Please be informed that the FreeBSD is supported till 12 and hence will not support 12.1 or later. We will take this as a feedback and forward it to our Product Management Team for their consideration."
Comment 2 Dima Sipovich 2020-03-21 14:28:41 UTC
I got this problem. 
On the screen I have this.
..
FreeBSD/x86 bootstrap loader revision 1.1
cd0: read 1 sector(s) from 8094719 to 0xffffe000 (8x8000): 0x1

panic: zfree(0xe4e9690,8224): wild pointer
--> Press a key on the console to reboot <--


I use mainboard intel DX38BT with 8GB Ram
hdd ssd MTRON 64GB.  

What should I do ?
Comment 3 Andy Mender 2020-03-26 19:45:06 UTC
Oddly enough, this very same error occurs when booting a non-VM image of FreeBSD-12.1-RELEASE as well. So far I tried the following images (uploaded to the official FreeBSD FTP server on 2019-11-01, at around 5 am):
- FreeBSD-12.1-RELEASE-amd64-bootonly.iso
- FreeBSD-12.1-RELEASE-amd64-disc1.iso

I will test also -STABLE and -CURRENT images just in case.
Comment 4 Andy Mender 2020-03-26 20:05:35 UTC
(In reply to Andy Mender from comment #3)
Image FreeBSD-12.1-STABLE-amd64-20200326-r359308-bootonly.iso no longer shows the error and boots properly.
Comment 5 Dima Sipovich 2020-04-07 20:48:52 UTC
(In reply to Andy Mender from comment #3)
OK, I will be to wait.
If you want, I can add some photo with error.
Comment 6 Jonathan 2020-10-04 18:36:27 UTC
Set vm.bios.efi = 1 to the boot flag in the boot order settings. That should resolve the issue.
Comment 7 Jonathan 2020-10-05 13:13:10 UTC
(In reply to Jonathan from comment #6)
Let me clarify: this is the boot order within parallels settings.