Bug 2549 - [USE CASE] Support live images on emulated targets (hddimg for kvm)
Summary: [USE CASE] Support live images on emulated targets (hddimg for kvm)
Status: RESOLVED OBSOLETE
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 1.1.1
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-06-06 12:50 UTC by Ross Burton
Modified: 2025-04-24 14:59 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2012-06-06 12:50:07 UTC
Build an atom-pc image as a .hddimg, and boot it under KVM.  It will hang at udev's "waiting for removable media" message.

Interestingly, .iso images boot fine.

(probably a low-priority bug as really the machine for running under kvm should be "kvm")
Comment 1 Darren Hart 2012-06-08 15:49:20 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.
Comment 2 Randy MacLeod 2019-04-11 16:42:18 UTC
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.
Comment 3 Ross Burton 2025-04-24 14:59:37 UTC
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.