| Summary: | [USE CASE] Support live images on emulated targets (hddimg for kvm) | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | deployment | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie, sgw |
| Version: | 1.1.1 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Ross Burton
2012-06-06 12:50:07 UTC
I believe the key here is the image type, not the machine. The image type, hddimg, is a live image and relies on udev to notify when the USB key is detected. We typically boot directdisk style images, or just filesystem images directly. when working with emulation. I agree that this is likely lower priority. I'm actually going to mark this as an enhancement "Support live images for emulated targets". I suspect the image isn't being used as removable media by KVM. Kevin, See if you can *easily* make hddimg work for qemu/runqemu and if not, summarize the situation to the list and CC Richard/Ross to get some guidance. I struggle to remember the full context on this but I don't think it's relevant anymore... wic images in my experience just boot in kvms. |