Lots of error entries in VBoxSVC.log

[Reiner Brodbeck]

Looking into VBoxSVC.log I find lots of error entries.

When starting the VM Virtualbox Manager GUI, the first entries appear (time stamps 00:00:00 in attached file)

Then, related to time stamps beginning with 00:18:59 I executed the following commands, that are embedded in a script:

vboxmanage createvm --name AMHS-Tester --groups "/AMHS-CentOS-Eval" --ostype RedHat_64 --register --basefolder "E:\VMs\Eval-Testsuite\AMHS-CentOS-Eval\VMs"
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --memory 3072 --boot1 dvd --boot2 disk --boot3 none --cpus 8 --vram 12 --audio pulse --usb on --usbehci on
vboxmanage createhd --filename "E:\VMs\Eval-Testsuite\VMs\AMHS-CentOS-Eval\AMHS-Tester\AMHS-Tester" --size 16384 --format VMDK --variant Split2G
vboxmanage storagectl 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name IDE-Controller --add ide
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl IDE-Controller --port 0 --device 0 --type dvddrive --medium "E:\VMs\Eval-Testsuite\AMHSTESTER.iso"
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl IDE-Controller --port 0 --device 1 --type dvddrive --medium "C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso"
vboxmanage storagectl 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name SATA-Controller --add sata --portcount 1
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl SATA-Controller --port 0 --type hdd --medium "E:\VMs\Eval-Testsuite\VMs\AMHS-CentOS-Eval\AMHS-Tester\AMHS-Tester.vmdk"
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nic1 hostonly --hostonlyadapter1 "VirtualBox Host-Only Ethernet Adapter #2"
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nic2 natnetwork --nat-network2 NatAMHS
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nicpromisc2 allow-all
vboxmanage sharedfolder add 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name work --hostpath "E:\VMs\Eval-Testsuite\work" --automount
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --clipboard bidirectional
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --draganddrop bidirectional
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --vcpfile "E:\VMs\Eval-Testsuite\work\AMHS-Tester.webm" --vcpwidth 1920 --vcpheight 1200
vboxmanage startvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c

And finally, starting at time stamp 00:18:59 the script checked the VM every five seconds using:
vboxmanage showvminfo 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --machinereadable

The UUID is of course that of the newly created VM in the first command.