Custom Query (16363 matches)
Results (946 - 948 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1614 | fixed | Missing Run Level shortcuts with generic Linux .RUN install => Fixed in 1.6.2 | ||
| Description |
I have installed VB three times, using the generic Linux .RUN installer. I noticed that the VirtualBox kernel driver and networking are not initialized in run level 2, which is the default run level in Debian. I'm using "testing" and "unstable", so the pre-packaged Debian binaries for "stable" are not usable for me. Symbolic links S20vboxdrv -> ../init.d/vboxdrv S20vboxnet -> ../init.d/vboxnet are installed in /etc/rc3.d/ and /etc/rc5.d/ but not /etc/rc2.d/ which is the Debian default run level. Please consider putting the symbolic links into Run Levels 2 through 5. People who know enough to alter their run level will know to delete these symbolic links if they do not want those drivers to be active. Sadly, it took me a while to figure out why VirtualBox would give me an error when I first started my machine, but work once I "rebuilt" the driver. The initial installation and subsequent driver "rebuilds" all occurred in Run Level 2, which I must assume your installer does not check before creating the symbolic links. |
|||
| #1615 | fixed | insufficient guest time synchronisation (in 1.5.6 was OK) | ||
| Description |
Hello VirtualBox programmers, 1.6.0 time synchronisation of the guest system is insufficient. In version 1.5.6 it worked absolutely sufficient. Background: we (industry OEM, paying for VirtualBox licences) are using a data acquisition program as VirtualBox guest (host=Win XP(e), guest = Win XPe). Using VirtualBox 1.5.6 time synchronisation is fine, the acquired trend data do not show any interruption. After updating to VirtualBox 1.6.0 (for test purposes) we get an unusable time delay of the guest machine. The time delay of the guest is resynchronised after some minutes, but the data trend lines aquired every second get an interruption when automatic resync is done. We need a guest time differing less than one second of the host time! This is a killer criterion for our future using of VirtualBox! martl |
|||
| #1619 | fixed | Assertion Failed to release the client -> Fixed in 2.1.2 | ||
| Description |
When powering off a vm an assertion was thrown by VBoxVRDP 41:29:57.892 VRDP: TCP server failed to send data to the client!!! Disconnecting the client. 41:29:57.892 VRDP: Failed to release the client. Status 0x2, Context 0x2!!! 41:29:57.892 41:29:57.892 !!Assertion Failed!! 41:29:57.892 Expression: <NULL> 41:29:57.892 Location : /home/vbox/vbox-1.5.6/src/VBox/RDP/server/vrdpclient.cpp(340) void VRDPClient::ThreadContextRelease(int) This put the machine into an aborted state and could not be recovered by a VBoxManage controlvm <vmname> poweroff|reset because the VBoxVRDP process had executed and there was no current session. I had to manually change the aborted="true" value in the vm .xml file to reset this state. What is the correct method from recovering from aborts such as these? Manually having to edit the xml file is a sloppy. |
|||

