virtualbox.org

I have a lab setup at home.
VirtualBox 5.0.10 on top of Solaris (11.3) host..

Have some OEL as a guest OS.
While copying big files
1. from one Linux guest to Other Linux guest
2. from one Linux guest to Solaris host

System simply hangs and become non-operational .. had to hard reset to re-start.
In my last attempt it created a tar ball of size 2.7G and hanged/crashed ...

Please assist !!!

I have looked at one of the post ...""VirtualBox 5.0.4 crashes Solaris 11.3 beta""

Have fired below command ...
VBoxManage setproperty hwvirtexclusive off

Fired creating tar ball again ....

So far it has created 4GB ...
Will post again with the status

This time the copy completed using method 2 above....
Request professionals here ... to confirm if this was the real culprit ...

was struggling since long ... not sure if RAC processes are the culprit ...

I will keep this post open for a day if someone responds ...

After using below command ... haven't find any issues ... will check for couple of more days ...
VBoxManage setproperty hwvirtexclusive off

I think we can close this post .. Not sure if I can do that !!

No !!!! It crashed / Hanged
While un-tar is going on one of the guest where CRS(11.2.0.4) is running, it hanged ...

I had to reboot solaris.
Not sure what all information is required .. but can give if needed...

Please assist...

It is crashing/hang at this point ...

00:31:53.088425 AsyncCompletion: Task 0xffff80ff6814e500 completed after 10 seconds
00:31:53.509510 AsyncCompletion: Task 0xffff80ff68147dc0 completed after 11 seconds
00:31:53.509589 AsyncCompletion: Task 0xffff80ff9046d980 completed after 11 seconds
00:31:53.509647 AsyncCompletion: Task 0xffff80ff681312c0 completed after 11 seconds
00:32:01.311015 AHCI#0P7: Write request was active for 30 seconds
00:32:01.311185 AHCI#0P7: Write request was active for 30 seconds
00:32:01.452901 AHCI#0P7: Write request was active for 30 seconds
00:32:05.575646 AHCI#0P7: Write request was active for 34 seconds
00:32:09.615103 AHCI#0P7: Write request was active for 38 seconds

Please read the following: Minimum information needed for assistance. As far as the "VBox.log.zip" goes, here's what you do:
- Start the VM.
- Observe the error. Is there an error message? What is it? EXACTLY.
- Shut down the VM (if it hasn't aborted by itself).
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

On top of that, we'd like to see the "recipe" of the VM.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show in Finder/Explorer/Whatever".
- Save it, ZIP it and attach it in your response.

NeerajKataria wrote:It is crashing/hang at this point ...

00:31:53.088425 AsyncCompletion: Task 0xffff80ff6814e500 completed after 10 seconds
00:31:53.509510 AsyncCompletion: Task 0xffff80ff68147dc0 completed after 11 seconds
00:31:53.509589 AsyncCompletion: Task 0xffff80ff9046d980 completed after 11 seconds
00:31:53.509647 AsyncCompletion: Task 0xffff80ff681312c0 completed after 11 seconds
00:32:01.311015 AHCI#0P7: Write request was active for 30 seconds
00:32:01.311185 AHCI#0P7: Write request was active for 30 seconds
00:32:01.452901 AHCI#0P7: Write request was active for 30 seconds
00:32:05.575646 AHCI#0P7: Write request was active for 34 seconds
00:32:09.615103 AHCI#0P7: Write request was active for 38 seconds

This is neither crashing nor hanging. All these messages mean is that your host system can't handle the I/O load generated by the guest.