Custom Query (16363 matches)
Results (163 - 165 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8273 | worksforme | Can't make VBox accept ssh connections | ||
| Description |
I am following instructions from http://mydebian.blogdns.org/?p=148 I have ran this script: GUEST="Solaris10_9-10" VBoxManage setextradata $GUEST "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/HostPort" 2222 VBoxManage setextradata $GUEST "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/GuestPort" 22 VBoxManage setextradata $GUEST "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/Protocol" TCP After reboot I am getting an error, see the attached screenshot. |
|||
| #8283 | invalid | Solaris 10 guest prints warnings in WIn7 host which itself is a guest in FreeBSD host | ||
| Description |
Win 7 guest runs fine under VBox on FreeBSD host. But Solaris 10 appliance (from oracle.com) on such Win 7 guest prints such warning: -- begin error -- WARFNING: /pci@0,0/pci8086,2829@d/disk@0,0 (ds0):
-- end error -- Same Solaris 10 appliance doesn't give this warning on MacOS or FreeBSD hosts. After this warning it proceeds to installation, and after installation prints similar warning again and hangs. |
|||
| #8297 | obsolete | VM doesn't get connected to network when it wasn't up during VM startup | ||
| Description |
I use VBox on laptop which isn't always connected to wireless. When guest is started during period when wifi was down it can't ever connect even when the host already has wifi. So that I have to restart the guest in order to get it connected. Network connectivity of the guest shouldn't depend of the state of network on the host during guest startup. |
|||

