VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (904 - 906 of 16363)

Ticket Resolution Summary Owner Reporter
#2657 fixed Floppy needs remounting for every diskette Dave
Description

Host XP-Home-SP3. VBox for DOS. Using DOS 6.22 and trying to install win3.1 from 5 floppies. Floppy drive Mounted OK. Run VBox and boot to DOS 6.22 on drive C: so far so good. Insert first win3.1 floppy and run setup, still fine. Setup asks for second floppy, I eject the floppy DISK1, insert Disk2, hit "Enter" as instructed by Setup and I get "Invalid media. Abort, Retry, Fail" At this point VBox hangs and I have to shut it down.

#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.

#16997 duplicate NEW Windows 10 Update version 1703 OS Build 15063.540 2017 Daveallw
Description

This afternoon 10th August 2017 Microsoft ran an automatic update to the version in the title.

Oracle Virtual Box is now classed as an Incompatible Program and will not even open. I have tried to run it in compatibility mode but nothing happens. I need this program so I can run my scanner software in XP in the box.

Any help will be most appreciated.

See screen shot on PC at https://www.facebook.com/photo.php?fbid=10214163526862382&set=p.10214163526862382&type=3&theater

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