Qemu-img convert -f raw -O vpc -o subformat=fixedĪlso tested both with and without "force_size" to maintain alignment. To test newer version of QEMU I resized the original raw and converted to vhd on Arch Linux using QEMU 2.7 using this command: image initially built to raw (and then vhd) on Debian Jessie.I have retired with auto creation since, but to avoid polluting the azure account I just took note of their names for re-use. The nic, vnet and subnet were originally auto-created by the first vm-create that failed. Then this is the problematic part (that goes forever and eventually fails): azure vm create -u -p -location "AustraliaEast" -g "" "" -Q -f -F -P 10.0.0.0/8 -j -k 10.0.0.0/24 -o -y linux Here's the commands that I'm using: azure storage blob upload -k -a įWIW the storage account used is in the same resource group as the Is there a list of common issues somewhere that i could work through?Īny help would be deeply appreciated! Thanks in advance. Is there somewhere within Azure (or an undocumented debug switch for azure-cli) that I can get more detailed error messages? So how do I troubleshoot what my issue is? Regardless, surely it shouldn't be this hard!? I have a fair bit of experience working with AWS and Linux, but basically none with Azure. azure-cli is not giving any useful error messages just something like "provisioning failed". When I try to provision the server it takes ages (literally hours) chugging away and then eventually fails. The upload goes fine and I have already worked around a few issues (like the vhd file extension being removed by Azure) but now I'm stuck. I am also using the newer "Resource Manager" mode (as opposed to the old "Classic" one). I am using azure-cli (why you would write a commandline client in NodeJS blows my mind, but that's a whole other story.!). I don't have access to MS HyperV so I have only tested it locally in VirtualBox. waagent installed, configured and the server has been "deprovisioned".grub has been tweaked as per requirements (as per ).a single bootable primary partition (no swap) that use all of the space on the VHD (some sources note that this is a requirement).no LVM (again some sources say that it is supported, others say it's not).VHD is in VPC format and aligned to 1 MB.static VHD file (some sources suggest that dynamic ones are supported, but some say they're not).I have tried to err on the side of caution to reduce or eliminate possible causes of issue. According to my research (and the MS docs I've read) it meets the Azure Linux VHD requirements. I have built a customised Debian (Jessie/8) VHD which I am trying to get running on Azure.
0 kommentar(er)
