vbox.log configuration

This is for discussing general topics about how to use VirtualBox.
Post Reply
Josef
Posts: 3
Joined: 10. May 2021, 03:53

vbox.log configuration

Post by Josef »

Hello. The current vbox.log system is quite useful for tracking state changes. Is there is a log level setting that would capture IMPORT and EXPORT operations?
thx
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: vbox.log configuration

Post by mpack »

VBox.log is a VM log. Export and import are not VM operations. You would find export/import in one of the manager logs in the .VirtualBox folder, if it's logged at all.

Export and Import are rarely used by most people, e.g. if you are using it for backup and restore then please stop!
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: vbox.log configuration

Post by scottgus1 »

Imports & exports should be logged in VboxSVC.log, in the .Virtualbox folder.
Josef
Posts: 3
Joined: 10. May 2021, 03:53

Re: vbox.log configuration

Post by Josef »

Thanks for the advice about log files and not using export/import. Is there a specific reason that one should avoid export/import? I suspect that one should use snapshots instead. How easily are snapshots transportable to other hosts, and will vm snapshot operations be logged inside VBox.log?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: vbox.log configuration

Post by mpack »

Josef wrote:I suspect that one should use snapshots instead.
Certainly not, snapshots are not backups in any sense of the word.

To make and restore a backup, just copy the VM folder to and from the backup media. Howto: Move a VM.

Import and Export modify the VM, which is not what you should be expecting from a backup. Import and Export only should be used when the VM needs to be moved to and from an incompatible VM platform. E.g. VMWare to VirtualBox.
Josef
Posts: 3
Joined: 10. May 2021, 03:53

Re: vbox.log configuration

Post by Josef »

Sound advice. thx
Gillykaboose
Posts: 23
Joined: 14. Jul 2020, 13:40

Re: vbox.log configuration

Post by Gillykaboose »

Hello Mpack, Trust all is well.

Reading your comments, do I understand your response correctly when you are saying to back up the VM all that is requred is to copy the file in which the specific VM is located into your chosen back area? A an export or cloning procdure is not required? In other words: VM folder copy into Backup VM folder?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: vbox.log configuration

Post by scottgus1 »

Yes, a copy of the folder that contains the .vbox file, the disk files and the Snapshots subfolder is a complete Virtualbox-compatible backup of the VM. The files can all be 'FC' file-compared for integrity checking, since no changes are made to the files. Hashing can also be used for offsite backup integrity checks.

The backup can be copied directly over the top of the existing VM (while the VM is shut down) to restore the VM to its backed-up state. Or the backup can be moved to a new host and registered there using the main Virtualbox window's Machine menu Add command.

Cloning is good for running multiple copies of the VM at the same time, but activated software may de-activate in the clones.

Exporting is only for taking the VM to another hypervisor, like Hyper-V or VMware. Export also changes activation-dependent codes in the VM.

(Note that some folks store the VM's disk files outside the VM folder, and there is even a way to put the Snapshots folder somewhere else. These choices complicate the above folder-copy backup process. Under the vast majority of situations, the disk files and Snapshots should be in the VM folder with the .vbox file. The whole VM folder can be on any SSD or platter disk you want to put it on.
Post Reply