Date: Thu, 1 Jul 2004 08:04:06 -0500 From: Sean Welch <Sean_Welch@alum.wofford.org> To: per@hedeland.org Cc: freebsd-emulation@freebsd.org Subject: Re: Patches to allow running multiple vmware3 instances Message-ID: <20040701130406.GA1134@NitroPhys.welchsmnet.net>
next in thread | raw e-mail | index | archive | help
THANK YOU! I've been wanting this feature for a very long time now. I abandoned vmware2 a while back and the lack of this particular feature has been severely limiting the usefulness of vmware3. I added in your patches and recompiled. I do indeed get multiple vmnet interfaces but I don't seem able to configure them as you show in your example. Specifically, I cannot configure the interfaces to be on the same subnet with the same netmask. I can have one but not the other... ??? Your example file suggests you used this (snip): vmnet1.Bridged = "NO" vmnet1.BridgeInterface = "" vmnet1.HostOnlyAddress = "172.31.254.1" vmnet1.HostOnlyNetMask = "255.255.255.240" vmnet2.Bridged = "NO" vmnet2.BridgeInterface = "" vmnet2.HostOnlyAddress = "172.31.254.17" vmnet2.HostOnlyNetMask = "255.255.255.240" My config file looks like this: vmware.fullpath = "/usr/local/lib/vmware/bin/vmware" wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard" dhcpd.fullpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd" loop.fullpath = "/usr/local/lib/vmware/bin/vmware-loop" libdir = "/usr/local/lib/vmware" vmnet1.Bridged = "NO" vmnet1.BridgeInterface = "" vmnet1.HostOnlyAddress = "172.19.20.40" vmnet1.HostOnlyNetMask = "255.255.255.0" vmnet2.Bridged = "NO" vmnet2.BridgeInterface = "" vmnet2.HostOnlyAddress = "172.19.20.41" vmnet2.HostOnlyNetMask = "255.255.255.0" The system complains with this message when attempting to configure the second instance: ifconfig: ioctl (SIOCAIFADDR): File exists Any ideas? I'd love to start using this right away! Sean > Hi, > > I just send-pr'ed some patches to allow running of multiple > networked > vmware3 instances: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=68532 > > The scheme isn't very elegant, since it uses one vmnet interface per > vmware instance, but if your needs aren't very "dynamic", I think > it's > OK. Only tested on 5.2.1-RELEASE, see the pr for some possible > issues on > other versions (it should be possible to create the vmnet devices > manually on non-devfs systems - *before* running the start > script...). > > --Per Hedeland > per@hedeland.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040701130406.GA1134>