"Warning : VMName is not supported in the Windows Azure Emulator in role 'WorkerRole1'"

Question

I have a WorkerRole and I am trying to use the vmName attribute is the cscfg file;
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<ServiceConfiguration xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="2" osVersion="*" serviceName="AzureDeploymentProject">
<Role name="WorkerRole1" vmName="vma">
<Instances count="2"/>
When I run it up with the following ;
"C:\Program Files\Microsoft SDKs\Windows Azure\Emulator\csrun.exe" /run:"C:\Users\john\workspace-azure\AzureRunMeOutside\deploy\WindowsAzurePackage.cspkg";"C:\Users\john\workspace-azure\AzureRunMeOutside\deploy\ServiceConfiguration.cscfg" /usefullemulator
I get the following error;
"Warning : VMName is not supported in the Windows Azure Emulator in role 'WorkerRole1'."
Does this mean that the ComputeEmulator does not support use of the vmName attribute, or am I doing something wrong.

Answer 1

Hi Jambor.
Thanks for the reply.
I am using Compute Emulator 2.3:
c:\Users\john\workspace-azure\AzureRunMeOutside\emulatorTools>"C:\Program Files\Microsoft SDKs\Windows Azure\Emulator\cs
run.exe"
Windows(R) Azure(TM) Desktop Execution Tool version 2.3.0.0
for Microsoft(R) .NET Framework 4.0
Copyright © Microsoft Corporation. All rights reserved.
Use "csrun /?" for command-line syntax.
c:\Users\john\workspace-azure\AzureRunMeOutside\emulatorTools>
and SDK 2.3 and I still get this warning. Am I using the correct namespace/version for the configuration?
xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration"
Where is the vmName registered, and how can I get access to it?
If I use the following, the DNS name is not registered in my standard DNS ( I am using Windows 7 Pro SP1 x64 and the machine is outside a Windows Domain, using a corporate DNS server ). Is there some 'Compute Emulator' DNS that I need to lookup, or do I
have to set the DNS part of the Role Endpoints to point to my local DNS server? In the cloud Azure provides DNS services Azure
Name Resolution (DNS), is there any Compute Emulator equivalent?
private void printOutInterestingInfo()
Tracer.WriteLine("Hostname is " + Dns.GetHostName(), "Information");
foreach (var endpoint in RoleEnvironment.CurrentRoleInstance.InstanceEndpoints)
string variable = endpoint.Key;
string value = endpoint.Value.IPEndpoint.Port.ToString();
string ipAdress = endpoint.Value.IPEndpoint.Address.ToString();
try
IPHostEntry hostEntry = Dns.GetHostEntry(ipAdress);
string machineName = hostEntry.HostName;
Tracer.WriteLine("\tEndpoint "+variable+": Machine name: " + machineName, "Information");
catch(Exception e)
Tracer.WriteLine("\tEndpoint "+variable+": Machine name is not available for ipAdress: "+e, "Information");
Tracer.WriteLine("\tEndpoint "+variable+": IP Address: " + ipAdress, "Information");
Tracer.WriteLine("\tEndpoint " + variable + ": Port: " + endpoint.Value.IPEndpoint.Port, "Information");
foreach (var role in RoleEnvironment.Roles)
foreach (RoleInstance roleInstance in role.Value.Instances)
Tracer.WriteLine("Role: " + roleInstance.Role.Name, "Information");
Tracer.WriteLine("\tInstance: " + roleInstance.Id, "Information");
foreach (RoleInstanceEndpoint roleInstEndpoint in roleInstance.InstanceEndpoints.Values)
Tracer.WriteLine("\t\tInstance endpoint IP address and port: " + roleInstEndpoint.IPEndpoint, "Information");
Information: MU: 2014-09-02 10:36:42Z Hostname is mu
A first chance exception of type 'System.Net.Sockets.SocketException' occurred in System.dll
Information: MU: 2014-09-02 10:36:46Z Endpoint Debugging: Machine name is not available for ipAdress: System.Net.Sockets.SocketException (0x80004005): No such host is known
at System.Net.Dns.InternalGetHostByAddress(IPAddress address, Boolean includeIPv6)
at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
at WorkerRole.RunMe.printOutInterestingInfo() in c:\Users\john\git\AzureRunMe\WorkerRole\RunMe.cs:line 355
Information: MU: 2014-09-02 10:36:46Z Endpoint Debugging: IP Address: 127.255.0.0
Information: MU: 2014-09-02 10:36:46Z Endpoint Debugging: Port: 8091
A first chance exception of type 'System.Net.Sockets.SocketException' occurred in System.dll
Information: MU: 2014-09-02 10:36:51Z Endpoint http: Machine name is not available for ipAdress: System.Net.Sockets.SocketException (0x80004005): No such host is known
at System.Net.Dns.InternalGetHostByAddress(IPAddress address, Boolean includeIPv6)
at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
at WorkerRole.RunMe.printOutInterestingInfo() in c:\Users\john\git\AzureRunMe\WorkerRole\RunMe.cs:line 355
Information: MU: 2014-09-02 10:36:51Z Endpoint http: IP Address: 127.255.0.0
Information: MU: 2014-09-02 10:36:51Z Endpoint http: Port: 81
A first chance exception of type 'System.Net.Sockets.SocketException' occurred in System.dll
Information: MU: 2014-09-02 10:36:55Z Endpoint http-alt: Machine name is not available for ipAdress: System.Net.Sockets.SocketException (0x80004005): No such host is known
at System.Net.Dns.InternalGetHostByAddress(IPAddress address, Boolean includeIPv6)
at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
at WorkerRole.RunMe.printOutInterestingInfo() in c:\Users\john\git\AzureRunMe\WorkerRole\RunMe.cs:line 355
Information: MU: 2014-09-02 10:36:55Z Endpoint http-alt: IP Address: 127.255.0.0
Information: MU: 2014-09-02 10:36:55Z Endpoint http-alt: Port: 8081
The thread 0x2504 has exited with code 259 (0x103).
The thread 0x1728 has exited with code 259 (0x103).
Information: MU: 2014-09-02 10:37:09Z Endpoint telnet: IP Address: 127.255.0.0
Information: MU: 2014-09-02 10:37:09Z Endpoint telnet: Port: 24
Information: MU: 2014-09-02 10:37:09Z Role: WorkerRole
Information: MU: 2014-09-02 10:37:09Z Instance: deployment23(267).AzureRunMe.WorkerRole_IN_0
Information: MU: 2014-09-02 10:37:09Z Instance endpoint IP address and port: 127.255.0.0:8091
Information: MU: 2014-09-02 10:37:09Z Instance endpoint IP address and port: 127.255.0.0:81
Information: MU: 2014-09-02 10:37:09Z Instance endpoint IP address and port: 127.255.0.0:8081
Information: MU: 2014-09-02 10:37:09Z Instance endpoint IP address and port: 127.255.0.0:24
outputs;