Custom Query (16363 matches)
Results (1195 - 1197 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7424 | obsolete | Guru Meditation (pPage->enmKind != PGMPOOLKIND_FREE) | ||
| Description |
VirtualBox told me to report this crash. The title is line from log, after that the situation happened. Occurred during slipstream phase of DriversPack. Using VirtualBox on this machine (Notebook Compaq 6720s, Ubuntu 9.10) is quite unstable. Sometime guest freeze, sometime host freeze or restart itself without any message. |
|||
| #7427 | obsolete | Kernel panic when starting F5 Big-IP (not syncing: Fatal exception) | ||
| Description |
I spun up an F5 Big-IP trial VM on VirtualBox. It can be found here: https://www.f5.com/trial/. It's designed to run on VMWare. The disk I use is the original VMDK that comes from F5. I've set up a virtual machine with PIIX4, I/O APIC. Base memory is 1GB, network interfaces are PCNet-II. This all matches the VMWare setup. Upon boot, after Loading udev, I get "Kernel panic - not syncing: Fatal exception" The interesting part is that this does not happen always. If you allow the VM to auto-reboot, eventually it will load successfully. This makes me think that we may have some sort of race condition here. I am assuming at this point that it has something to do with attaching the storage devices from /etc/fstab, though I do not know this for certain. The one thing I can see that is slightly unusual is that /etc/fstab uses UUIDs, not /dev/hda references. This should be easy to reproduce by downloading the F5 trial and using the attached machine XML. |
|||
| #7431 | obsolete | With 2 GB guest RAM VirtualBox is twenty times slower than with 700 MB RAM | ||
| Description |
Steps to reproduce:
I get output like this: Creating 1000 objects... Done in 0.026094316000000003 seconds. Writing to test.ser... Done in 0.23731131500000002 seconds. Reading from test.ser... Done in 7.03051558 seconds. Checksum: -406759103 The 7 seconds for reading the file is an enormously long time. If I change the virtual machine's RAM size to 700 MB and and repeat points 3-6 then I get the following, much better time: Creating 1000 objects... Done in 0.017042552000000002 seconds. Writing to test.ser... Done in 0.11916187800000001 seconds. Reading from test.ser... Done in 0.36389537600000005 seconds. Checksum: -884318403 Increasing the object count in the test program increases run time proportionally, e. g. for "java SerTest 10000 100 0" the times are 70 seconds and 3 seconds for 2 GB RAM and 700 MB RAM, respectively. The host is 64-bit Windows 7 with 4 GB RAM and Intel Core2 Duo E6400 processor. |
|||

