Opened 17 years ago
Closed 17 years ago
#174 closed defect (fixed)
guest aborts
| Reported by: | scott | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.3.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Having an issue with XP guest when working in Corel Draw X3. XP will abort, I don't have a clue why. It maybe related to the amount of ram used, I have 836MB of base ram in Vbox with a total of 1024MB.It seems that the redraw is very slow at times. Is there a maxium amount of ram that Vbox can use? I have Xandros for a host. Thanks Scott
Attachments (1)
Change History (8)
follow-up: 2 comment:1 by , 17 years ago
comment:2 by , 17 years ago
Replying to klaus:
Maximum RAM for a VM is more than 1GByte for 1.3.6. However leaving just 188MByte for host OS is potentially too little and can be the cause for the trouble. The host OS, X11, libraries and VirtualBox need to fit in those 188MByte. Check for excessive paging on the host (which will greatly decrease the speed of VirtualBox). If possible attach the log file for the VM when it aborted (you can find it in ~/.VirtualBox/Machines/VMNAME/Logs/VBox.log), there might be some information about the reason of the abort in there.
Thanks I'll try tweaking the ram somemore.
follow-up: 4 comment:3 by , 17 years ago
I have this as well, in 1.3.8, Ubuntu Feisty Host, WinXP Guest.
It can run for long periods of time, the suddenly crash. I have attached a log file, that shows glibc - Corrupted memory.
The initial stuff gets written in the log at every startup, I don't think it is relevant to the crashes.
comment:4 by , 17 years ago
Replying to kenken:
I have this as well, in 1.3.8, Ubuntu Feisty Host, WinXP Guest.
It can run for long periods of time, the suddenly crash. I have attached a log file, that shows glibc - Corrupted memory.
The initial stuff gets written in the log at every startup, I don't think it is relevant to the crashes.
The samething happens in Xandros. I think it's an issue with how VBox handles the ram. It seems to happen only when you are doing some intensive things, ie graphics and such. I'm using VMware with no issues, it runs at near native speed.
comment:6 by , 17 years ago
I no longer get the Glibc error message in the log file, instead I see the errors reported in Ticket #367: http://www.virtualbox.org/ticket/367
comment:7 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Maximum RAM for a VM is more than 1GByte for 1.3.6. However leaving just 188MByte for host OS is potentially too little and can be the cause for the trouble. The host OS, X11, libraries and VirtualBox need to fit in those 188MByte. Check for excessive paging on the host (which will greatly decrease the speed of VirtualBox). If possible attach the log file for the VM when it aborted (you can find it in ~/.VirtualBox/Machines/VMNAME/Logs/VBox.log), there might be some information about the reason of the abort in there.