VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (226 - 228 of 16363)

Ticket Resolution Summary Owner Reporter
#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

#18620 fixed Module build fails on linux due to mistake in vboxnetadp/Makefile -> fixed in releases after 7 May 2019 Ambroz Bizjak
Description

In some circumstances (probably out-of-tree build), the vboxnetadp module fails to build with an error like this:

cc1: fatal error: /build/virtualbox-6.0.6-modsrc/include/VBox/SUPDrvMangling.h: No such file or directory

This is fixed by changing

VBOXMOD_CFLAGS = -include $(KBUILD_EXTMOD)/include/VBox/SUPDrvMangling.h -fno-pie -Wno-declaration-after-statement

to

VBOXMOD_CFLAGS = -include $(VBOXNETADPT_DIR)include/VBox/SUPDrvMangling.h -fno-pie -Wno-declaration-after-statement

in the vboxnetadp Makefile. It appears that this change was missed during refactoring of the makefiles in this commit: https://www.virtualbox.org/changeset/77394/vbox. One can easily see the problem by comparing this line with the equivalent lines in Makefiles of other modules.

#18621 fixed Failure to disable hardening in Linux kernel modules -> fixed in releases after May 8 2019 Ambroz Bizjak
Description

As of VirtualBox 6, there is a bug in the export of kernel module source code whereby if hardening was disabled with a configure flag, it is not actually disabled in VBoxNetAdp, VBoxNetFlt and VBoxPci (but is disabled in VBoxDrv). This seems to be the result of refactoring of makefiles and forgetting to update sed commands that remove the VBOX_WITH_HARDENING compile flag. I am attaching a patch.

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