2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I also tried: ec2-register -n pvami -s snap-0ffe4a3cb9932b167 --virtualization-type paravirtual to see if I could force the ami to paravirtual, but this didn't work either. The ami is still listed as hvm.
con risposta 2 anni fa
You need to specify --kernel-id <kernel> on aws ec2 register-image, but I don't know what your kernel ID is. Try uname -a on the command line of the original instance
Thank you! That was it!
0
Thanks for getting back to me, Rodney. I checked and when I create the AMI I cannot select a kernel. It just says it is going to use the default. I never selected one before, honestly. I've checked a few other snapshots, both from the same ec2 I am using and others from different ec2's (All using paravirtual).
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 8 mesi fa
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata un anno fa
I don't have any paravirtual instances, but according to the documentation, you have to specify the Kernel ID that matches the source OS. You may also have to enter a RAM Disk ID if you are using that feature. Are you specifying those options?