Hey Jeff, It looks like you have not filled in your mac address information for your virtual machine. Vmware likes a particular format for this. Try 00:50:56:2A:3B:00 for eth0macaddress and 00:50:56:2A:3B:01 for eth1macaddress.
The field "IPaddress" corresponds to the "public" address. Though, I don't think this will matter here. A public IP address typically will be generate for your machine. Try a reservation with the mac addresses and see if that fixes this. You may have already done these steps but I thought I would add them to be safe: You should have an entry for your virtual machine in your /etc/hosts file. (ex. 10.75.144.15 csuvm15). You should also have an entry in your dhcpd.conf file as well for each virtual machine. Hope this helps, Patrick On Feb 8, 2010, at 12:14 AM, Jeffrey Wisman wrote: > We're now at the point where we can create reservations and virtual machines > get loaded with images. The issue we're having is that the virtual machines > come up on their private IP addresses only. The reservation screen shows > the private IP and the RDP file has that IP in it. We have the virtual > machines configured with two interfaces - one on the private network for VCL > admin stuff, and the other on the public network where we have the campus > DHCP server configured to give it an IP. However, it doesn't seem to be > working, or at least if it is getting a public IP, VCL isn't telling us what > it is. > > I'm wondering if the issue is in the database. Each virtual machine has an > "IPaddress" and a "privateIPaddress". On our virtual machines, they are set > to the same thing. Here is an example: > > mysql> select * from computer; > +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+-------+------------+-----------+---------+-----------------------+-----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+ > | id | stateid | ownerid | platformid | scheduleid | currentimageid | > preferredimageid | nextimageid | imagerevisionid | RAM | procnumber | > procspeed | network | hostname | IPaddress | > privateIPaddress | eth0macaddress | eth1macaddress | type | > provisioningid | drivetype | deleted | notes | lastcheck | location | dsa | > dsapub | rsa | rsapub | host | hostpub | vmhostid | vmtypeid | > +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+-------+------------+-----------+---------+-----------------------+-----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+ > <snip> > | 24 | 2 | 1 | 1 | 1 | 4 > | 0 | 0 | 0 | 512 | 1 > | 2000 | 1000 | csuvm15 | 10.75.144.15 | > 10.75.144.15 | NULL | NULL | virtualmachine > | 4 | hda | 0 | NULL | NULL | NULL | NULL > | NULL | NULL | NULL | NULL | NULL | 1 | NULL | > > > Should one be NULLed out or set to something else? Should we put all the > private entries in the /etc/hosts file of the VMWare management server? > Currently I haven't done that, but read it in one of the posts here. Any > other ideas? > > Thanks, > Jeff
