Page 1 of 1

Request to add nested VT-X support on AWS EC2 Ubuntu Instance

Posted: Wed Oct 18, 2017 9:14 pm
by rdparmar87
Hi team,

Not sure if this is a relevant feature request or not but I see an issue with Juniper vSRX qemu image on eve-ng on AWS Ec2 (start and stop issue0) and this looks to be an issue with VT-X not supported on AWS Ec2 instance as this machine itself is already running on VM. If there is any way we can find an alternative solution then would help us to save lots of money by investing on physical hardware.

Thank you!

Re: Request to add nested VT-X support on AWS EC2 Ubuntu Instance

Posted: Thu Oct 19, 2017 7:21 am
by ramindia
rdparmar87 wrote:
Wed Oct 18, 2017 9:14 pm
Hi team,

Not sure if this is a relevant feature request or not but I see an issue with Juniper vSRX qemu image on eve-ng on AWS Ec2 (start and stop issue0) and this looks to be an issue with VT-X not supported on AWS Ec2 instance as this machine itself is already running on VM. If there is any way we can find an alternative solution then would help us to save lots of money by investing on physical hardware.

Thank you!
When you install EVE-Ng under Amazon it will become Nested, Some of Underlay infrastructure dont expose properly their hardware information to nested VM. So you some many issues.

If you keen to work, may be join to tech chat, and can be discussed.

R!

Re: Request to add nested VT-X support on AWS EC2 Ubuntu Instance

Posted: Thu Oct 19, 2017 7:45 am
by Uldis (UD)
As I know AWS cloud and server does not offer exposure hw acceleration thats why will work only IOL or dynamips...

Best cloud choice is ovh.com

UD

Re: Request to add nested VT-X support on AWS EC2 Ubuntu Instance

Posted: Thu Oct 19, 2017 9:50 pm
by rdparmar87
True that UD, AWS does not support KVM VT-X in any of it's instances and that's the reason only IOL and dynamips are working whereas other devices are not supported.