Custom Query (16363 matches)
Results (1939 - 1941 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16430 | obsolete | DHCP server netmask issue | ||
| Description |
I found an issue in the Virtualbox DHCP server and it's configuration interface. Since the command line help does not specify the netmask format for the add command, we used it with the bitcount format, like: VBoxManage dhcpserver add --netname int-cp --ip 192.168.54.1 --netmask 24 --lowerip 192.168.54.32 --upperip 192.168.54.40 --enable The command is accepted, but when using it, a very strange netmask is given in the DHCP offer to the VM: 96.223.171.3. This is not even a legal netmask. See the attached packet capture for the details. When using the dhcpserver add command with decimal netmask number (255.255.255.0) it works as expected. If bitcount netmask format is not accepted, the command shall fail. A listing or similar inquiry operation would be great for the DHCP servers, since now you can only add/modify/remove them. Maybe this issue would be also visible in such listing output. P.S.: an interesting addition to the story is that on RHEL linux type of guests there were a recently fixed issue in the ipcalc command (provided by the initscripts rpm), which is used by the dhclient command. The issue caused that the mentioned random netmask was accepted and the client bound itself to the given IP address with a /32 netmask. |
|||
| #16428 | fixed | Restoring snapshots does not work for Multi-processor VMs | ||
| Description |
I encountered a serious issue in Vbox 5.1.51 (compiled from source, cloned from git 25 Jan 2017), inside a Vbox VM I have Win7x64 SP1 running, everything works fine, I do a snapshot and shut down the OS. If I restore the snapshot and start the Vbox VM, the following error occurs: cpum#1: X86_CPUID_FEATURE_EDX_HTT is not supported by the host but has already exposed to the guest [ver=17 pass=final] (VERR_SSM_LOAD_CPUID_MISMATCH).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
This only happens with VMs with more than one CPU. If I discard the snapshot I can start the machine with two CPU without a problem. If I se t it to one CPU, the snapshots are working. The Vbox app is running inside an Ubuntu 16.04.1LTS which is running inside VMware Worksation VM(details below). VBox running inside an:
running inside a VM from:
|
|||
| #16427 | invalid | As a guest, must hold keyboard key a second or more | ||
| Description |
VBox 5.1.14 installed on Windows 10 with Linux 6 Guest. When working with the guest any key must be held down approximately a second or more to be recognized. |
|||

