5 ms·
You can currently run FreeBSD instances using cperciva's AMIs, but that's not the same as Amazon supporting FreeBSD in the same way they support Linux. The onl
by cperciva 13y ago
You can currently run FreeBSD instances using cperciva's AMIs, but that's not the same as Amazon supporting FreeBSD in the same way they support Linux.
The only "lack of support" which concerns me is the fact that on older EC2 instance types HVM (which FreeBSD uses) is only available by paying for a Windows license. I wouldn't want Amazon to start publishing their own "FreeBSD" images -- those should be provided by the project.
- profquail 13y agoThat's what I mean -- having to pay for a Windows license you're not using is a strong deterrent to using FreeBSD on AWS; people who might prefer a FreeBSD server end up using Linux instead simply because of the cost difference. You're far more knowledgeable than I (or pretty much anyone else!) about building FreeBSD AMIs, so if you say they should be provided directly by the project, I'm happy to go with that. I would just like to see 'FreeBSD' appear as a "mainstream" option when choosing the OS for a new EC2 instance. (See gonzo's link -- the dialog shown in the picture has 15 Linux distributions available; it'd be nice for FreeBSD to be on that menu.) Will the licensing issue for the smaller AMIs go away once the PVHVM drivers are fully implemented? I don't know a whole lot about Xen, so I'm curious to know what needs to be implemented to fix that problem.
- cperciva 13y agoI would just like to see 'FreeBSD' appear as a "mainstream" option when choosing the OS for a new EC2 instance. That is now fixed in the AWS Marketplace -- although the only AMIs in the marketplace running FreeBSD are my FreeBSD image and Citrix's NetScaler and CloudBridge products. Will the licensing issue for the smaller AMIs go away once the PVHVM drivers are fully implemented? No, PVHVM is still a variety of HVM, and on the old instance types that's only available with a "Windows" label attached.