Custom Query (16363 matches)
Results (1606 - 1608 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12977 | obsolete | Hardware address conflict among Host and DHCP server in Host-only mode | ||
| 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.
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 | ||
| 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) | ||
| 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). |
|||

