Virtual Machines
-
Low On Memory Error: Server 2016, B series
I just spun up a brand new Standard B1ms (1 vcpu, 2 GB memory), all I did was login to the VM and am getting out of memory errors (which would tell me windows server 2016 doesn't really support this level of VM size). Also it fails to retrieve updates - this is just a plain vanilla OOB/first run experience. Additionally you can't login and click the start button - you have to click it about 10 times to get the menu to pop up - this is probably more of a windows issue but I'd expect it to at…
17 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Improve Portal Message for Availability Set allocation errors
If there is an allocation error when restarting a deallocated VM, the following error message is logged:
“Failed to start virtual machine 'xyc'. Error: Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.”If there is an allocation issue when creating a new machine the following message is displayed:
“New-AzureRmVM : Unable to create the VM because the requested size StandardF4 is not available in the cluster where the availability set is currently allocated. The available sizes are: StandardDS1v2,StandardDS2_v2…11 votes -
The virtual machines of the B series do not inform about the bandwidth. All series report about bandwidth except type B machines. Accordin
The virtual machines of the B series do not inform about the bandwidth.
All series report about bandwidth except type B machines.
According to Microsoft they do not inform because it is a variant connection, but at least they should indicate the minimum and maximum.
As in all series in the NIC part, the bandwidth must also appear.
10 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Report VM Status and PowerState More Accurately
VM Status and PowerState are not always reported correctly. Often a VM which has been running for hours or days will report Status=RoleStateUnkown or PowerState=Starting (even though it is clearly Started).
Please work to make this reporting more accurate. Thank you!
9 votes -
Creating a Low Priority VMSS using Portal has FD count bug
When creating a VMSS with Low Priority, FaultDomain Count is set to 5 by default.
"spreadingAlgorithmPlatformFaultDomainCount": {
"value": "5"Obviously this is a bug, because Low Priority VMSS only supports Single Fault Domain
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priorityIf we go with the default value, we got FD count error.
Deployment failed. Correlation ID:
{
'error': {'code': 'InvalidParameter',
'message': 'The value of parameter platformFaultDomainCount is invalid.',
'target': 'platformFaultDomainCount'}
}I think this needs to be fixed in Portal Front-end side.
5 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
storing vmSize with the exactly the same capitalization independently how VM was created
VmSize is stored with the capitalization how it was called during creation (v2 <> V2).
VM with v2
az vm create -n clitest1 -g SAP --image UbuntuLTS --size StandardD13v2az vm show -g SAP -n clitest1 -d
"hardwareProfile": {
"vmSize": "Standard_D13_v2"VM with V2
az vm create -n clitest2 -g SAP --image UbuntuLTS --size StandardD13V2az vm show -g SAP -n clitest2 -d
"hardwareProfile": {
"vmSize": "Standard_D13_V2"It causes additional data cleaning necessary during azure data analyzes.
Please correct
thanks
István5 votes -
Modify Set-AzureRmVMDiagnosticsExtension cmdlet to improve the ability to automate the install/config of diagnostics exten
Remove the dependency to have the virtual machine unique ID inside XML configuration file. To automate the install/config of a hundred VMs you would need to customize a hundred XML files. See attached document fo further explanation
5 votes -
I can not set up automatic backup of SQL Server 2016 on a portal with a language setting other than English
When deploying the image of SQL Server 2016 with the portal in Japanese language setting and setting automatic backup, the deployment parameter is set to Japanese and an error occurs at the time of expansion.
If you set the portal language setting to English, the correct parameters are set and you can deploy.
backupScheduleType : 手動 → Manual
fullBackupFrequency: 週単位 → WeeklyEven in languages other than English, I would like you to pass the correct parameters at deployment time.
4 votes -
Improve image gallery replication to other region
image replication to other region fail or limited to 1
Code="ReplicationJobsNotCompleted" Message="The replication job has not completed at region: 'eastasia'. You can try to reduce the number of the target regions when you first create the gallery image version, then update the gallery image version by adding more target regions.
3 votesValid suggestion subject to upvote
-
Update Disk count in VM Selection to match documented maximums
Available Data Disk is showing incorrect number during VM creation size selection versus documented data disk availabilities.
3 votes -
Posible Bug when create a new VM with powershell
When I create a Linux VM with PS, whith a migrated vhd between suscriptions, the machine is created correctly but:
1) Name of the Machine don't appear in 'General Information'
2) Connect button is in grey (inactive)
Machine is working ok, and we can connect to it with putty, but these two elements are not ok.3 votes -
SharePoint 2013 Non-HA Template Doesn't work
Twice today I have tried to use the SharePoint 2013 Non-HA Template and it has failed both times. Once when it was trying to create the domain controller and the second time when it was trying to create the SQL Server.
Can this template be fixed ?
3 votes -
3 votes
-
Failed to reset the password/ssh key
Can't reset ssh key and password for virtual machine.
Similar problem: http://stackoverflow.com/questions/31004642/azure-failed-to-reset-the-password-ssh-key-for-virtual-machine3 votes -
Getting Duplicate search results for "Windows Virtual Desktop - Provision a host pool"
Getting Duplicate results coming for the following keyword in azure portal
Azure portal -> Create Resource -> type "Windows Virtual" in "Search the Marketplace" search box
"Windows Virtual Desktop - Provision a host pool"
2 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
New SQL Server Resource Provider not idempotent?
It seems that the new Microsoft.SqlVirtualMachine/SqlVirtualMachines resource provider is not idempotent when deployed from an ARM template. Every first deployment succeeds and yields the expected results, but subsequent deployments time out on the Microsoft.SqlVirtualMachine/SqlVirtualMachines resource after > 2 hours.
Currently, the workaround is to move this resource to a separate template which is kicked off only once, but obviously that's not ideal. Am I missing something, or is this a bug and should the Microsoft.SqlVirtualMachine/SqlVirtualMachines be idempotent?
2 votes -
Usernames longer than 14 are not valid, but allowed to be created in new VM wizard.
When creating a new VM from the portal, an admin user name greater than 14 characters can be created, but it is not valid. The result was I could not remote into the VM as the user credentials were rejected. It wasn't until I went and tried to reset the password did I receive the validation error that the username I had selected was too long. I had to delete the VM and recreate it with a shorter username before I could RDP into the new Virtual Machine.
2 votes -
Allow machines without a public IP to go outbound to the internet when in the same group as one machine with a Standard Public IP SKU
When you have the following configuration:
1 HA Group
1 Machine with Standard public Sku
N number of machines with no public IP assigned.The machines with no public IP cannot go to the internet. MS support tell me this is a feature.
This works differently to the following:
1 HA Group
1 Machine with BASIC public Sku
N number of machines with no public IP assigned.All of the machines in this group can go outbound to the internet.
2 votes -
Set-AzureRmVMBootDiagnostics has no effect
The Set-AzureRmVMBootDiagnostics PowerShell cmdlet returns without an error, however, the boot diagnostics for a VM does not appear to change.
Also, the documentation for the Set-AzureRmVMBootDiagnostics cmdlet specifies the ResourceGroupName is the resource group of the VM, however, the cmdlet only works when the resource group of the storage account is used.
2 votes -
Choose WDDM or TCC mode during New Azure VM setup process
For NV and NC instances, users should be given a choice at the point of VM creation to enable TCC or WDDM mode on the Nvidia Tesla GPU.
2 votes
.png){kind=link}
- Don't see your idea?