#7271 closed defect (fixed)
Storage systems disconnecting randomly. — at Version 3
Reported by: | daniel | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 3.2.6 |
Keywords: | vdi lvm vmdk sata storage freezing | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description (last modified by )
HOST:
Server installation of VirtualBox PUEL on SunFire x2270
CPU: Intel Xeon E5504, 2.00GHz (64bit) Storage: 2 SATA disks, RAID1 (root partition); 3 SATA disks, RAID5 (data partition) OS: CentOS 5.5
GUEST
Various 64bit linux distributions - CentOS 5.5 (just the same image as host), Fedora 13, Arch Linux.
CPU: added one or two cores, IO/APIC enabled, EFI disabled, PEA/NX disabled, VT-x enabled, Nested Paging enabled
RAM: 2048MB
Storage: SATA controller (AHCI), standard 150GB *.vdi on xfs physical filesystem., host IO caching disabled, dm_crypt/luks encrypted /home partitionm ext3 filesystem
Network: bridged Pc-NET III fast
Linux guest is accessed through the VRDP connection.
BUG:
After accessing the destkop, system is randomly freezing. Networking still works, I can ping the machine, but SSH won't give me shell after logon. I can click on some running apps (probably cached in RAM) but I am not able to work with them. It seems like the VDI disk was completely disconnected from virtual machine.
I did few tests.
=> disabled dm_crypt/luks encryption => changed standard vdi disks from xfs physical filesystem to logical volumes with RAW vmdk abstraction => changed host OS from CentOS to Arch Linux => changed virtualbox from centos rmp package => changed virtualbox "all distribution" binary => changed virtualbox compiled from ArchLinux user repositury
And remote virtual desktop is still getting frozen in the same way.
Logs says nothing, I went through vbox.log, dmesg, messages.log, kernel.log, syslog, faillog - nothing relevant at all.
Change History (3)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
well, unfortunatelly, problem remains. i've tried also ide controller with *.vdi images and got the same results.
in order to really exclude some kind of hardware issue, i've installed vbox puel *.deb package on completely different machine (with debian seystem.)
after some hours of remote work - dstat no longer made any record of machnine's activity.
comment:3 by , 11 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Closing, please reopen if still relevant with a recent release of VirtualBox.
Chance is that the fixes to the virtual SATA controller which went into 3.2.8 are addressing those issues...