Also take a look at the output of this: Marcuss-MacBook-Pro:~ marcus$ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --status Password: NAT service on vmnet1 is running Hostonly virtual adapter on vmnet1 is enabled NAT service on vmnet8 is running Hostonly virtual adapter on vmnet8 is enabled All the services configured on all the networks are running
On Sat, Aug 31, 2013 at 8:05 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > Check your nat.conf files and verify that they have an ip and netmask > entry, bot the vmnet1 and vmnet8 ones, they tend to get switched back > automatically for some reason. > > /Library/Preferences/VMware\ Fusion/vmnet1/nat.conf > /Library/Preferences/VMware\ Fusion/vmnet8/nat.conf > > Marcuss-MacBook-Pro:~ marcus$ grep ip /Library/Preferences/VMware\ > Fusion/vmnet[18]/nat.conf > /Library/Preferences/VMware Fusion/vmnet1/nat.conf:ip = 172.17.10.1 > /Library/Preferences/VMware Fusion/vmnet8/nat.conf:ip = 192.168.100.1 > > Marcuss-MacBook-Pro:~ marcus$ grep netmask > /Library/Preferences/VMware\ Fusion/vmnet[18]/nat.conf > /Library/Preferences/VMware Fusion/vmnet1/nat.conf:netmask = 255.255.255.0 > /Library/Preferences/VMware Fusion/vmnet8/nat.conf:netmask = 255.255.255.0 > > Marcuss-MacBook-Pro:~ marcus$ ifconfig -a > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > options=3<RXCSUM,TXCSUM> > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > stf0: flags=0<> mtu 1280 > en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > ether 14:10:9f:d7:0b:13 > inet6 fe80::1610:9fff:fed7:b13%en0 prefixlen 64 scopeid 0x4 > inet 10.10.10.145 netmask 0xffffff00 broadcast 10.10.10.255 > media: autoselect > status: active > p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304 > ether 06:10:9f:d7:0b:13 > media: autoselect > status: inactive > vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > ether 00:50:56:c0:00:01 > inet 172.17.10.2 netmask 0xffffff00 broadcast 172.17.10.255 > vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > ether 00:50:56:c0:00:08 > inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 > > You may also have to change the IPs on your other VMs to go along with > these NAT subnets if you have others. > > On Sat, Aug 31, 2013 at 6:24 PM, Mike Tutkowski > <mike.tutkow...@solidfire.com> wrote: >> I notice when running ifconfig from my host (Mac OS X), I don't see any >> info on Fusion adapter: >> >> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >> options=3<RXCSUM,TXCSUM> >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >> inet 127.0.0.1 netmask 0xff000000 >> inet6 ::1 prefixlen 128 >> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 >> stf0: flags=0<> mtu 1280 >> en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4> >> ether 40:6c:8f:56:0e:27 >> media: autoselect (none) >> status: inactive >> en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> ether 7c:d1:c3:8f:e1:64 >> inet6 fe80::7ed1:c3ff:fe8f:e164%en1 prefixlen 64 scopeid 0x5 >> inet6 2600:100e:b006:5436:7ed1:c3ff:fe8f:e164 prefixlen 64 autoconf >> inet6 2600:100e:b006:5436:b47f:ebff:2b65:c03b prefixlen 64 autoconf >> temporary >> inet 192.168.1.12 netmask 0xffffff00 broadcast 192.168.1.255 >> media: autoselect >> status: active >> p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304 >> ether 0e:d1:c3:8f:e1:64 >> media: autoselect >> status: inactive >> fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078 >> lladdr 00:3e:e1:ff:fe:61:3c:5c >> media: autoselect <full-duplex> >> status: inactive >> >> >> >> On Sat, Aug 31, 2013 at 6:21 PM, Mike Tutkowski < >> mike.tutkow...@solidfire.com> wrote: >> >>> So, here is info from ifconfig: >>> >>> cloudbr1 Link encap:Ethernet HWaddr 52:54:00:52:B1:5E >>> inet addr:192.168.100.10 Bcast:192.168.100.255 >>> Mask:255.255.255.0 >>> inet6 addr: fe80::5054:ff:fe52:b15e/64 Scope:Link >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 b) TX bytes:6571 (6.4 KiB) >>> >>> This is my attempt to SSH in: >>> >>> mtutkowski-LT:~ mtutkowski$ ssh root@192.168.100.10 >>> ssh: connect to host 192.168.100.10 port 22: Operation timed out >>> >>> I've also noticed my XenServer VM that I run under Fusion is no longer >>> pingable. >>> >>> Always something, eh. :) >>> >>> Thanks for helping me out! >>> >>> >>> On Sat, Aug 31, 2013 at 6:14 PM, Marcus Sorensen <shadow...@gmail.com>wrote: >>> >>>> You may have to look into the VMware fusion vmnet commands, when I get a >>>> minute I'll take a look at mine, I remember it being kind of fickle. None >>>> of that should keep you from starting up a zone though. Does the 192.168 >>>> address work (Public)? You should be able to ssh in via that as well. >>>> On Aug 31, 2013 5:56 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> >>>> wrote: >>>> >>>> > All of my VNET_1 and VNET_8 lines are identical to the ones in the >>>> how-to >>>> > doc, if that helps. :) >>>> > >>>> > >>>> > On Sat, Aug 31, 2013 at 5:55 PM, Mike Tutkowski < >>>> > mike.tutkow...@solidfire.com> wrote: >>>> > >>>> > > I do get one prompt when starting that VM. >>>> > > >>>> > > This is the how-to doc I followed: Thanks! >>>> > > >>>> > > 1. install vmware fusion 5 >>>> > > >>>> > > 2. copy/move devcloud-kvm.vmwarevm into ~/Documents/Virtual\ Machines >>>> > > >>>> > > 3. edit /Library/Preferences/VMware\ Fusion/networking, switching >>>> vmnet1 >>>> > > to nat, adding addresses for the virtual interfaces, disabling dhcp: >>>> > > >>>> > > VERSION=1,0 >>>> > > answer VNET_1_DHCP no >>>> > > answer VNET_1_DHCP_CFG_HASH E6A9871BECB2D4190B4017A52E2E9915F5CB2D5B >>>> > > answer VNET_1_HOSTONLY_NETMASK 255.255.255.0 >>>> > > answer VNET_1_HOSTONLY_SUBNET 172.17.10.0 >>>> > > answer VNET_1_NAT yes >>>> > > answer VNET_1_VIRTUAL_ADAPTER yes >>>> > > answer VNET_1_VIRTUAL_ADAPTER_ADDR 172.17.10.2 >>>> > > answer VNET_8_DHCP no >>>> > > answer VNET_8_DHCP_CFG_HASH DDADDB2BB56F4411617D6EFB2F83F72B82BA7D38 >>>> > > answer VNET_8_HOSTONLY_NETMASK 255.255.255.0 >>>> > > answer VNET_8_HOSTONLY_SUBNET 192.168.100.0 >>>> > > answer VNET_8_NAT yes >>>> > > answer VNET_8_VIRTUAL_ADAPTER yes >>>> > > answer VNET_8_VIRTUAL_ADAPTER_ADDR 192.168.100.2 >>>> > > >>>> > > 4. Change the gateway address for vmnet8 in >>>> /Library/Preferences/VMware\ >>>> > > Fusion/vmnet8/nat.conf >>>> > > >>>> > > # NAT gateway address >>>> > > change ip line to "ip = 192.168.100.1" >>>> > > >>>> > > 5. Create /Library/Preferences/VMware\ Fusion/vmnet1/nat.conf >>>> > > >>>> > > cd /Library/Preferences/VMware\ Fusion >>>> > > mkdir vmnet1 >>>> > > cp vmnet8/nat.conf vmnet1 >>>> > > vi vmnet1/nat.conf >>>> > > >>>> > > change ip line to "ip = to 172.17.10.1" >>>> > > >>>> > > 6. Force the nat.conf files to stay the same, like so: >>>> > > chflags uchg /Library/Preferences/VMware\ Fusion/vmnet8/nat.conf >>>> > > chflags uchg /Library/Preferences/VMware\ Fusion/vmnet1/nat.conf >>>> > > >>>> > > 7. reboot to take effect, or maybe do: >>>> > > >>>> > > /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop >>>> > > /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start >>>> > > >>>> > > 8. start VM, log in via 'ssh root@172.17.10.10', follow instructions >>>> at >>>> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvmfrom >>>> > > section 'Building' >>>> > > >>>> > > >>>> > > >>>> > > On Sat, Aug 31, 2013 at 5:50 PM, Marcus Sorensen <shadow...@gmail.com >>>> > >wrote: >>>> > > >>>> > >> Oh, and VMware fusion should prompt twice for your password when the >>>> VM >>>> > >> starts, due to the bridges in the VM wanting promiscuous access. If >>>> you >>>> > >> don't enter your password it won't work. >>>> > >> On Aug 31, 2013 5:48 PM, "Marcus Sorensen" <shadow...@gmail.com> >>>> wrote: >>>> > >> >>>> > >> > Sounds like your Nat in VMware fusion isn't working. Did you see >>>> the >>>> > >> setup >>>> > >> > instructions in the archive? >>>> > >> > On Aug 31, 2013 4:38 PM, "Mike Tutkowski" < >>>> > mike.tutkow...@solidfire.com >>>> > >> > >>>> > >> > wrote: >>>> > >> > >>>> > >> >> From that KVM host, that is. :) >>>> > >> >> >>>> > >> >> >>>> > >> >> On Sat, Aug 31, 2013 at 4:37 PM, Mike Tutkowski < >>>> > >> >> mike.tutkow...@solidfire.com> wrote: >>>> > >> >> >>>> > >> >> > I don't seem to have access to the Internet. >>>> > >> >> > >>>> > >> >> > >>>> > >> >> > On Sat, Aug 31, 2013 at 4:25 PM, Mike Tutkowski < >>>> > >> >> > mike.tutkow...@solidfire.com> wrote: >>>> > >> >> > >>>> > >> >> >> Hey Marcus, >>>> > >> >> >> >>>> > >> >> >> Should I be able to ping 172.17.10.10 from my host OS (Mac OS >>>> X)? >>>> > >> >> >> >>>> > >> >> >> I would have thought so, but it times out. >>>> > >> >> >> >>>> > >> >> >> Any thoughts on that? I went back and double checked my >>>> settings >>>> > >> from >>>> > >> >> the >>>> > >> >> >> How-to doc. >>>> > >> >> >> >>>> > >> >> >> Thanks >>>> > >> >> >> >>>> > >> >> >> >>>> > >> >> >> On Fri, Aug 30, 2013 at 11:51 PM, Marcus Sorensen < >>>> > >> shadow...@gmail.com >>>> > >> >> >wrote: >>>> > >> >> >> >>>> > >> >> >>> You can update the system VM template by just downloading it >>>> and >>>> > >> >> >>> replacing >>>> > >> >> >>> whatever template is in /nfs/secondary/template/tmpl/1/3 with >>>> it, >>>> > >> just >>>> > >> >> >>> rename the new one to whatever uuid that one has and replace >>>> > it... >>>> > >> >> Before >>>> > >> >> >>> you bootstrap the zone. >>>> > >> >> >>> On Aug 30, 2013 11:48 PM, "Marcus Sorensen" < >>>> shadow...@gmail.com >>>> > > >>>> > >> >> wrote: >>>> > >> >> >>> >>>> > >> >> >>> > That all looks good... 172 on cloudbr0 is your mgmt >>>> interface. >>>> > >> >> 192.168 >>>> > >> >> >>> is >>>> > >> >> >>> > the public network that the vpcs/routers will live on. Now >>>> > Marvin >>>> > >> >> >>> should be >>>> > >> >> >>> > able to set up your zone if you install the rpms. I have >>>> > >> >> occasionally >>>> > >> >> >>> had >>>> > >> >> >>> > permission issues with the /var/lib/libvirtd directory, >>>> FYI, so >>>> > >> if >>>> > >> >> the >>>> > >> >> >>> VMS >>>> > >> >> >>> > don't come up you may want to look there. >>>> > >> >> >>> > >>>> > >> >> >>> > You may also need to update the system VM template in >>>> > >> >> /nfs/secondary/ >>>> > >> >> >>> ... >>>> > >> >> >>> > I don't remember if its the 4.2 one. >>>> > >> >> >>> > On Aug 30, 2013 11:38 PM, "Mike Tutkowski" < >>>> > >> >> >>> mike.tutkow...@solidfire.com> >>>> > >> >> >>> > wrote: >>>> > >> >> >>> > >>>> > >> >> >>> >> Hi, >>>> > >> >> >>> >> >>>> > >> >> >>> >> I am trying to set up devcloud-kvm and having a little >>>> > trouble. >>>> > >> >> >>> >> >>>> > >> >> >>> >> I am running it on VMware Fusion 5 (Mac OS X 10.8.3). >>>> > >> >> >>> >> >>>> > >> >> >>> >> I thought I followed all of the directions correctly, but I >>>> > >> don't >>>> > >> >> >>> have an >>>> > >> >> >>> >> IP address for eth0. >>>> > >> >> >>> >> >>>> > >> >> >>> >> Any thoughts on this? >>>> > >> >> >>> >> >>>> > >> >> >>> >> Thanks! >>>> > >> >> >>> >> >>>> > >> >> >>> >> [root@devcloud-kvm ~]# ifconfig >>>> > >> >> >>> >> >>>> > >> >> >>> >> cloudbr0 Link encap:Ethernet HWaddr 52:54:00:4E:FF:4F >>>> > >> >> >>> >> >>>> > >> >> >>> >> inet addr:172.17.10.10 Bcast:172.17.10.255 >>>> > >> >> >>> Mask:255.255.255.0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> inet6 addr: fe80::5054:ff:fe4e:ff4f/64 Scope:Link >>>> > >> >> >>> >> >>>> > >> >> >>> >> UP BROADCAST RUNNING MULTICAST MTU:1500 >>>> Metric:1 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX packets:0 errors:0 dropped:0 overruns:0 >>>> frame:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> TX packets:55 errors:0 dropped:0 overruns:0 >>>> > carrier:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> collisions:0 txqueuelen:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX bytes:0 (0.0 b) TX bytes:7734 (7.5 KiB) >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> cloudbr1 Link encap:Ethernet HWaddr 52:54:00:52:B1:5E >>>> > >> >> >>> >> >>>> > >> >> >>> >> inet addr:192.168.100.10 Bcast:192.168.100.255 >>>> > >> >> >>> >> Mask:255.255.255.0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> inet6 addr: fe80::5054:ff:fe52:b15e/64 Scope:Link >>>> > >> >> >>> >> >>>> > >> >> >>> >> UP BROADCAST RUNNING MULTICAST MTU:1500 >>>> Metric:1 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX packets:0 errors:0 dropped:0 overruns:0 >>>> frame:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> TX packets:39 errors:0 dropped:0 overruns:0 >>>> > carrier:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> collisions:0 txqueuelen:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX bytes:0 (0.0 b) TX bytes:6571 (6.4 KiB) >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> eth0 Link encap:Ethernet HWaddr 52:54:00:4E:FF:4F >>>> > >> >> >>> >> >>>> > >> >> >>> >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX packets:0 errors:0 dropped:0 overruns:0 >>>> frame:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> TX packets:0 errors:0 dropped:0 overruns:0 >>>> carrier:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> collisions:0 txqueuelen:1000 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> eth1 Link encap:Ethernet HWaddr 52:54:00:52:B1:5E >>>> > >> >> >>> >> >>>> > >> >> >>> >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX packets:0 errors:0 dropped:0 overruns:0 >>>> frame:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> TX packets:0 errors:0 dropped:0 overruns:0 >>>> carrier:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> collisions:0 txqueuelen:1000 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> lo Link encap:Local Loopback >>>> > >> >> >>> >> >>>> > >> >> >>> >> inet addr:127.0.0.1 Mask:255.0.0.0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> inet6 addr: ::1/128 Scope:Host >>>> > >> >> >>> >> >>>> > >> >> >>> >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX packets:36 errors:0 dropped:0 overruns:0 >>>> frame:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> TX packets:36 errors:0 dropped:0 overruns:0 >>>> > carrier:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> collisions:0 txqueuelen:0 >>>> > >> >> >>> >> >>>> > >> >> >>> >> RX bytes:2520 (2.4 KiB) TX bytes:2520 (2.4 KiB) >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> >>>> > >> >> >>> >> -- >>>> > >> >> >>> >> *Mike Tutkowski* >>>> > >> >> >>> >> *Senior CloudStack Developer, SolidFire Inc.* >>>> > >> >> >>> >> e: mike.tutkow...@solidfire.com >>>> > >> >> >>> >> o: 303.746.7302 >>>> > >> >> >>> >> Advancing the way the world uses the >>>> > >> >> >>> >> cloud<http://solidfire.com/solution/overview/?video=play> >>>> > >> >> >>> >> *™* >>>> > >> >> >>> >> >>>> > >> >> >>> > >>>> > >> >> >>> >>>> > >> >> >> >>>> > >> >> >> >>>> > >> >> >> >>>> > >> >> >> -- >>>> > >> >> >> *Mike Tutkowski* >>>> > >> >> >> *Senior CloudStack Developer, SolidFire Inc.* >>>> > >> >> >> e: mike.tutkow...@solidfire.com >>>> > >> >> >> o: 303.746.7302 >>>> > >> >> >> Advancing the way the world uses the cloud< >>>> > >> >> http://solidfire.com/solution/overview/?video=play> >>>> > >> >> >> *™* >>>> > >> >> >> >>>> > >> >> > >>>> > >> >> > >>>> > >> >> > >>>> > >> >> > -- >>>> > >> >> > *Mike Tutkowski* >>>> > >> >> > *Senior CloudStack Developer, SolidFire Inc.* >>>> > >> >> > e: mike.tutkow...@solidfire.com >>>> > >> >> > o: 303.746.7302 >>>> > >> >> > Advancing the way the world uses the cloud< >>>> > >> >> http://solidfire.com/solution/overview/?video=play> >>>> > >> >> > *™* >>>> > >> >> > >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> -- >>>> > >> >> *Mike Tutkowski* >>>> > >> >> *Senior CloudStack Developer, SolidFire Inc.* >>>> > >> >> e: mike.tutkow...@solidfire.com >>>> > >> >> o: 303.746.7302 >>>> > >> >> Advancing the way the world uses the >>>> > >> >> cloud<http://solidfire.com/solution/overview/?video=play> >>>> > >> >> *™* >>>> > >> >> >>>> > >> > >>>> > >> >>>> > > >>>> > > >>>> > > >>>> > > -- >>>> > > *Mike Tutkowski* >>>> > > *Senior CloudStack Developer, SolidFire Inc.* >>>> > > e: mike.tutkow...@solidfire.com >>>> > > o: 303.746.7302 >>>> > > Advancing the way the world uses the cloud< >>>> > http://solidfire.com/solution/overview/?video=play> >>>> > > *™* >>>> > > >>>> > >>>> > >>>> > >>>> > -- >>>> > *Mike Tutkowski* >>>> > *Senior CloudStack Developer, SolidFire Inc.* >>>> > e: mike.tutkow...@solidfire.com >>>> > o: 303.746.7302 >>>> > Advancing the way the world uses the >>>> > cloud<http://solidfire.com/solution/overview/?video=play> >>>> > *™* >>>> > >>>> >>> >>> >>> >>> -- >>> *Mike Tutkowski* >>> *Senior CloudStack Developer, SolidFire Inc.* >>> e: mike.tutkow...@solidfire.com >>> o: 303.746.7302 >>> Advancing the way the world uses the >>> cloud<http://solidfire.com/solution/overview/?video=play> >>> *™* >>> >> >> >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkow...@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the >> cloud<http://solidfire.com/solution/overview/?video=play> >> *™*
