VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1672 - 1674 of 16363)

Ticket Resolution Summary Owner Reporter
#5705 fixed VB consumes all CPU utilization and Ram on host Taz Higgins
Description

Running windows XP as the guest, windows vista as the host. The Host PC has an i7 and 8GB Ram

Virtual Box consumed increasing amounts of CPU Utilization on the Host while the guest was doing nothing. It reached over 80% utilization on a 4 cores of the host.

Virtual Box consumed increasing amounts of Ram on the Host while the guest was doing nothing, it grabbed over 6GB ram.

The guest OS was unusably slow when this happened

Closing down the guest session returned all my CPU and Ram to the host system.

#771 worksforme Got code to 'contact vendor' on VirtualBox tavis7g
Description

Hi,

I ran across Virtual Box and thought that I would give it a try. It worked just fine for my WinXP Pro (CDrom) and I was even able to play KNOPPLIX 3.4 (.iso) on it :D . Eventually, the (.iso) stopped loading along with a message of 'failed...' upon ignition :cry: (WinXP Pro still works fine). I've tried other .iso (Mandriva & FreeDOS) files but none worked after the KNOPPLIX 3.4 incident. So, I preformed a system recovery on my HP on Vista which is about 2 months old so that I could rule out options for what possibly could be wrong. Then, I set up the Virtual box and only loaded the .iso KNOPPLIX 3.4. Ths is the message that I got (below). In it, it requested that I contact the vendor and on the Virtual Box website, it requests that posts be made in forum as a first tactic. So, I did respond to forum. Then I read about here, so, here I am. I know not what the message means and would really appreciate any assistance. The message is just below....

Assertion failed: [VBOX_SUCCESS (vrc)] at 'E:\vbox\w32-rel\src\VBox\Main\MachineImpl.cpp' (4681) in Machine::openConfigLoader. VERR_OPEN_FAILED (-101) - File/Device open failed.. Please contact the product vendor!.

Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}

tavis

#955 fixed Incorrect snapshot handling in Linux (VERR_ALREADY_EXISTS) tautrimas
Description

This is how it happens:

  1. I create a snapshot of running Win XP client.
  2. I use the client, and when I finish my work, I simly push "revert to current snapshot".
  3. It works many times, but one day, after reverting it says "aborted".
  4. Then, when I try to revert again (after starting client up and playing a bit), it says:

Could not copy the state file '/home/tautrimas/.VirtualBox/Machines/WinXP/Snapshots/{b2ec225f-3158-4dde-d1a7-dd58663d6426}.sav' to '/home/tautrimas/.VirtualBox/Machines/WinXP/Snapshots/{02b3e0da-9713-46f2-8e88-3e0806fb9da6}.sav' (VERR_ALREADY_EXISTS).

Result Code: 0x80004005 Component: Machine Interface: IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}

  1. Virtual Disk Manager says, that there are currently 2 difference disks (each 60.50 KB in size) for my single snapshot.

Problem is, that I can't revert my snapshot back. Problem appeared second time in a week (after reinstall of VBox).

Linux system: Sabayon Linux 3.4f

USB and sound enabled.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy