Custom Query (16363 matches)
Results (2335 - 2337 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2395 | fixed | VirtualBox failing when a virtual machine is started at boot -> fixed in 2.0.4 | ||
| Description |
Hi, I have a strange problem: I have a recent (2.0.2 PUEL) version of VirtualBox installed on a very up-to-date ubuntu 8.4 Hardy host. I have a specialized Linux version (IPCop 1.4.21) as guest; this is based on a 2.4.36 kernel. This virtual machine acts as firewall for the host and for the rest of my home network. It works (I'm using it to write this!). The strangeness begins if and when I start this virtual machine with USER=$VBOXUSER LOGNAME=$VBOXUSER start-stop-daemon --start --quiet --background --make-pidfile --pidfile $PIDFILE --name VBoxHeadless --chuid $VBOXUSER --startas /usr/bin/VBoxHeadless -- -s IPCop -a $VRDPADDR -p $VRDPPORT from within one of the startup scripts (I do attach the complete script along with the /etc/network/interfaces file I use to setup the bridges). If I do this the firewall machine starts ok and works (I can ssh into the machine and the whole firewall does work), but VirtualBox does not work ok anymore. Symptoms are:
I saw another, apparently similar bug that concerned the SDL libraries, but I do not think it is relevant here. I also tried to move the start of the Virtual Machine to the very end of the boot sequence (S95vbox-ipcop in /etc/rc2.d), but nothing changed. The behavior is very repetitive.
What did I do wrong? |
|||
| #2396 | duplicate | VirtualBox failing when a virtual machine is started at boot | ||
| Description |
Hi, I have a strange problem: I have a recent (2.0.2 PUEL) version of VirtualBox installed on a very up-to-date ubuntu 8.4 Hardy host. I have a specialized Linux version (IPCop 1.4.21) as guest; this is based on a 2.4.36 kernel. This virtual machine acts as firewall for the host and for the rest of my home network. It works (I'm using it to write this!). The strangeness begins if and when I start this virtual machine with USER=$VBOXUSER LOGNAME=$VBOXUSER start-stop-daemon --start --quiet --background --make-pidfile --pidfile $PIDFILE --name VBoxHeadless --chuid $VBOXUSER --startas /usr/bin/VBoxHeadless -- -s IPCop -a $VRDPADDR -p $VRDPPORT from within one of the startup scripts (I do attach the complete script along with the /etc/network/interfaces file I use to setup the bridges). If I do this the firewall machine starts ok and works (I can ssh into the machine and the whole firewall does work), but VirtualBox does not work ok anymore. Symptoms are:
I saw another, apparently similar bug that concerned the SDL libraries, but I do not think it is relevant here. I also tried to move the start of the Virtual Machine to the very end of the boot sequence (S95vbox-ipcop in /etc/rc2.d), but nothing changed. The behavior is very repetitive.
What did I do wrong? |
|||
| #2397 | fixed | VBoxMouse segfaults when starting up the X Server => fixed in SVN | ||
| Description |
When I start KDM, the X Server segfaults and exits. The stack trace shows an entry in vboxmouse_drv.so; see the attached log file for details. |
|||

