virtualbox.org

Hi,

I have a problem that yet I can figure it out. I have Ubuntu 18.04 host, running VirtualBox 6.0.14 with a VM of Windows 10. Almost everyday this VM appears as aborted (same was happening with version 5.x of VirtualBox).

I am attaching the last log before VM gets aborted.

Thanks in advance.

Your Extension Pack doesn't match your Virtualbox:

00:00:00.663089 VirtualBox VM 6.0.14 r133895 linux.amd64 (Oct 10 2019 21:02:02) release log
00:00:00.701031   Oracle VM VirtualBox Extension Pack (Version: 6.0.10 r132072; VRDE Module: VBoxVRDP)

The Extension Pack must match the Virtualbox version number exactly. This may be why you're getting so many Virtualbox RDP errors.

The log does not end. Try to post a log that shows the Virtualbox guest window being closed, however it's closed, preferably by shutting down within the guest OS.

If your guest shows up Aborted again, please zip and post another log, as well as the guest's .vbox file from the guest folder, using the forum's Upload Attachment tab.

One other thing... Where did you get this VM from? Because there's a discrepancy between your VM and your hard drive's name, which is a VMDK, not the default:

00:00:00.906332 File system of '/home/vbox/VirtualBox-VMs/win10-admin/ADMIN PRUEBA-disk002.vmdk' is ext4

scottgus1: yes, because I've upgraded the version of VirtualBox and forgot the extension pack, but the problems is before then. I will post again when happen.

socratis: because comes from migration from a test VM from other server, thats why it has a different name (and which has nothing to do with what I am asking here, I believe).

gusarg81 wrote:which has nothing to do with what I am asking here, I believe

How you build your guest... you think that this is irrelevant to why your VM gets aborted? Not at all, not at all...

The next step will be to ask you to install a fresh VM, just FYI...

Hi,

Here the logs and .vbox files (after a new aborted state), and hence he sice, I can't upload here. Here is the link to my Cloud:

https://cloud.gdnet.ar/index.php/s/eFGfJ6YZDPk3EXf

gusarg81 wrote:I can't upload here

Yes you can, if you ZIP them first... Please do.

The compressed file (whatever is zip or another) is bigger than what this forum allows to attach.

Maybe, because you ZIPPED all 4 logs. When I'm asking for a log, I don't want to see 4 random logs, from 4 random run, with random settings. I want to see "The log" where/when the problem occurs.

If you ZIP just the VBox.log, it will fit...

But you mean the log thats correspond to that VM? Is not supposed to be the first log the last one?

VBox.log is the latest complete VM run.
VBox.log.1 is the one before VBox.log.
VBox.log.2 is the one before VBox.log.1.
VBox.log.3 is the one before VBox.log.2.

Here are my typical instructions...

We need to see a complete VBox.log, from a complete VM run, where the problem actually occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response.

I will wait till get aborted again to grab that particular Log, because is a VM that just has a platform for billing and related stuff, there is no way to reproduce it easily because I don't know exactly when happens, because it acts like a server. This means, nobody is using that VM, but only the platform running in it.

Also, this is very random for me, because it freeze even when nobody is using it.