My setup/config: Host-system: Running Win 7 (64-bit Enterprise edition) absolutely latest patches
Virtualbox: 64-bit rel 4.3.10 build 93012 Network config: Host-only network, NIC: Paravirtualized Host-only adapter Guest-system: CentOS 6.4 (64-bit) stripped-down minimalistic server package (we use it extensively on physical hardware without issues) Within my guestOS, I see only "lo" (loopback) and "virbr0" (for the libvirt based host-only network). "virbr0" has the host-only gateway-less subnet "192.168.122.0/24". Problem statement: My reading of the documentation for host-only networking is that IP communication between multiple guest VMs on the same host, is possible, and also IP communication between host and guest VM's is possible. However, even with ssh-daemon running/configured, using putty(ssh-client on Windows) to try to login to guestVM on 192.168.122.100 (what was assigned to guest by DHCP), doesn't seem to work. Of course, I can create a 2nd interface (eth0) as NAT/bridged, but I wanted to double-check if my assumption about capabilities of host-only network are incorrect, about host <--> guestVM comm? thanks, BD ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
