VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (991 - 993 of 16363)

Ticket Resolution Summary Owner Reporter
#6566 obsolete not great CPU loading until run second virtual machine Alpx
Description

While one guest runing in idle mode, VirtualBox process loads CPU in some percent (5-10). After start second virtual machine even without installed some OS, VirtualBox process reduce CPU load to 1-2%. See attached screen.

#6572 obsolete Able to add two identical DVD images, resulting in inaccessible VM with no error message Jamie Jackson
Description

Somehow, I was able to get into a situation where I had two identical attached CD images. This resulted in an "inaccessible" VM, with *no* error message to guide me to the problem/fix.

I was managing the VM via the GUI.

Here is the offending config snippet:

      <StorageController name="IDE Controller" type="PIIX4" PortCount="2">
        <AttachedDevice passthrough="false" type="DVD" port="0" device="0">
          <Image uuid="{aa281874-fdb0-421e-2194-7d0a4816598f}"/>
        </AttachedDevice>
        <AttachedDevice passthrough="false" type="DVD" port="0" device="1">
          <Image uuid="{aa281874-fdb0-421e-2194-7d0a4816598f}"/>
        </AttachedDevice>
      </StorageController>

This corresponds to the vbox guest additions DVD image:

  <Image uuid="{aa281874-fdb0-421e-2194-7d0a4816598f}" location="/usr/share/virtualbox/VBoxGuestAdditions.iso"/>

I'm not completely sure what I did to get in this situation, and don't have time to reproduce it, but here's what I think was the sequence.

  1. Removed IDE and floppy controller, and started XP VM (with just the sata controller/vdi).
  2. Shut down VM.
  3. Added IDE controller, with the "Host Drive" first, and the vbox guest additions image second. Also added floppy controller with a floppy image.
  4. Started VM and clicked "install guest additions" via the menu.
  5. Shut down VM.
  6. Shut down/restarted GUI?
  7. GUI showed the inaccessible VM, with no error in the error box.

Removing both duplicate attached devices from the XML config yielded an accessible VM, and I was back in business.

#6583 obsolete Contention for host CPU can trigger high host CPU usage for idle Guest Adam Tilghman
Description

Environment:

Host: CentOS 5.4 (1.8Ghz P4 non-VMX CPU; kernel: redhat 2.6.18-164.15.1.el5)

Guest: CentOS 5.4 (kernel: 2.6.18-164.15.1.el5)

The guest's tick rate is set to 100hz (verified via "getconf CLK_TCK" on guest). VBox USB is disabled. The guest is configured to be completely idle after boot: after startup,the only non-kernel processes running are "udev" and "sshd".

Description:

Once the guest finishes bootup, its CPU sits idle, and as expected, "VBoxHeadless" consumes less than 10% of the host CPU.

After some time, however, VBoxHeadless CPU usage jumps to ~50% and permanently remains at that level, even though from the guest's perspective the CPU remains idle. (See attached graph of host CPU usage).

When starting the guest VM 'nice +20', I can trigger the unexpected behavior simply by loading down the host CPU with other work.

Without the 'nice', a SIGSTOP/sleep 60/SIGCONT on the VM process will also cause the permanent jump in CPU usage.

The VBox.log entries show a missed timer catch-up at precisely the point where CPU usage jumps higher. I wonder if the high CPU usage is due to a bug in the VBox timer emulation code?

I can provide a shell login on the host and guest to interested developers, and I'm happy to supply the guest VM files if desired.

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