Custom Query (16363 matches)
Results (1990 - 1992 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17913 | duplicate | documentation indicates (incorrectly) that NAT VM can't communicate with host over network -> duplicate of #16912 | ||
| Description |
https://www.virtualbox.org/manual/ch06.html#networkingmodes Table 6.1 "VM ↔ Host" column has a "–" symbol for NAT, which is misleading, as the guest VM is able to communicate over the network with the host, in fact bypassing the host's firewall (which, btw, seems like a security issue which should also be noted in the documentation, particular since NAT is the default); the guest VM, for example, can ping the host's IP. The host, however, can't ping the guest VM's IP. |
|||
| #11410 | fixed | documentation for KRDC wrong/outdated => Fixed in SVN | ||
| Description |
Chapter 7. Remote virtual machines / Common third-party RDP viewers (http://www.virtualbox.org/manual/ch07.html#rdp-viewers) contains some either wrong or outdated information about KRDC:
Regards Alex |
|||
| #10975 | wontfix | document which information from the host are visible to VMs | ||
| Description |
Please make one section with all information from the host, which are visible to the VM. Information like hardware serials, battery information, cpu features, cpu mhz, etc. Here are two examples, what I mean... acpi -V Battery 0: Full, 100% Battery 0: design capacity ..... Adapter 0: on-line Cooling 0: Processor 0 of 0 cat /proc/cpuinfo although Synthetic CPU hides a bit, mhz frequency is still visible Those are just two examples, where I am aware about it. It would be nice, if we had a list with all things, which are visible to the VM. |
|||

