Comment 2 for bug 1639732

Revision history for this message
Fred Moser (fredmoser) wrote : Re: [Bug 1639732] Re: vagrant box xenial-server write log file on absolute path on host. Even if synced folder is disabled.

Thanks.

I did not know that virtualbox could write in my vagrant folder, that's weird. Never see this before. And the absolute path is kept somewhere: if I export an ova (some colleague do not want to use vagrant), the VM will not work because of this. I will keep working with another box that does not do this.

Thanks again.

> Le 8 nov. 2016 à 04:51, Maxwell <email address hidden> a écrit :
>
> Virtualbox(or other VM) wrote the log, not guest system. Guest's COM1 redirected to a file. Add
> config.vm.provider "virtualbox" do |vb|
> vb.customize [ "modifyvm", :id, "--uartmode1", "disconnected" ]
> end
> to Vagrantfile can disable the log.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1639732
>
> Title:
> vagrant box xenial-server write log file on absolute path on host.
> Even if synced folder is disabled.
>
> Status in cloud-images:
> New
>
> Bug description:
> vagrant box xenial-server write log file on absolute path on host.
> Even if synced folder is disabled. So, firstly, absolute path should
> be replaced by relative path. Then, if synced folder is disabled,
> nothing should be written on host.
>
> Thanks !
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-images/+bug/1639732/+subscriptions