Can you share a zip with packer template and scripts? I can run a build in
a MAC to test
On Sun, Jul 24, 2016 at 11:50 AM, Bruno Vernay
wrote:
> I set information in post_manage, like
> "vboxmanage_post": [
> ["modifyvm", "{{.Name}}", "--vrde", "off"],
> ["modifyvm", "{{.Name}}", "--nic1", "nat"
I set information in post_manage, like
"vboxmanage_post": [
["modifyvm", "{{.Name}}", "--vrde", "off"],
["modifyvm", "{{.Name}}", "--nic1", "nat"],
...
["modifyvm", "{{.Name}}", "--cableconnected2", "on"]
But they are lost in translation. I have to re-set them on the command
line, after having i
Sure,
if you can add steps how to reproduce, and what you have found, that will
help a lot
Thanks for looking after this.
Alvaro
On Sun, Jul 24, 2016 at 9:19 AM, Bruno Vernay wrote:
> At this point maybe I should open an issue, shouldn't I??
>
> --
> This mailing list is governed under the Ha
At this point maybe I should open an issue, shouldn't I??
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues:
I tried on the VirtualBox forum
https://forums.virtualbox.org/viewtopic.php?f=7&t=78830
But they claim the issue is on Packer side :-)
As for me running headless solved my issue. I though about it reading the
last line in VirtualBox logs:
00:05:21.112882 Changing the VM state from 'DESTROYING'
We crossed our post.
I was not talking about Packer output directory, but VirtualBox machine
directory ...
On Saturday, July 23, 2016 at 10:30:21 PM UTC+2, Loren Gordon wrote:
>
> Oh right. I see. On my system I don't see logs in my machine directory.
> But I use the `output_directory` paramete
If I understand correctly, Packer:
1. Creates the Machine
2. Provision it
3. shutdown
4. runs post_manage (if there are no session still hanging)
5. Export the machine as an ovf
6. unregister and delete the machine (including VirtualBox logs)
Then I import the OVF back to Virtua
Oh right. I see. On my system I don't see logs in my machine directory. But
I use the `output_directory` parameter to create the machine in an
alternate location. If you use the `output_directory` parameter, perhaps
the logs would be preserved wherever they are saved and only the virtual
disk f
Sorry, I was not clear: I do not want to copy files between host/guest.
It all happens on the host. VirtualBox keeps a logs of its operations in
its machine directory. But all this is cleaned up by Packer in case of
failure.
That is my problem ...
--
This mailing list is governed under the Ha
Is packer making it to the "provisioners" stage? If so, and if you know the
path to the file you want, you could try using the `direction` parameter of
the "file" provisioner to download it.
{
"type": "file",
"source": "/tmp/manifest.log",
"destination
The VirtualBox forums are asking for logs and I have a hard time to get
them since Packer clean up everything.
I ended up doing "tail -f VBMachines/my-vm/Logs/VBox.log" but maybe there
is a better way?
The --debug step-by-step is not an option since there is a timing issue and
I don't reproduc
Sorry, but I am getting excited: if I run step by step with --debug ...
there are no errors.
So it might be a timing issue. If Packer could introduce a short delay or
a retry or if there was some kind of synchronous call that could asset that
the Machine i ready to accept commands, that would b
Funny this is that if I run "guestcontrol list sessions", it says there are
no sessions
==> vb-fedora-24-np: Executing custom VBoxManage commands...
vb-fedora-24-np: Executing: guestcontrol vb-fedora-24-np list sessions
--verbose
==> vb-fedora-24-np: Error executing command: VBoxManage error:
Yes, I guess I should do that also, but it is strange.
If I issue the VBoxManage commands from the command line, after exporting
the machine, it works.
But if I use the vboxmanage_post it fails as if a session was still open.
But the VM is supposed to be stopped when post commands are runs right?
14 matches
Mail list logo
