packer-plugin-qemu
packer-plugin-qemu copied to clipboard
hashicorp
PACKER_LOG_PATH file doesn't reveal when QEMU segfaults.
This issue was originally opened by @daveloyall as hashicorp/packer#5119. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
- Packer v1.0.2
- Linux boxfactory 4.9.0-3-amd64 # 1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 GNU/Linux
For whatever reason, my qemu is segfaulting. I'll figure that out.
But, it took me half an hour to figure out that qemu was segfaulting. This means that the packer logs could be improved.
I thought about how to reproduce this bug... Probably the easiest way is to create a file called segfault.c and put the following content in it:
main;
...Then compile it with gcc segfault.c -o qemu-system-x86_64 and install the resulting binary wherever your real qemu binary should be...
That may sound weird, but then you can just adjust the source of packer until the logs properly say "qemu segfaulted!"
I hope this is helpful. Thanks for making packer.
this is old, but can you publish the logs at the time qemu segfaulting? @daveloyall
😂
On Fri, Sep 10, 2021 at 6:10 AM Dave Loyall @.***> wrote:
I'm sorry, I can't jshen28. That segfault happened in 2017.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/hashicorp/packer-plugin-qemu/issues/16#issuecomment-916475551, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADH3XAY6SHL37TOG76ERHJ3UBEWHFANCNFSM43GFC5BQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
--
Best Regards,
Jiatong Shen