Bug 270430 - gpart crashes when used in a VM on Apple Silicon
Summary: gpart crashes when used in a VM on Apple Silicon
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: 13.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-arm (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2023-03-24 14:53 UTC by Mark Felder
Modified: 2023-04-02 16:47 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Felder freebsd_committer freebsd_triage 2023-03-24 14:53:43 UTC 
If you try to execute the gpart command on an M1 Mac using the Parallels hypervisor which supports ARM guests you receive this error which breaks the ability to install:

gpart: Cannot get GEOM tree: Illegal byte sequence
Comment 1 Warner Losh freebsd_committer freebsd_triage 2023-03-24 15:25:08 UTC 
There is a sysctl to get the geom config. I think it's kern.geom.config.xml. what does that report. That's where the illegal sequence is coming from. Also, what is LANG? And does setting LANG to C.UTF-8 change things.
Comment 2 Bob Bishop 2023-03-24 15:47:38 UTC 
(In reply to Mark Felder from comment #0)
Hi, I can't reproduce this. What are your MacOS and Parallels versions?
Comment 3 Warner Losh freebsd_committer freebsd_triage 2023-03-24 16:42:14 UTC 
"sysctl kern.geom.confxml" is the command to capture the output from, if you can... Sorry for my fuzzy memory before.
Comment 4 Warner Losh freebsd_committer freebsd_triage 2023-03-24 16:44:03 UTC 
I suspect, btw, not a general issue, but that the name of some disk on this specific machine is bad, we don't encode it right in our XML and then we get the byte-stream error.
Comment 5 Mark Felder freebsd_committer freebsd_triage 2023-04-02 16:47:05 UTC 
I will try to reproduce this again but it took a bunch of work to trick chef/vagrant/bento to try generate an ARM FreeBSD image seeded with the vagrant ssh key. I blew it all away and decided to figure out how to get this to work with bhyve on my amd64 server instead.