| Summary: | can't generate live/iso/hddimg for aarch64 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | niqingliang2003 <niqingliang2003> |
| Component: | core | Assignee: | niqingliang2003 <niqingliang2003> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, ross.burton, tim.orling |
| Version: | unspecified | ||
| Target Milestone: | 5.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | NIR 07/11, 07/18 | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
niqingliang2003
2025-06-10 01:28:01 UTC
Can you just use a normal .wic image and copy it to a USB stick or SD-Card? Somewhat related is https://bugzilla.yoctoproject.org/show_bug.cgi?id=13263 about replacing cdrecord with xorriso. There's also discussion about moving the live/hddimg/iso type out of core because it's such a niche case. Can you explain your use-case? Are you making actual physical CDs to boot on aarch64, or using live images on USB sticks? I'm packaging for multi arch, and want to use same file format both for x86 and aarch64 Why not use a more standard GPT disk image built using wic? Do you need any of the functionality provided by hddimg/live? the hdd image is like binary data, that is the reason I don't want to use. In my opinion, the iso is more friendly to user than hdd image. How are these users booting your images? If it's anything apart from a physical CD then ISO images are massively overcomplicated. I think same as ubuntu arm iso But I'm not asking how ubuntu users are using aarch64 ISOs, I'm asking how _you_ are. Because we want to solve real problems, not hypothetical ones. use iso to boot efi arm64 server From an actual physical CD-ROM, or a USB stick? I think this has been fixed with oe-core 4ea24276ad3b6cf3d63a839f3c5fbe697ccd28cd "support disable isohybrid for EFI-only boot". |