Custom Query (16363 matches)
Results (712 - 714 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2270 | fixed | Large page problems for RedHat 5 guest applications | ||
| Description |
I am running VirtualBox 2.0.2 32-bit on Windows XP SP3 with an Intel Core2 Duo T7300 CPU. I installed RedHat Enterprise Linux (actually oracle Enterprise Linux which is a rebadged version) with kernel version 2.6.18-92. Linux detects the HugePageSize as 4 Mb (as per cat /proc/meminfo) which is incorrect; it should be 2 Mb (this works correctly under VMware). Asa result, several pieces of software that use large pages do not work correctly. Since the page size is detected properly when installed on real hardware and also within VMware on the same host it would seem this is due to some issue with VirtualBox. I have tried with both software and hardware virtualisation but it behaves thesame. |
|||
| #2332 | worksforme | RedHat 5 64-bit install crashes VirtualBox 2.0.2 | ||
| Description |
I am running 64-bit VirtualBox 2.0.2 on a 64-bit machine running 64-bit Vista Business SP1. I am trying to install RedHat Enterprise 5 Update 2 (actually Oracle Enterprise Linux 5 which is simply a rebadged version of RedHat). Part way through the install, VirtualBox crashes. I have run this a ferw times and each time it fails, but at different points. I have attached the VM settings file, the machine log file and the image (.png) file. |
|||
| #8614 | duplicate | Damage to .vbox file for first VM renders all VMs inacessible and VM Manager empty | ||
| Description |
I have 4 VMs con figured. They are all configured similarly to the attached .vbox file. I had a situation where for unexplained reasons (subject of much discussion but no conclusion as yet) the .vbox file for the first VM that I had defined becamed 'damaged'. By this I mean that three of the 'HardDisk' entries in the 'MediaRegistry' section were removed. The relevant entries for these disks were still present in the 'AttachedDevice' section at the end of the file. When I opened the VBox GUI, all 4 VMs were shown as 'inacessible', even though there was no problem with the .vbox files for the other three VMs, and when I opened the Virtual Media Manager that also showed as 'empty' (i.e. no media was listed). I have performed some experiments and have confirmed the following:
This behaviour isn't very nice. A problem with the .vbox file for the first defined VM should not have any impact on other VMs nor on the Virtual Media Manager. |
|||

