Soporte técnico de la comunidad de Azure
Formule preguntas, obtenga respuestas y comuníquese con los ingenieros de Microsoft y los expertos de la comunidad de Azure
Foro de MSDN
Respuesta de Microsoft a las preguntas técnicas sobre Azure
Auto-shutdown did not work on Win 10 VM
Forum: Azure Virtual Machines
Forum: Azure Virtual Machines
Virtual machine RDP is not working on Mac OSX for guest account
Forum: Azure Virtual Machines
Increasing Azure VM Spot price
Forum: Azure Virtual Machines
42
Votos
MS Learn/ Sandbox Creation Error
Forum: Azure Virtual Machines
32
Votos
Forum: Azure Virtual Machines
27
Votos
Multiple IP addresses for a VM to be able to use Multiple HTTPS endpoints
Forum: Azure Virtual Machines
26
Votos
Azure VMs no longer see themselves via public virtual IP
Forum: Azure Virtual Machines
73
Respuestas
MS Learn/ Sandbox Creation Error
Forum: Azure Virtual Machines
51
Respuestas
VM becomes unresponsive or disk becomes read-only
Forum: Azure Virtual Machines
42
Respuestas
Question about deploying multiple VMs with template
Forum: Azure Virtual Machines
37
Respuestas
Forum: Azure Virtual Machines
StackOverflow
Respuestas de la comunidad a las preguntas de desarrollo
37
Votos
32
Votos
Serverfault
Respuestas de la comunidad a las preguntas de administración de Sys/Net
15
Votos
10
Votos
Comentarios de Azure
¿Tiene alguna idea o sugerencia basada en su experiencia con Azure?
Create VM basing on parameters of one existing vm
From PowerShell GitHub repo: https://github.com/Azure/azure-powershell/issues/11989. It will be nice that New-AzVM supports creating VM basing on an existing VM within on cmdlet.
Support create VM from unattached disk in Portal
Support create VM from unattached disk in Portal Why it's only supported with script? https://docs.microsoft.com/en-us/azure/virtual-machines/scripts/virtual-machines-windows-powershell-sample-create-vm-from-managed-os-disks
Documentation: Updating CUDA drivers on N-Series VMs
We encountered a driver mismatch issue with the preinstalled CUDA drivers on N-series VMs (cuDNN 7.0 vs. CUDA 9.0). And upgrading to newer versions took some time due to confusing N-series driver setup documentation that led us down the wrong path. Drivers in VM image should be updated (to cuDNN 7.4 and CUDA 10.0) and docs should be updated to provide better guidance for setting up drivers. Documentation: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup
[VM Scale Set] Cannot create more than one Microsoft.Azure.Extensions.CustomScript for Ubuntu
Only one custom script can be attached to Ubuntu VMSS Agent Pool, need the ability to add more than one custom script to Ubuntu VMSS.
5172
Votos
Virtual machine console access
There is no VMConnect capability for console access to the VM as there is with Hyper-V. So in the situation where I lost connectivity, by misconfiguration, or system failure, is there only one very time and bandwith consuming way to fix it - download the VHDs on-premise, boot it in Hyper-V and VMConnect to repair VM, then upload all GBs back to the Azure... I requesting console access, also with ability to mount some image for repair and boot from it (as we do it in standard environment).
1435
Votos
VM Created from custom image should be able to select storage account for VHD
When we try to create a virtual machine from a custom image the VHD's for the new virtual machine are created in the same storage account as the custom image. This is not ideal because most customers have different environments in different subscriptions so they are forced to copy the image into storage account in each subscriptions. It is not easy to copy the images between the storage accounts either.
1418
Votos
Add the ability to rename a VM. The VM name is what appears in Azure, not the DNS name. Changing a VM's name should not affect the VM in any way. If you need a unique identifier for a VM that does not change, I suggest using a GUID rather than the VM's name in Azure.
1201
Votos
Live migrate the VMs during maintenance/hardware failures
Right now Azure VM customers experience very frequent restarts that impact the availability of services. As far as I know, these restarts are mostly caused by either host upgrades or hardware failures. Developing a HA setup is pretty straightforward for some scenarios (web servers), complex (database back-ends, notably MySQL) or extremely difficult (back-end applications used by our accounting department, for instance, which were designed to be run on one machine). Of course, HA setups are necessary for any major applications, but most of the setups we see have lots of single-instance roles (and for good reason most of the times). Currently, if you don't have an HA setup, machines are restarted about once per month or even more frequent (some as often as weekly). If this restart occurs during business hours, then this means downtime. Furthermore, for services like MySQL or SQL Server, this also means that the entire buffer pool is emptied and the performance of the application is degraded until the buffer pool fills up again. What we would love to have is something like Google Cloud's Live Migration - the VM would be moved to another host in case of hardware failures or host upgrades without restarts or downtime.
Azure VM limits should be visible on VM Overview page graphs
In a support case I found one of my VMs was being throttled because it was over disk write limit; the performance (other colors, not red) and limits (in red) should be on the graphs on the overview. This seriously impacts availability when VMs are being throttled and makes for an insidious and hard to understand issue. All performance limits should be visible! Please implement?
For the maintenance that doesn't require a reboot, customers can know it only through Scheduled Events API. https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-and-updates?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json#maintenance-that-doesnt-require-a-reboot Several customer requests easier way to grasp the affected resources and that history (e.g. dashboard).
Currently if you want to change the VM Size of Azure, VM is restarted. VM Resize shouldn't require downtime and it should be done in the backend. As CPU and RAM is still throttle when we use more resources then why can't we just remove the throttling limit and inform customer that VM is resized from A to D series when request is raised of resize?
The target resources affected by planned maintenance
When a planned maintenance is executed, the details and impacted resources are announced toward administrator by mail. I would like to check the target affected resources other methods exept mail.