Closed jbsmith86 closed 5 years ago
Please only use GitHub Issues for reporting bugs and feature requests. Do not ask for general help here. Use IRC #packer-tool
on Freenode or the mailing list for that.
See https://www.packer.io/community/
If you are describing a bug or a feature request please reopen and try to add some more details to make it clearer.
Your template is wrong. Please ask on the mailing list.
Template works fine with raw, breaks in qcow2 seems to be a bug imo
This template is essentially what is on the qemu example https://www.packer.io/docs/builders/qemu.html
Your template have a empty boot_command
. Unfortunately the example in the docs is not functioning, we have already fixed that but the update hasn't been deployed yet.
@jbsmith86 I have somewhat of an identical issue and found that adding
"skip_compaction": "true",
to the "builders"-section of the JSON-file helped me out. Building a Debian Jessie amd64-box, not Ubuntu.
However the result is a significant bigger image! 1.1G for file debian-8.11.libvirt.box
And unpacked, 3.8G: file box.img: QEMU QCOW Image (v3), 68719476736 bytes
Tested with my yet unpublished version of Packer - see #6955. Might be related to the handling of things in QEMU 3.0.0 too.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Packer version: 1.3.1 Platform: OSX high sierra Template:
I can download and build a new ubuntu 18.04 image however once it finishes, qemu cannot boot the output qcow2 image, even if I remove all boot commands. I've tried numerous things, reinstalling grub and making sure the drive has the boot flag and it still doesn't boot. I just get the message "no bootable device" on kvm and also "no bootable device" running the output as a disk image with packer. The device identifier is /dev/vda and I am using an LVM drive on the entire volume with default setup settings. This template and all the boot commands worked perfectly fine in Ubuntu 16.04