I will not open a bug report, because a bug is a problem with a feature that is not working as advertised. This is not the case here, because VBox is not "advertised" as supporting 10.10 yet. I'll wait for 4.3.2x.
- Host: MacBookPro early 2011, 10.6.8, 4 physical CPUs, 16GB RAM, AMD Radeon HD 6750M.
- Guest: 10.10 final, 3GB RAM, 128 VRAM, 2CPUs, SATA controller. IO/APIC, PAE, VT-x, Nested Paging enabled.
- Modifications: 10.9 (64) template. Enabled 1280x1024 via the EfiGopMode=3 method.
- Symptom: Slow as molasses, mainly in the graphics department. CPUs in the guest are barely working, same as on the host, so no problem there. Disk activity is close to zero on both. But, mouse movement is jerky, keyboard input if more than 2 characters per second, misses characters. You can actually read the output of 'ls -alR /' in the Terminal as it scrolls by (haven't seen this one since I was using a 80286, so that brought back memories). Corrupted graphics in the toolbar (that's where the new translucent crap feature was added by Apple).
I compared the logs from a 10.10 and a 10.9 guest. Remember that the recipe is identical. Similar output (except of course the memory locations/assignments) except a minor point:
- 10.10 : 00:00:02.050804 EFI: VBoxDbg> loadimage64 'boot.efi.macho.x8.efi' 0xbe33d000 LB 0x90000
- 10.9 : 00:00:02.656756 EFI: VBoxDbg> loadimage64 'boot.sys.x8.efi' 0x7e363000 LB 0x7d000