| Summary: | kvm not enabled with qemu | ||
|---|---|---|---|
| Product: | [Runtime] General Runtime | Reporter: | Laurentiu Serban <laurentiu.serban> |
| Component: | General Runtime | Assignee: | Saul Wold <sgw> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandrux.palalau, scott.a.garman, sgw, yp.kernel.watcher, yp.watcher |
| Version: | 1.3 | ||
| Target Milestone: | 1.3 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Laurentiu Serban
2012-08-20 11:27:17 UTC
Does this also happen with ext3 images? I notice this is a btrfs image, I am building a btrfs image also to test. I also tested with a btrfs image and it works for me.I am going to close this one, if there is a real problem, please provide more details. Tested on 1.3_M3.rc2 tag with ext3 image and the error is still encountered. Ok, I see the problem now! It's really a runqemu issue not parsing MACHINE, you missed putting qemux86 on the runqemu command runqemu tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-sato-qemux86-20120819235319.rootfs.btrfs kvm It should be runqemu qemux86 tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-sato-qemux86-20120819235319.rootfs.btrfs kvm The check for a blank machine and parsing of the kernel comes AFTER the kvm check, should be a straight forward fix. Verified in commit id 8ebed883d45ee952bd89d2143e0b0ab8736049b0 |