Page 1 of 1

Win7 aborts when I try to run in VB

Posted: 11. Mar 2010, 19:43
by sundance2010
Hi all,

I have installed Win 7 in VB on my mac running Snow leopard. When I try to run windows it starts to load and just after welcome screen it stops and shuts down and it says abort under the icon in VB. Win runs OK in safe mode in VB. :cry: BTW, it ran OK when it was first installed and I don't know what I did (if it was me) to cause this.

Any help on this out there?

Thanks

Most recent VB log file attached.

Here is the information from the Mac host:

Last login: Thu Mar 4 18:30:43 on console
S-Ls-Mac-Pro:~ sl$ VBoxManage showvminfo Win7onMac
VirtualBox Command Line Management Interface Version 3.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Name: Win7onMac
Guest OS: Windows 7
UUID: 824f5301-54af-4e8a-a1b8-44287a515df3
Config file: /Users/sl/Library/VirtualBox/Machines/Win7onMac/Win7onMac.xml
Hardware UUID: 824f5301-54af-4e8a-a1b8-44287a515df3
Memory size: 4096MB
VRAM size: 100MB
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: on
Time offset: 0 ms
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging: off
VT-x VPID: off
State: powered off (since 2010-03-11T17:41:47.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Name (1): Floppy Controller
Storage Controller Type (1): I82078
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 1
Storage Controller Port Count (1): 1
IDE Controller (0, 0): /Users/sl/Library/VirtualBox/HardDisks/Win7onMac.vdi (UUID: 054519f3-367a-4ea9-ab13-7ef13001afb3)
IDE Controller (1, 0): /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso (UUID: b3a6f578-fcfa-4c9e-b16e-e60a04a65c7e)
Floppy Controller (0, 0): Empty
NIC 1: MAC: 0800278D275B, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
UART 1: disabled
UART 2: disabled
Audio: enabled (Driver: CoreAudio, Controller: AC97)
Clipboard Mode: Bidirectional
VRDP: disabled
USB: enabled

USB Device Filters:

Index: 0
Active: yes
Name: New Filter 1
VendorId:
ProductId:
Revision:
Manufacturer:
Product:
Remote: <NULL>
Serial Number:

Shared folders: <none>

Guest:

Statistics update: disabled

Re: Win7 aborts when I try to run in VB

Posted: 18. Mar 2010, 00:06
by rpmurray
According to what you posted, your Mac has 8192MB of RAM, of which 3937MB is available, and you're trying to allocate 4096MB to the guest. You'll either need to close down some apps on the Mac to free up more memory, or change the amount you've allocated to the guest so that it can run. You may want to change the amount of RAM you give Win 7 to 2000MB or 2500MB. That way you also get around what appears to be a bug in VB where allocating more than 3000MB seems to cause problems in the guest.

Re: Win7 aborts when I try to run in VB

Posted: 4. Apr 2010, 03:17
by sundance2010
rpmurray wrote:According to what you posted, your Mac has 8192MB of RAM, of which 3937MB is available, and you're trying to allocate 4096MB to the guest. You'll either need to close down some apps on the Mac to free up more memory, or change the amount you've allocated to the guest so that it can run. You may want to change the amount of RAM you give Win 7 to 2000MB or 2500MB. That way you also get around what appears to be a bug in VB where allocating more than 3000MB seems to cause problems in the guest.

Thanks, that fixed it. I assumed (I know) that if I moved the slider anyplace with in the green it was OK, guess not.

Re: Win7 aborts when I try to run in VB

Posted: 4. Apr 2010, 08:22
by Entegy
I'd more be worried about what's taking up over 4GB of your memory unless you're running a crapload of programs at once.

Re: Win7 aborts when I try to run in VB

Posted: 6. Apr 2010, 22:45
by sundance2010
sundance2010 wrote:
rpmurray wrote:

Thanks, that fixed it. I assumed (I know) that if I moved the slider anyplace with in the green it was OK, guess not.
It didn't last long I afraid. It ran OK for a while but is doing the same thing again. Will start to run and shortly after the windows logo with the swirling colors shows it aborts. Here is the new log, I think. It shows Vbox.log, Vbox.log.1, Vbox.log.2 and so on. I assume Vbox.log.2 is the newest one?
It may be the memory and I don't know what is suing so much but in this case I have 2.7 (VB set to use 2.5) available and it still aborted.

00:00:01.261 VirtualBox 3.1.2 r56127 darwin.amd64 (Dec 17 2009 14:44:51) release log
00:00:01.261 Log opened 2010-04-04T04:29:43.810559000Z
00:00:01.261 OS Product: Darwin
00:00:01.261 OS Release: 10.3.0
00:00:01.261 OS Version: Darwin Kernel Version 10.3.0: Fri Feb 26 11:57:13 PST 2010; root:xnu-1504.3.12~1/RELEASE_X86_64
00:00:01.261 Host RAM: 8192MB RAM, available: 2776MB
00:00:01.261 Executable: /Applications/VirtualBox.app/Contents/MacOS/../Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
00:00:01.261 Process ID: 5494

Re: Win7 aborts when I try to run in VB

Posted: 6. Apr 2010, 23:06
by sundance2010
Think I have solved the memory issue and I hope the VB issue as well. In general I just put my Mac to sleep and almost never reboot. Once I rebooted I have over 6GB of free memory and Win7/VB seems to be running OK. :D

So I will have to change my practice of not shutting down the system and just putting it to sleep.

Re: Win7 aborts when I try to run in VB

Posted: 7. Apr 2010, 14:22
by rpmurray
sundance2010 wrote:Once I rebooted I have over 6GB of free memory and Win7/VB seems to be running OK.
Looks like you may have a memory leak in a program that you run on the Mac side. If you continue to have the problem, you should start up the Activity Monitor and sort the processes by Real Memory in descending order and keep an eye on it. Whatever is eating the memory should float to the top after a while.