Error unregistering floppy: VBoxManage error: VBoxManage: error: Could not find a controller named 'Floppy Controller'. Not considering this a critical failure; build will continue. #73
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
This seems to be an issue that has been occuring since earlier than 2016, and continues to present itself, across platforms and use cases. There are dozens of issues logged in this project, but I want to bring particular attention to #2401 which was logged in 2015, and was closed in 2020, but is still not resolved. There are earlier examples like #1193 and later examples also.
==> virtualbox-iso: Cleaning up floppy disk...
==> virtualbox-iso: Error unregistering floppy: VBoxManage error: VBoxManage: error: Could not find a controller named 'Floppy Controller'. Not considering this a critical failure; build will continue.
==> virtualbox-iso: Deregistering and deleting VM...
I am experiencing this issue, and it crashes my build and deletes all my efforts basically every time after hours of running, unless I can literally snatch the image file away before packer gets a chance.
That this has gone on for so long unresolved, I'm not sure what to say. Can something be done about this, beyond workarounds adjusting timeouts of shutdown_timeout and post_shutdown_delay?
I have adjusted these timeouts higher and higher, and still experience this issue. Running headless doesn't help. I would appreciate if this could get beyond screaming into the void, and nothing being done about it.
Reproduction Steps
Run Packer template as normal.
Issue occurs at end of runtime.
Packer version
Packer v1.8.2
on Ubuntu 20.04
Virtualbox 6.1.34_Ubuntur150636
This issue was originally opened by @KptnKMan in https://github.com/hashicorp/packer/issues/11935 and has been migrated to this repository. The original issue description is below.
Community Note
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
Overview of the Issue
This seems to be an issue that has been occuring since earlier than 2016, and continues to present itself, across platforms and use cases. There are dozens of issues logged in this project, but I want to bring particular attention to #2401 which was logged in 2015, and was closed in 2020, but is still not resolved. There are earlier examples like #1193 and later examples also.
I am experiencing this issue, and it crashes my build and deletes all my efforts basically every time after hours of running, unless I can literally snatch the image file away before packer gets a chance.
That this has gone on for so long unresolved, I'm not sure what to say. Can something be done about this, beyond workarounds adjusting timeouts of
shutdown_timeout
andpost_shutdown_delay
?I have adjusted these timeouts higher and higher, and still experience this issue. Running
headless
doesn't help. I would appreciate if this could get beyond screaming into the void, and nothing being done about it.Reproduction Steps
Run Packer template as normal. Issue occurs at end of runtime.
Packer version
Packer v1.8.2 on Ubuntu 20.04 Virtualbox 6.1.34_Ubuntur150636
Simplified Packer Template
In this example am using packer recommended scripts from: https://github.com/StefanScherer/packer-windows
Operating system and Environment details
Ubuntu 20.04 Virtualbox 6.1.34_Ubuntur150636
Log Fragments and crash.log files