[SOLVED] VirtualBox: WXP guest loses CIFS file system when real net cable unplugged
Linux - VirtualizationThis forum is for the discussion of all topics relating to Linux Virtualization. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
VirtualBox: WXP guest loses CIFS file system when real net cable unplugged
Hello
Here's the setup: VirtualBox 3.0.10 on Slackware 13.0 running WXP in a virtual machine with bridged adapter on eth0, an onboard RTL8111B. Host: 192.168.1.47, guest: 192.168.1.48, both static. Host runs samba including config
Code:
[home]
comment = Home directories
writable = yes
locking = yes
path = /home
public = no
The guest mounts "home" as D:. Has been working for a long time.
Here's the issue: when the real network cable is unplugged, D: is no longer connected.
Thoughts: is this normal? Do packets normally go out to the switch and come back when the host puts the NIC in promiscuous mode?
Best
Charles
Last edited by catkin; 02-10-2010 at 07:30 AM.
Reason: Comatose comma
This sounds right to me. When the cable is unplugged, the interface
goes down, so no traffic can go through it. I know there is a "host
only" networking option, although I can't remember what it is called.
You could set up a host only interface to connect between guest and
host, and it would work even when the network cable is unplugged.
I have several virtual machines that have two interfaces, one bridged
to the host adapter and the other host-only. That assures me that
the guest and host can connect no matter what else is going on with
the network.
I have several virtual machines that have two interfaces, one bridged
to the host adapter and the other host-only. That assures me that
the guest and host can connect no matter what else is going on with
the network.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.