Hi Kiran,
Do your vmprofile adapter names virtualswitch0 and virtualswitch1 match
the adapters listed on your esx server?
Aaron
On 4/12/10 3:11 PM, Kiran N wrote:
hello Josh,
I am facing some what similar issue.I have added a new computer host(virtual
machine).
I checked the dhcp.conf
Yes.. it does match!
In this installation, the visrtualswitch0 is the public port and
virtualswitch1 is private. They are named exactly same as the virtual
machine configuration..
Thanks,
Kiran
On Tue, Apr 13, 2010 at 9:23 AM, Aaron Peeler aaron_pee...@ncsu.edu wrote:
Hi Kiran,
Do your
In addition to the previous email, the base Windows 2003 image does power on
and take the network settings in the correct manner(seen in VI client).
When I try to make a reservation on this image, the new virtual machine gets
powered on but is unable to detect the networkname or devname.
I checked
On 4/13/10 9:38 AM, Kiran N wrote:
In addition to the previous email, the base Windows 2003 image does power on
and take the network settings in the correct manner(seen in VI client).
On the working vm. Is this the initial vm guest that you created?
When I try to make a reservation on
Yes.. its the initial vm created..
Please find the files are attached with the emal..
Thanks,
Kiran
On Tue, Apr 13, 2010 at 10:03 AM, Aaron Peeler aaron_pee...@ncsu.eduwrote:
On 4/13/10 9:38 AM, Kiran N wrote:
In addition to the previous email, the base Windows 2003 image does power
on
In your assigned vmprofile. What is your vmtypeid set to? It should be
set to id 5 which is 'vmwareESX3'
The vcl generated vmx file is creating EthernetX.vnet instead of
EthernetX.networkName.
Aaron
On 4/13/10 10:25 AM, Kiran N wrote:
Yes.. its the initial vm created..
Please find the
Yes, change the vmtypeid to 5 and try to load the image again through vcl.
-A
On 4/13/10 11:02 AM, Kiran N wrote:
It is set to 3 , since as discussed with my co worker Brian Copcea, it says
it is ESX provisioning but practically the most of the provisioning scheme
is GSX with few added ESX
Thanks Vinay, Aaron for the help!
I tried changing it to 5 and now.. it does recognize the 2 networks( as seen
in VI client) in the correct manner. It shows the public IP address, but no
private IP address.
Also, in the vcld.log, it still shows the message:
2010-04-13 10:23:35|15069|35:35|reload|
Hi Andy (and anyone else following along here). I've been doing a lot of
poking around, and, long story short, I can now (for the first time ever)
successfully book and log into the Windows image (yay!) but, annoyingly, only
with a single one of the vm guest computers I've configured.
While
