VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1432 - 1434 of 16363)

Ticket Resolution Summary Owner Reporter
#17592 fixed Entering curly brackets does not work in Turbo Pascal -> fixed in 5.2.10 Turbo Pascal
Description

I have installed the following in a virtual machine:

MS-DOS 6.22 Turbo Pascal 7.0

Keyboard layout is Finnish.

When using the Turbo Pascal IDE, it is impossible to enter curly brackets by pressing the AltGr + 7 keys. This key combination works correctly in MS-DOS Edit, but not in Turbo Pascal IDE.

#17586 invalid Not able to create Host only network adapter ManiJ
Description

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005) Component: HostNetworkInterfaceWrap Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

#17584 fixed DNS server IP 0.0.0.0 not propagated to guest VM in NAT mode -> fixed in 5.2.10 DaveU8282
Description

In a Linux host's /etc/resolv.conf, it is possible to define an entry representing a DNS server running on the local host:

nameserver 127.0.0.1

In this case, a VirtualBox VM with a virtual network interface in NAT mode will see an IP in the NAT network provided in place of 127.0.0.1, thus making it possible for the VM to use the host's local DNS server. For instance, if 10.0.0.2 is assigned to the VirtualBox host and 10.0.0.3 is assigned to the guest, the guest would see 10.0.0.2 in the DNS resolver list.

However, an equivalent construct:

nameserver 0.0.0.0

which also represents the local Linux host, is not correctly handled by VirtualBox NAT. In this case, the VM will see 0.0.0.0 in the DNS server list which is not NATted to the host. This results in a broken DNS resolver entry. If there is no other nameserver in the resolver list, DNS lookups will fail, or if there are additional nameservers in the list, DNS lookups will be delayed due to the lame 0.0.0.0 DNS server entry.

This has been observed with a Windows 10 guest but it's expected that other guests would see the same issue.

Proposed solution: handle 0.0.0.0 exactly like 127.0.0.1 by NATting it to the NAT IP for the Linux host.

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