vagrant box xenial-server write log file on absolute path on host. Even if synced folder is disabled.

[Fred Moser]

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 !

[Maxwell (maxwell1987)]

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.

[Fred Moser (fredmoser)]

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

[Gary Diamond (skeeve27)]

Is it possible not have the VM not write the log file by default? Also, don't include the customization for VirtualBox in the Vagrantfile packaged within the official Vagrant image? Having the log file goes against the spirit of official images. This is similar to when default user for the official image was 'ubuntu' instead of 'vagrant'.

[Whileloop (whileloop)]

My VM never boots when using the work around Maxwell mentioned.

[Dan Watkins (oddbloke)]

Hi Fred, all,

Thanks for using Ubuntu! It's not entirely clear to me what the issue is here, so I'm going to mark this as Incomplete. If someone can provide clear reproduction instructions (including what you expect to happen and what you actually see happening), please set it back to New.

Thanks,

Dan

[Fred Moser (fredmoser)]

Thanks for looking at this.

1. Create a `Vagrantfile` for VirtualBox VM
--
Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/xenial64"
end
--

2. Launch Vagrant
--
> vagrant up
--

3. Inspect the folder where the Vagrant file is. There is a log file. This should not be there.
4. Stop vagrant machine
--
> vagrant halt
--
5. Export the virtual box appliance as an ova in another directory
4. Delete or rename the folder where the log is.
6. When reimported in VirtualBox, the OVA will not work because it will fail to load the log file :

--
RawFile#0 failed to create the raw output file /private/tmp/testUbuntuBox/ubuntu-xenial-16.04-cloudimg-console.log (VERR_FILE_NOT_FOUND).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--

I dont need this box nor vagrant anymore, so not a priority for me now.

Thanks !

[Dan Watkins (oddbloke)]

Thanks for the reproducer, Fred! That confirms that this is a duplicate of an issue we've fixed in the development release of Ubuntu, so we can continue to track this issue in that bug.