VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1606 - 1608 of 16363)

Ticket Resolution Summary Owner Reporter
#12977 obsolete Hardware address conflict among Host and DHCP server in Host-only mode PeLo
Description

Enabled Host-only mode and activated DHCP server. Host and the guest got their respective IP's from the DHCP server. Address range was 10.1.2.1-20, DHCP server was assigned 10.1.2.1. Since there is no option to assign different IP's to DHCP server and the Host, both the DHCP server and the Host shared the same IP (10.1.2.1 in my case). The guest got 10.1.2.2.

The DHCP lease time for the guest was 20 mins. Soon after 20 mins, when the guest tries to renew its IP address, it broadcasts an ARP request for the hardware address of 10.1.2.1. A pair of ARP replies are seen in response. One from the Host itself and the other from the Virtual Host hosting the DHCP server. The original host gave out 0a:00:27:00:00:00 and the DHCP server gave out address in the Cadmus Corp range. The address of the original host came first and was cached by the guest. Subsequent DHCP renewal requests were being sent to the cached ARP address and since the original host was not actually hosting any DHCP service, ICMP error message are sent back to the guest.The cycle repeats endlessly with no success.

Not a major problem but creating unnecessary traffic between the Guests and the Host.

#5541 obsolete VMMR0.r0 expects C: drive to be the Windows System drive HexWizard
Description

I was getting the VERR_NO_MEMORY (can't remember exactly, but something like this) on starting VMs. I am using the Windows version of VirtualBox. I was getting an "unknown error" loading VMMR0.r0. Since I could not think of any reason why VMMR0.ro should fail to load, I took a guess that because my system drive is E: and not C:, perhaps that was the problem. I ran the command subst C: E:\ and that gas definitely resolved the problem.

Make VirtualBox more tolerant of non-C: system drives.

#909 fixed PCBSD: Bug while launching (Guru meditation selmgcGuestTSSWriteHandler) Hexade
Description

I've just installed the last BC-BSD operating system, as a FreeBSD OS.

The installation works fine but when launching the new OS, I got a critical error. It is not possible to launch PC-BSD 1.4.1 on VirtualBox 1.5.2 (host: Linux Fedora 2.6.23.1-49.fc8 x86_64).

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