VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2317 - 2319 of 16363)

Ticket Resolution Summary Owner Reporter
#2245 fixed Virtualbox 1.6.x - 2.0 black screen when starting any VM netoor
Description

When starting any (Ubuntu, FreeDos, Windows) virtual machine (either bootable iso image or vdi file) in VirtualBox on Ubuntu 8.04.1 there is only black screen displayed and the VM doesn't start at all. In 1.6.x vesrions a gray background of the bootable image could be seen when it's stopped, in 2.x it's all black. VirtualBox is installed from deb package successfully but isn't working.

PC configuration:

  • Intel based motherboard i945G, 1GB, Celeron 2530MHz, S-ATA 80GB, integrated graphics. OS: Ubuntu 8.04.1 (russian)

Threads on the forum, that I've tried with no success (for example IO APIC support,e etc):

#2246 fixed Seamless: Some windows invisible -> fixed in 3.0.6 Matěj Gottwald
Description

Host system: Windows Vista x86 SP1 Guest system: Ubuntu 8.04 VirtualBox version: 2.0.2 Guest Additions version: 2.0.2 AMD-V enabled

When I turn the Seamless Mode on, some applications (especially those included in the system itself like Nautilus, Disk manager etc.) simply don't bring up any window - no window is shown. The window is visible only in case another window, which can be shown, appears under the invisible window. Or let me put it this way - the visible window acts as desktop or screen and the "invisible" window is shown only within its boundaries.

Screenshot enclosed.

#2247 fixed VM Lock-Up after 300 seconds host uptime => Fixed in 2.0.4 Ken Preslan
Description

I'm having a weird problem with VirtualBox 2. I'm trying to use it to break my one server into two parts (the native server and a virtual machine) and split services across the two. I'm using bridged HIF networking, so the setup should look like two different machines.

The problem I'm seeing is that the virtual machine works fine for a while (2-3 minutes), and then it becomes unresponsive. The VM's CPU usage goes way down and the VM doesn't reliably talk to the network or through VRDP. In the end I have to do a "VBoxManage controlvm testvbox1 poweroff" to get rid of the VM.

The weird thing is the problem only occurs the first time I run the VM after I reboot the physical machine. After I see the problem and stop the VM, I can restart it and it works fine from then on -- until I reboot the host again.

Any suggestions?

My setup:

  • VirtualBox 2.0
  • A generic Pentium 4 box
  • Ubuntu Hardy Server as both the host and guest
  • No X servers on either the host or guest
  • Bridged HIF networking (both the host and guest are using static IPs)
  • I'm launching the virtual machine with VBoxManage startvm testvbox1 -type vrdp.

More details:

  • I've tried "nohz=off" on both the host and guest and it doesn't help.
  • 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.
  • 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.
  • The problem happens whether I run the headless frontend or the standard GUI frontend.
  • 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.
  • A VRDP connection works fine for the "good" 2-3 minutes, but completely locks up when the VM goes wonky.
  • Network connections to the host work fine through all of this.
  • This happens with VirtualBox 2.0.0 and 2.0.2
  • Thanks for reading all this. I'd be grateful for any help you guys could offer.

Forum Thread: http://forums.virtualbox.org/viewtopic.php?t=9590

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