Using SATA to install CentOS 5.3 locks up

[Mike]

I created a new Virtual Machine and attached a new Virtual Hard Disk to SATA port 0. I'm trying to install CentOS 5.3 amd64 from the installation DVD and it fails at random points in the installation. The Virtual Machine becomes completely unresponsive to any keyboard or mouse activity and the machine appears to hang.

I believe that it may succeed if I set number of processors to 1 but I haven't tested that under 3.1.0 yet.

My Host system is CentOS 5.3 amd64.

The log file does not appear very helpful:

00:00:08.225 Guest Log: BIOS: int13_harddisk: function 02, unmapped device for ELDL=81
00:00:08.225 Guest Log: BIOS: int13_harddisk: function 41, unmapped device for ELDL=81
00:00:10.462 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0)
00:00:10.462 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0)
00:00:15.591 EHCI: Hardware reset
00:00:15.591 EHCI: USB Operational
00:00:15.993 OHCI: Software reset
00:00:15.993 OHCI: USB Operational
00:00:16.449 OHCI: USB Suspended
00:01:34.238 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00002aaab980f000 w=800 h=600 bpp=24 cbLine=0x960

The host system is a dual-xeon quad core with hyperthreading (16 virtual cores):

processor : 15
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
stepping : 5
cpu MHz : 2400.047
cache size : 8192 KB
physical id : 1
siblings : 8
core id : 3
cpu cores : 4
apicid : 23
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx rdtscp lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr popcnt lahf_lm
bogomips : 4799.94
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: [8]

If any info is needed, please let me know.

[Mike]

Virtual Machine xml file

[Mike]

Log file

[Frank Mehnert]

Please reopen if this is still reproducible with VBox 3.2.6. Attach a new VBox.log file in that case.