How to troubleshoot Azure with custom Debian VHD; error message “provisioning failed”?Do I create a fixed...

Check if a string is entirely made of the same substring

Where was the County of Thurn und Taxis located?

"The cow" OR "a cow" OR "cows" in this context

A Paper Record is What I Hamper

Does a large simulator bay have standard public address announcements?

Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?

Is there a better way to say "see someone's dreams"?

What does "function" actually mean in music?

Older movie/show about humans on derelict alien warship which refuels by passing through a star

A faster way to compute the largest prime factor

Find a stone which is not the lightest one

Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?

Was Dennis Ritchie being too modest in this quote about C and Pascal?

Multiple fireplaces in an apartment building?

My admission is revoked after accepting the admission offer

Restricting the options of a lookup field, based on the value of another lookup field?

Israeli soda type drink

"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?

How can I practically buy stocks?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

Is there metaphorical meaning of "aus der Haft entlassen"?

Partitioning values in a sequence

Drawing a german abacus as in the books of Adam Ries

How can I wire a 9-position switch so that each position turns on one more LED than the one before?



How to troubleshoot Azure with custom Debian VHD; error message “provisioning failed”?


Do I create a fixed size or expandable VHD if I know the contents size in advance?How do I get a VHD with compression comparable to ZIP?Troubleshooting endless provisioning in Azure after custom image deploymentAzure Resource Manager storage - can I delete a VHD file using PowerShell?HOW-TO resolve “Add-AzureRmVhd : The remote server returned an error: (400) Bad Request.”Creating VM in Resource Group using Specialized VM but would like to enforce existing user to reset the password while creating vmWhere is my VHD being used in Azure VM?Error creating a Linux image/VM for upload to Azure due to incorrect correct sizeDeploying vhd from blob to AzureAzure classic migration errors






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have built a customised Debian (Jessie/8) VHD which I am trying to get running on Azure. According to my research (and the MS docs I've read) it meets the Azure Linux VHD requirements. I have tried to err on the side of caution to reduce or eliminate possible causes of issue. Here's some general info about my VHD:




  • static VHD file (some sources suggest that dynamic ones are supported, but some say they're not).

  • VHD is in VPC format and aligned to 1 MB.

  • no LVM (again some sources say that it is supported, others say it's not).

  • a single bootable primary partition (no swap) that use all of the space on the VHD (some sources note that this is a requirement).

  • grub has been tweaked as per requirements (as per https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-debian-create-upload-vhd/)

  • waagent installed, configured and the server has been "deprovisioned".


I don't have access to MS HyperV so I have only tested it locally in VirtualBox. FWIW it works fine there.



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 am also using the newer "Resource Manager" mode (as opposed to the old "Classic" one).



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. When I try to provision the server it takes ages (literally hours) chugging away and then eventually fails. azure-cli is not giving any useful error messages; just something like "provisioning failed".



I have a fair bit of experience working with AWS and Linux, but basically none with Azure. Regardless, surely it shouldn't be this hard!?



So how do I troubleshoot what my issue is?



Is there somewhere within Azure (or an undocumented debug switch for azure-cli) that I can get more detailed error messages?



Is there a list of common issues somewhere that i could work through?



Any help would be deeply appreciated! Thanks in advance.



[update] Here's the commands that I'm using:



azure storage blob upload <path-to-vhd> <container-name> <vhd-on-azure-name> -k <access-key> -a <storage-account-name>


FWIW the storage account used is in the same resource group as the
vm.



Then this is the problematic part (that goes forever and eventually fails):



azure vm create -u <admin-username> -p <admin-password> --location "AustraliaEast" -g "<my-resource-group>" "<vm-name>" -Q <full-vhd-urn> -f <nic-name> -F <vnet-name> -P 10.0.0.0/8 -j <subnet-name> -k 10.0.0.0/24 -o <storage-account-name> -y linux


The nic, vnet and subnet were originally auto-created by the first vm-create that failed. I have retired with auto creation since, but to avoid polluting the azure account I just took note of their names for re-use.



Other additional info:




  • image initially built to raw (and then vhd) on Debian Jessie.

  • 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:
    qemu-img convert -f raw -O vpc -o subformat=fixed


  • also tested both with and without "force_size" to maintain alignment.


  • all attempts work fine in VirtualBox, and all fail with Azure.


[another update]
Thanks @Sam for the suggestion to try using "Classic". It seems that the classic interface has better error reporting. It says that there is something wrong with the VHD (although doesn't give any clues on what). I'll try tweaking it some more and post back if I discover anything. Thanks guys.










share|improve this question

























  • plz detail the cmd lines you are using.

    – Bruno Faria
    Nov 2 '16 at 11:01











  • have you followed all the steps and requirements here - azure.microsoft.com/en-gb/documentation/articles/…

    – Sam Cogan
    Nov 2 '16 at 16:51











  • @BrunoFaria - THanks for your comment. I probably should have done that originally! I have now added some extra info, some is new (i.e. new stuff I've tried since OP - e.g. alignment) but some is just extra info of what I've tried.

    – Jeremy Davis
    Nov 3 '16 at 2:06











  • @Sam - Thanks for your comment too. I haven't tried that page as I have been attempting to use the "Resource Manager" method. Ultimately I'll need to use that, but thanks for the suggestion and I'm trying "Classic" now. Perhaps it will give me some additional info/insight?

    – Jeremy Davis
    Nov 3 '16 at 2:12


















0















I have built a customised Debian (Jessie/8) VHD which I am trying to get running on Azure. According to my research (and the MS docs I've read) it meets the Azure Linux VHD requirements. I have tried to err on the side of caution to reduce or eliminate possible causes of issue. Here's some general info about my VHD:




  • static VHD file (some sources suggest that dynamic ones are supported, but some say they're not).

  • VHD is in VPC format and aligned to 1 MB.

  • no LVM (again some sources say that it is supported, others say it's not).

  • a single bootable primary partition (no swap) that use all of the space on the VHD (some sources note that this is a requirement).

  • grub has been tweaked as per requirements (as per https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-debian-create-upload-vhd/)

  • waagent installed, configured and the server has been "deprovisioned".


I don't have access to MS HyperV so I have only tested it locally in VirtualBox. FWIW it works fine there.



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 am also using the newer "Resource Manager" mode (as opposed to the old "Classic" one).



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. When I try to provision the server it takes ages (literally hours) chugging away and then eventually fails. azure-cli is not giving any useful error messages; just something like "provisioning failed".



I have a fair bit of experience working with AWS and Linux, but basically none with Azure. Regardless, surely it shouldn't be this hard!?



So how do I troubleshoot what my issue is?



Is there somewhere within Azure (or an undocumented debug switch for azure-cli) that I can get more detailed error messages?



Is there a list of common issues somewhere that i could work through?



Any help would be deeply appreciated! Thanks in advance.



[update] Here's the commands that I'm using:



azure storage blob upload <path-to-vhd> <container-name> <vhd-on-azure-name> -k <access-key> -a <storage-account-name>


FWIW the storage account used is in the same resource group as the
vm.



Then this is the problematic part (that goes forever and eventually fails):



azure vm create -u <admin-username> -p <admin-password> --location "AustraliaEast" -g "<my-resource-group>" "<vm-name>" -Q <full-vhd-urn> -f <nic-name> -F <vnet-name> -P 10.0.0.0/8 -j <subnet-name> -k 10.0.0.0/24 -o <storage-account-name> -y linux


The nic, vnet and subnet were originally auto-created by the first vm-create that failed. I have retired with auto creation since, but to avoid polluting the azure account I just took note of their names for re-use.



Other additional info:




  • image initially built to raw (and then vhd) on Debian Jessie.

  • 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:
    qemu-img convert -f raw -O vpc -o subformat=fixed


  • also tested both with and without "force_size" to maintain alignment.


  • all attempts work fine in VirtualBox, and all fail with Azure.


[another update]
Thanks @Sam for the suggestion to try using "Classic". It seems that the classic interface has better error reporting. It says that there is something wrong with the VHD (although doesn't give any clues on what). I'll try tweaking it some more and post back if I discover anything. Thanks guys.










share|improve this question

























  • plz detail the cmd lines you are using.

    – Bruno Faria
    Nov 2 '16 at 11:01











  • have you followed all the steps and requirements here - azure.microsoft.com/en-gb/documentation/articles/…

    – Sam Cogan
    Nov 2 '16 at 16:51











  • @BrunoFaria - THanks for your comment. I probably should have done that originally! I have now added some extra info, some is new (i.e. new stuff I've tried since OP - e.g. alignment) but some is just extra info of what I've tried.

    – Jeremy Davis
    Nov 3 '16 at 2:06











  • @Sam - Thanks for your comment too. I haven't tried that page as I have been attempting to use the "Resource Manager" method. Ultimately I'll need to use that, but thanks for the suggestion and I'm trying "Classic" now. Perhaps it will give me some additional info/insight?

    – Jeremy Davis
    Nov 3 '16 at 2:12














0












0








0








I have built a customised Debian (Jessie/8) VHD which I am trying to get running on Azure. According to my research (and the MS docs I've read) it meets the Azure Linux VHD requirements. I have tried to err on the side of caution to reduce or eliminate possible causes of issue. Here's some general info about my VHD:




  • static VHD file (some sources suggest that dynamic ones are supported, but some say they're not).

  • VHD is in VPC format and aligned to 1 MB.

  • no LVM (again some sources say that it is supported, others say it's not).

  • a single bootable primary partition (no swap) that use all of the space on the VHD (some sources note that this is a requirement).

  • grub has been tweaked as per requirements (as per https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-debian-create-upload-vhd/)

  • waagent installed, configured and the server has been "deprovisioned".


I don't have access to MS HyperV so I have only tested it locally in VirtualBox. FWIW it works fine there.



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 am also using the newer "Resource Manager" mode (as opposed to the old "Classic" one).



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. When I try to provision the server it takes ages (literally hours) chugging away and then eventually fails. azure-cli is not giving any useful error messages; just something like "provisioning failed".



I have a fair bit of experience working with AWS and Linux, but basically none with Azure. Regardless, surely it shouldn't be this hard!?



So how do I troubleshoot what my issue is?



Is there somewhere within Azure (or an undocumented debug switch for azure-cli) that I can get more detailed error messages?



Is there a list of common issues somewhere that i could work through?



Any help would be deeply appreciated! Thanks in advance.



[update] Here's the commands that I'm using:



azure storage blob upload <path-to-vhd> <container-name> <vhd-on-azure-name> -k <access-key> -a <storage-account-name>


FWIW the storage account used is in the same resource group as the
vm.



Then this is the problematic part (that goes forever and eventually fails):



azure vm create -u <admin-username> -p <admin-password> --location "AustraliaEast" -g "<my-resource-group>" "<vm-name>" -Q <full-vhd-urn> -f <nic-name> -F <vnet-name> -P 10.0.0.0/8 -j <subnet-name> -k 10.0.0.0/24 -o <storage-account-name> -y linux


The nic, vnet and subnet were originally auto-created by the first vm-create that failed. I have retired with auto creation since, but to avoid polluting the azure account I just took note of their names for re-use.



Other additional info:




  • image initially built to raw (and then vhd) on Debian Jessie.

  • 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:
    qemu-img convert -f raw -O vpc -o subformat=fixed


  • also tested both with and without "force_size" to maintain alignment.


  • all attempts work fine in VirtualBox, and all fail with Azure.


[another update]
Thanks @Sam for the suggestion to try using "Classic". It seems that the classic interface has better error reporting. It says that there is something wrong with the VHD (although doesn't give any clues on what). I'll try tweaking it some more and post back if I discover anything. Thanks guys.










share|improve this question
















I have built a customised Debian (Jessie/8) VHD which I am trying to get running on Azure. According to my research (and the MS docs I've read) it meets the Azure Linux VHD requirements. I have tried to err on the side of caution to reduce or eliminate possible causes of issue. Here's some general info about my VHD:




  • static VHD file (some sources suggest that dynamic ones are supported, but some say they're not).

  • VHD is in VPC format and aligned to 1 MB.

  • no LVM (again some sources say that it is supported, others say it's not).

  • a single bootable primary partition (no swap) that use all of the space on the VHD (some sources note that this is a requirement).

  • grub has been tweaked as per requirements (as per https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-debian-create-upload-vhd/)

  • waagent installed, configured and the server has been "deprovisioned".


I don't have access to MS HyperV so I have only tested it locally in VirtualBox. FWIW it works fine there.



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 am also using the newer "Resource Manager" mode (as opposed to the old "Classic" one).



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. When I try to provision the server it takes ages (literally hours) chugging away and then eventually fails. azure-cli is not giving any useful error messages; just something like "provisioning failed".



I have a fair bit of experience working with AWS and Linux, but basically none with Azure. Regardless, surely it shouldn't be this hard!?



So how do I troubleshoot what my issue is?



Is there somewhere within Azure (or an undocumented debug switch for azure-cli) that I can get more detailed error messages?



Is there a list of common issues somewhere that i could work through?



Any help would be deeply appreciated! Thanks in advance.



[update] Here's the commands that I'm using:



azure storage blob upload <path-to-vhd> <container-name> <vhd-on-azure-name> -k <access-key> -a <storage-account-name>


FWIW the storage account used is in the same resource group as the
vm.



Then this is the problematic part (that goes forever and eventually fails):



azure vm create -u <admin-username> -p <admin-password> --location "AustraliaEast" -g "<my-resource-group>" "<vm-name>" -Q <full-vhd-urn> -f <nic-name> -F <vnet-name> -P 10.0.0.0/8 -j <subnet-name> -k 10.0.0.0/24 -o <storage-account-name> -y linux


The nic, vnet and subnet were originally auto-created by the first vm-create that failed. I have retired with auto creation since, but to avoid polluting the azure account I just took note of their names for re-use.



Other additional info:




  • image initially built to raw (and then vhd) on Debian Jessie.

  • 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:
    qemu-img convert -f raw -O vpc -o subformat=fixed


  • also tested both with and without "force_size" to maintain alignment.


  • all attempts work fine in VirtualBox, and all fail with Azure.


[another update]
Thanks @Sam for the suggestion to try using "Classic". It seems that the classic interface has better error reporting. It says that there is something wrong with the VHD (although doesn't give any clues on what). I'll try tweaking it some more and post back if I discover anything. Thanks guys.







debian azure vhd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 13 mins ago









Michael Hampton

176k27321651




176k27321651










asked Nov 2 '16 at 5:02









Jeremy DavisJeremy Davis

301311




301311













  • plz detail the cmd lines you are using.

    – Bruno Faria
    Nov 2 '16 at 11:01











  • have you followed all the steps and requirements here - azure.microsoft.com/en-gb/documentation/articles/…

    – Sam Cogan
    Nov 2 '16 at 16:51











  • @BrunoFaria - THanks for your comment. I probably should have done that originally! I have now added some extra info, some is new (i.e. new stuff I've tried since OP - e.g. alignment) but some is just extra info of what I've tried.

    – Jeremy Davis
    Nov 3 '16 at 2:06











  • @Sam - Thanks for your comment too. I haven't tried that page as I have been attempting to use the "Resource Manager" method. Ultimately I'll need to use that, but thanks for the suggestion and I'm trying "Classic" now. Perhaps it will give me some additional info/insight?

    – Jeremy Davis
    Nov 3 '16 at 2:12



















  • plz detail the cmd lines you are using.

    – Bruno Faria
    Nov 2 '16 at 11:01











  • have you followed all the steps and requirements here - azure.microsoft.com/en-gb/documentation/articles/…

    – Sam Cogan
    Nov 2 '16 at 16:51











  • @BrunoFaria - THanks for your comment. I probably should have done that originally! I have now added some extra info, some is new (i.e. new stuff I've tried since OP - e.g. alignment) but some is just extra info of what I've tried.

    – Jeremy Davis
    Nov 3 '16 at 2:06











  • @Sam - Thanks for your comment too. I haven't tried that page as I have been attempting to use the "Resource Manager" method. Ultimately I'll need to use that, but thanks for the suggestion and I'm trying "Classic" now. Perhaps it will give me some additional info/insight?

    – Jeremy Davis
    Nov 3 '16 at 2:12

















plz detail the cmd lines you are using.

– Bruno Faria
Nov 2 '16 at 11:01





plz detail the cmd lines you are using.

– Bruno Faria
Nov 2 '16 at 11:01













have you followed all the steps and requirements here - azure.microsoft.com/en-gb/documentation/articles/…

– Sam Cogan
Nov 2 '16 at 16:51





have you followed all the steps and requirements here - azure.microsoft.com/en-gb/documentation/articles/…

– Sam Cogan
Nov 2 '16 at 16:51













@BrunoFaria - THanks for your comment. I probably should have done that originally! I have now added some extra info, some is new (i.e. new stuff I've tried since OP - e.g. alignment) but some is just extra info of what I've tried.

– Jeremy Davis
Nov 3 '16 at 2:06





@BrunoFaria - THanks for your comment. I probably should have done that originally! I have now added some extra info, some is new (i.e. new stuff I've tried since OP - e.g. alignment) but some is just extra info of what I've tried.

– Jeremy Davis
Nov 3 '16 at 2:06













@Sam - Thanks for your comment too. I haven't tried that page as I have been attempting to use the "Resource Manager" method. Ultimately I'll need to use that, but thanks for the suggestion and I'm trying "Classic" now. Perhaps it will give me some additional info/insight?

– Jeremy Davis
Nov 3 '16 at 2:12





@Sam - Thanks for your comment too. I haven't tried that page as I have been attempting to use the "Resource Manager" method. Ultimately I'll need to use that, but thanks for the suggestion and I'm trying "Classic" now. Perhaps it will give me some additional info/insight?

– Jeremy Davis
Nov 3 '16 at 2:12










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f812658%2fhow-to-troubleshoot-azure-with-custom-debian-vhd-error-message-provisioning-fa%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f812658%2fhow-to-troubleshoot-azure-with-custom-debian-vhd-error-message-provisioning-fa%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Фонтен-ла-Гаярд Зміст Демографія | Економіка | Посилання |...

Список ссавців Італії Природоохоронні статуси | Список |...

Маріан Котлеба Зміст Життєпис | Політичні погляди |...