There are vagrant plugins to instantiate vagrant VMs on AWS, Linode, and DigitalOcean, among others. I've personally succeeded in getting the Linode and DigitalOcean ones up to the point of "vagrant ssh". But you don't get to pick arbitrary box files.
But the way you're using terms makes me think you mean something different from what the rest of the world means. Are you looking for a VPS that itself can host VMs? There are probably some out there, but you should probably examine very carefully your reasons for thinking that's what you need. For all the scenarios I can imagine, it's at least one surplus level of virtualization. -- jmcg On Wed, Apr 28, 2021 at 2:12 PM dnmo...@gmail.com <dnmor...@gmail.com> wrote: > As mentioned before you need what is called a :"bare metal" tyoe of VM, > AWS has m5, r5 or z1d - > https://aws.amazon.com/about-aws/whats-new/2019/02/introducing-five-new-amazon-ec2-bare-metal-instances/, > Linode has their version - https://www.linode.com/products/bare-metal/ > > On Wednesday, April 28, 2021 at 1:25:13 PM UTC-4 Antony Stone wrote: > >> On Wednesday 28 April 2021 at 19:21:20, Norman Robins wrote: >> >> > On Wed, Apr 28, 2021 at 10:18 AM Antony Stone wrote: >> > > >> > > I can only continue to wonder why you don't run Vagrant on AWS, then, >> and >> > > just skip all the virtual server stuff. >> > > >> > > https://www.vagrantup.com/docs/plugins/providers >> > >> > I guess I don't understand what this means. If I create an EC2 >> > instance at AWS and run vagrant up I get 'AMD-V is not available' When >> > I asked them they said EC2 instances do not support running VMs. >> >> Hm. >> >> In that case, I'm sorry, but I can't help you further - I've never >> actually >> run Vagrant on AWS - I was just aware that this documentation existed and >> thought that it sounded like an ideal solution to your requirement. >> >> Maybe someone else here who actually has done Vagrant on AWS can comment >> further. >> >> >> Regards, >> >> >> Antony. >> >> -- >> I wasn't sure about having a beard at first, but then it grew on me. >> >> Please reply to the list; >> please *don't* CC me. >> > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/hashicorp/vagrant/issues > Discuss: https://discuss.hashicorp.com/c/vagrant/24 > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/319d5f1d-9b1b-40db-ac37-c74fe7e88f03n%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/319d5f1d-9b1b-40db-ac37-c74fe7e88f03n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CACEPCkTSxPpiSEZSv9%2B%2BkJuMiG8gbZEmyU_pBAZ0RiuFj3j5-w%40mail.gmail.com.
