Opened 12 years ago
Closed 12 years ago
#11430 closed defect (fixed)
Mac OSX 10.8.2 Host / Windows 7 x64 Guest Dual Monitor Crash
Reported by: | mnichols | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.6 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description
Host OS: MBP with Retina Mountain Lion. Host Graphics: NVIDIA GeForce GT 650M VB Versions tried : 4.2.4 _and_ 4.2.6 Guest OS: Win7x64 Professional SP1, fully updated
Monitors: Dell 2408 , Dell 2407 Config:
- I _have_ installed Guest Additions.
- I disabled 3D and 2D
- Remote Desktop Server is disabled
- Max video memory (128MB)
- Guest RAM is 4GB
- SATA Controller for Guest OS
- Acceleration: VT-x/AMD-V, Nested Paging
I have successfully run dual monitor on this system with my Debian 6 guest. Running the guest in single monitor works fine and I can go into Full Screen mode.
Problem:
When I try to have dual monitor, the second window ({guestName} Running: 2) doesn't appear. If I try to go into to 'FullScreen Mode' in the one window that _does_ appear, the guest crashes and is reported as 'Aborted'. The weird thing is, there is not a log entry pertaining to the crash that I can see. There _is_ a crash report in the OS logs though.
I tried opening my Mac to see if the problem persisted but nothing is different.
I tried to 'extend desktop to ' the second monitor inside the Guest OS, but the VM Crashes when I do that, too!
I'm at a loss here and I can't see anything in the logs that help out. I am new to running VB on Mac, so perhaps there is something I should do?
I am attaching my VBox and my Mac .crash files which may help.
Attachments (4)
Change History (7)
by , 12 years ago
by , 12 years ago
Attachment: | VirtualBoxVM_2013-01-27-222401_Mikes-MacBook-Pro.crash added |
---|
Crash log from Mac
comment:1 by , 12 years ago
I just tested Win Server 2008 and Windows 8 as guests inside this same host. Dual monitor works okay for these OSs.
comment:3 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.2.10.
VBox log primary