After great results trying out VirtualBox on an Ubuntu Feisty host (kernel 2.6.20-16-generic, 32bit) with an W2K guest I had to learn that playing any kind of mpeg video files, independent on the Windows program used and independent where they reside, leads into a messageless hanging state of the guest after a few seconds
The VirtualBox process while in sleeping state guzzles all CPU cycles from this point on. There is no entry in W2K event log relating to the situation, and the VBox.log does not contain a single line referring to the situation. The last entries in the log are:
00:00:20.409 PCNet#0: Init: ss32=1 GCRDRA=0x02733220[32] GCTDRA=0x02733020[32]
00:00:32.367 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=b0f15000 w=1192 h=877 bpp=16 cbLine=0x950
00:00:32.367 VBVA: Enabled.
00:00:33.957 Guest requests mouse pointer integration
00:00:36.694 NAT: DHCP offered IP address 10.0.2.15
00:00:36.701 PCNet#0: Init: ss32=1 GCRDRA=0x02733220[32] GCTDRA=0x02733020[32]
00:00:43.929 Audio: set_record_source ars=0 als=0 (not implemented)
00:00:59.730 Audio: set_record_source ars=0 als=0 (not implemented)
00:01:00.416 Guest Additions capability report: (0x1) VMMDEV_GUEST_SUPPORTS_SEAMLESS: yes VMMDEV_GUEST_SUPPORTS_GUEST_HOST_WINDOW_MAPPING: no
00:01:01.841 PATM: Stop monitoring IDT handler pages at 827d0ae4 - invalid write 827d097c-827d0980 (this is not a fatal error)
00:01:02.728 PATM: Stop monitoring IDT handler pages at 827d0404 - invalid write 827d097c-827d0980 (this is not a fatal error)
01:12:48.908 VMMDev::SetVideoModeHint: got a video mode hint (1192x877x0) at 0
01:15:56.704 Audio: set_record_source ars=0 als=0 (not implemented)
01:15:57.924 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:15:57.943 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:15:59.547 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:15:59.566 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:08.545 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:08.567 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:09.360 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:09.374 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:11.649 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:11.658 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:12.493 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:14.509 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:14.528 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:23.569 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:23.588 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:26.539 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:26.557 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:35.555 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:35.567 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:35.639 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:35.640 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:38.559 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:38.572 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:38.941 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:38.942 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
01:16:39.594 PIT: mode=2 count=0x4ad (1197) - 996.81 Hz (ch=0)
01:16:48.051 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0)
The only way to get out of this state is to power down or reset the machine.
This bug does not depend whether I use AMD-V or not. The processor is "AMD Athlon(tm) 64 Processor 3500+", featuring: fpu, vme, de, pse, tsc, msr, pae, mce, cx8, apic, sep, mtrr, pge, mca, cmov, pat, pse36, clflush, mmx, fxsr, sse, sse2, syscall, nx, mmxext, fxsr_opt, lm, 3dnowext, 3dnow, up, pni, cx16, lahf_lm, svm, cr8legacy, ts, fid, vid, ttp, tm, stc.
W2K reports AMD Athlon(tm) 64 Processor 3500+ as well. The guest has 384M RAM and 32M graphic memory.
What is going wrong here?
FMF