VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2323 - 2325 of 16363)

Ticket Resolution Summary Owner Reporter
#11020 obsolete Error installing VirtualBox on Win XP nofish
Description

Please see thread:

https://forums.virtualbox.org/viewtopic.php?f=6&t=51855

Install log is attached. If I can help with more info let me know. Thanks.

#11024 obsolete Reproducable crashes with VNC LBurmeister
Description

At least with VBox 4.1.22_OSEr80657 (with FreeBSD VNC hack) and 4.2.0_OSE (with integrated VNC server) it's possible to crash a VM running Windows XP SP3 when the desktop is viewed via the integrated VNC server: pid 80484 (VBoxHeadless), uid 1002: exited on signal 11. So far I was unable to get a crash dump. The log file is attached but doesn't show anything. The crash is NOT reproduceable when interacting directly with the VM (starting and using it by the qt4 GUI) or when connecting to the Windows integrated RDP server (NOT the VBox RDP server).

To reproduce:

  1. Start a Windows XP SP3 VM and install Mozilla Firefox into it. The crash will happen after some websurfing. Good ways to "force" a crash are typing things into the google.com searchbar or heavy scrolling. A very crash prone URL is http://superuser.com/questions/84995/how-to-enable-multiple-processors-on-xp-sp-3
  1. A more reliable way is to connect by VNC to the VM and log into the Windows RDP server (the remote desktop) while the VNC session is still running. Chances are high that VBox will crash immediately.
#11027 obsolete Unable to connect to SQL Server 2012 client via ODBC from host Ambrose
Description

I have MS Access 2010 on the Windows 7 VirtualBox host, which connects fine to every other SQL Server in the workgroup except the SQL Server 2012 installed on the VirtualBox Windows 7 guest.

No other Windows 7 MS Access 2010 machine in the workgroup can connect to this VirtualBox guest version of SQL Server 2012 either, but they can connect to other SQL Servers installed in exactly the same way on non-virual Windows 7 machines using the same ODBC drivers.

I installed Access 2010 on this aforementioned VirtualBox guest and it works just fine with the local version of SQL Server 2012 on the same guest.

I am using the VirtualBox 4.2 bridged networking type with all the defaults. I can connect network drives on the guest and transfer data from the guest, no problem. Only SQL Server ODBC has any trouble connecting to this host (SQL Server error 10060) and the same driver connects fine to other hosts.

Oh, and SQL Server 2012 "Allow External Connections' is 'Yes', TCP/IP and Named Pipes are enabled for the clients, and the firewall is off for the guest. Doesn't work whether the SQL Server Browser Service' is on or off, and there's no reason this should matter with only one instance of SQL Server on the default port, 1433.

This is truly bizarre, everything works fine except an ODBC connection to the guest Windows 7 SQL Server 2012

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