Oxide Computer Company: Initial boot sequence

Re:Oxide Computer Company: Initial boot sequence by slowmovintarget on Monday December 02, 2019 @11:56AM (#21684197)

Does that mean "I have servers... Oxide manages the virtualization"?

Or "I bought a rack full of Oxide and now I have my own puddle of elastic compute on-premises." (If you condense a small cloud, you get a puddle, I presume.)

If hardware is involved it would seem like the latter. In which case they'll be competing with Amazon's on-premises solution and commodity hardware.

[ Parent | on HN ]

Re:Oxide Computer Company: Initial boot sequence by weberc2 on Monday December 02, 2019 @12:58PM (#21684876)

I wonder if they're trying to eliminate the VM substrate layer that clouds today currently run on by replacing it with hardware and an OS that is more amenable to running containers natively with good isolation/security properties?

[ Parent | on HN ]

Re:Oxide Computer Company: Initial boot sequence by akhilcacharya on Monday December 02, 2019 @01:25PM (#21685179)

So, like AWS Nitro?

[ Parent | on HN ]

Re:Oxide Computer Company: Initial boot sequence by floatboth on Monday December 02, 2019 @02:52PM (#21686151)

Nitro doubles down on VMs instead of abandoning them, but it is indeed a good example of what integrated hardware and software can do.

What they did with Nitro is develop custom PCIe devices to handle storage and networking, so these devices' virtual functions (SR-IOV) are directly passed through to the VMs and now the hypervisor basically has nothing to do other than switching contexts.

[ Parent | on HN ]