| Summary: | hddimg incorrect partition table | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Todor Minchev <todor.minchev> |
| Component: | bsps-meta-intel | Assignee: | Todor Minchev <todor.minchev> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | eduard.bartosh, sgw |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Todor Minchev
2016-12-07 18:18:38 UTC
Does hddimg have partition table at all? Here is the output of fdisk -l for qemux86-64 machine: $ /sbin/fdisk -l ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-2016120223*.hddimg Disk ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20161202233134.hddimg: 25.7 MiB, 26892288 bytes, 52524 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 JFYI: There is a proposal and ongoing activity of getting rid of hddimg: http://lists.openembedded.org/pipermail/openembedded-architecture/2016-December/000359.html hddimg images infer their partition table from the partition table of the host on which they are generated. Closing this as we are removing hddimg. |