Custom Query (16363 matches)
Results (604 - 606 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10778 | fixed | Unable to enter an odd value in the second character position of the Mac Address assignment field | ||
| Description |
Physical Host OS: Windows 7 Ultimate SP1 64-bit/x64
Description of Problem: Attempts to enter an odd value into the second position of the custom MAC address field will not enter, resulting in the red error message: "The value of the Mac Address field on the Network page is not complete" Entering 222222222222 will work, but 212222222222 will not. Attempts to change the second value to an odd number after entering all twos will fail. While this may not be a critical issue to most implementations, the inability to change the address to desired values completely defeats the purpose of the feature and should therefore be considered a severity value of at least 2 or at most 1.5 and should be hot-fixed ASAP. This would definitely impact certain applications of using Virtual Box to test network issues relating to MAC addresses which contain unassigned/spoofed/invalid values. While I have not tested whether this exists solely in the Windows GUI or if it also fails through VBoxManage, but based on the problem, I would take a well-educated guess that the problem is simply an invalid input validation mask for the "Mac Address:" input field in the GUI.
Recreation/Validation: Prerequisites:
Steps to recreate:
|
|||
| #15138 | duplicate | VirtualBox 5 stucks while starting virtual machine | ||
| Description |
Hello, I do have problems with virtualbox 5.0.14 on linux kernel 4.4. I experienced that some virtual machines stuck while starting. So I created a new virtual Machine(Linux Mint). It boots using a livecd-image and I can install Linux Mint. While shutting down the virtual machine ist stucks and the cpu runs on 100% (i attached screenshots of htop and vbox-log while it stucks). After killing the virtualbox-processes and starting the virtualmachine it stucks again. I tried an installation 2 times. It was always the same. |
|||
| #3906 | duplicate | wxp guest, ubuntu 9.04 host, network in guest doesnt work when network in host turned back on | ||
| Description |
this one is a bit tricky, but i've reproduced it a few times. its hard to reproduce, because i think the host network must be down a long time before its turned back on, a minute or two doesn't work. 20 hours does. i'm not sure where the threshold in between is. host ubuntu 9.04 amd64, NIC in AMD 780G chipset, ext4 guest plain vanilla wxp 32bit network PCnet-FAST III (NAT) this whole thing worked fine until i upgraded from ubuntu 8.10 amd64 on the same computer. at the same time i think i also upgraded vbox? not sure. here's the bug. i leave the vm running all the time. but i turn the network on and off on the host. when i turn the network back on after being off for A WHILE (not sure what the threshold is), then the vm can't access the network. i try software stuff inside windows, like repair connection, or disable then enable, and it doesn't work. i have to restart the windows machine. mabye if i wait another long while it will find the network, but i haven't tried. either way its still a bug, thats making me nuts :-). i'm going to try downgrading. |
|||

