VirtualBox

Changes between Initial Version and Version 6 of Ticket #2247


Ignore:
Timestamp:
Sep 16, 2008 7:22:04 AM (16 years ago)
Author:
Frank Mehnert
Comment:

Thanks for your findings. Are you 100% sure that this is a 2.0.0 regression?

To help debugging this problem you could do the following: Start the VM with 

gdb -args /usr/lib/virtualbox/VBoxHeadless -startvm testvbox1

When the guest does not respond anymore, force the process to terminate with a core dump. I've updated the instructions at ​http://www.virtualbox.org/wiki/Core_dump. Keep in mind to allow SUID root processes to dump core dumps and kill the process with -4 (as described there).

Send the core dump to frank _dot_ mehnert _at_ sun _dot_ com. If the compressed file is bigger than 4MB (very likely), try to make it available somehow for me for download (preferred) or use some file sharing service (megaupload.com, yousendit.com or similar).

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2247 – Description

    initial v6  
    1 I'm having a weird problem with VirtualBox 2. I'm trying to use it to
     1I'm having a weird problem with !VirtualBox 2. I'm trying to use it to
    22break my one server into two parts (the native server and a virtual
    33machine) and split services across the two. I'm using bridged HIF
    … …  
    2020My setup:
    2121
    22 - VirtualBox 2.0
    23 - A generic Pentium 4 box
    24 - Ubuntu Hardy Server as both the host and guest
    25 - No X servers on either the host or guest
    26 - Bridged HIF networking (both the host and guest are using static IPs)
    27 - I'm launching the virtual machine with "VBoxManage startvm
    28 testvbox1 -type vrdp".
     22 * !VirtualBox 2.0
     23 * A generic Pentium 4 box
     24 * Ubuntu Hardy Server as both the host and guest
     25 * No X servers on either the host or guest
     26 * Bridged HIF networking (both the host and guest are using static IPs)
     27 * I'm launching the virtual machine with {{{VBoxManage startvm testvbox1 -type vrdp}}}.
    2928
    3029
    3130More details:
    3231
    33 - I've tried "nohz=off" on both the host and guest and it doesn't help.
     32 * I've tried "nohz=off" on both the host and guest and it doesn't help.
    3433
    35 - When I see the problem, the CPU usage drops from 0.3% to 2% cpu load
    36 for the idle VM to not showing up in "top" most refreshes. So, the VM
    37 is definitely doing less.
     34 * When I see the problem, the CPU usage drops from 0.3% to 2% cpu load for the idle VM to not showing up in "top" most refreshes. So, the VM is definitely doing less.
    3835
    39 - The problem happens whenever I run the VM the first time after boot.
    40 Whether I run it as part of the boot scripts or wait a few minutes and
    41 run it by hand makes no difference. The second run always works
    42 right.
     36 * The problem happens whenever I run the VM the first time after boot. Whether I run it as part of the boot scripts or wait a few minutes and run it by hand makes no difference. The second run always works right.
    4337
    44 - The problem happens whether I run the headless frontend or the
    45 standard GUI frontend.
     38 * The problem happens whether I run the headless frontend or the standard GUI frontend.
    4639
    47 - This is weird: During the 2-3 minutes of "good" time before the VM
    48 goes all wonky, I ssh (with X forwarding) from my laptop into the VM
    49 and run a xterm so I can type commands to the VM and see what's going
    50 on. When the VM start misbehaving, I can still type commands to the
    51 VM, but the output stalls. For example, I type "ps ax" and hit enter
    52 it will print a few lines of result and then stop. If I then move the
    53 mouse into and out of the xterm, it will print a few more lines.
    54 It seems like the focus events that the laptop's X server sends to
    55 the VM cause it to wake up and do work. It's like the VM is dropping
    56 interrupts or something.
     40 * This is weird: During the 2-3 minutes of "good" time before the VM goes all wonky, I ssh (with X forwarding) from my laptop into the VM and run a xterm so I can type commands to the VM and see what's going on. When the VM start misbehaving, I can still type commands to the VM, but the output stalls. For example, I type "ps ax" and hit enter it will print a few lines of result and then stop. If I then move the mouse into and out of the xterm, it will print a few more lines. It seems like the focus events that the laptop's X server sends to the VM cause it to wake up and do work. It's like the VM is dropping interrupts or something.
    5741
    58 - A VRDP connection works fine for the "good" 2-3 minutes, but completely
    59 locks up when the VM goes wonky.
     42 * A VRDP connection works fine for the "good" 2-3 minutes, but completely locks up when the VM goes wonky.
    6043
    61 - Network connections to the host work fine through all of this.
     44 * Network connections to the host work fine through all of this.
    6245
    63 - This happens with VirtualBox 2.0.0 and 2.0.2
     46 * This happens with !VirtualBox 2.0.0 and 2.0.2
    6447
    65 - Thanks for reading all this. I'd be grateful for any help you guys
    66 could offer.
    67 
     48 * Thanks for reading all this. I'd be grateful for any help you guys could offer.
    6849
    6950Forum Thread:  http://forums.virtualbox.org/viewtopic.php?t=9590
    70 

© 2023 Oracle
Contact – Privacy policy – Terms of Use