virtualization

NOTE: The opinions shared in this post are mine alone and are not related to my employer in any way.

I ran into an interesting problem recently in my production OpenStack deployment that runs the Mitaka release.

Today is the second day of the OpenStack Summit in Austin and I offered up a talk on host security hardening in OpenStack clouds.

I spent some time working with macvlan interfaces on KVM hypervisors last weekend.

I received some good feedback about my post on systemd-networkd and bonded interfaces on Rackspace’s OnMetal servers, and I decided to write about another use case.

I decided to change some of my infrastructure back to KVM again, and the overall experience has been quite good in Fedora 22.

The world of containers is constantly evolving lately.

Amid all of the Docker buzz at the Red Hat Summit, Project Atomic was launched.

Getting started with LXC is a bit awkward and I’ve assembled this guide for anyone who wants to begin experimenting with LXC containers in Fedora 20.

Docker is a hot topic in the Linux world at the moment and I decided to try out the new trusted build process.

After upgrading my Fedora 20 Xen hypervisor to virt-manager 1.

I’ve written about installing Xen on Fedora 19 and earlier versions on this blog before.

Outside of the RHCA exams, I haven’t configured a PXE system for my personal needs.

Pairing virt-manager with KVM makes booting new VM’s pretty darned easy.

It’s been a little while since I last posted about installing Xen on Fedora, so I figured that Fedora 19’s beta release was as good a time as any to write a new post.

I’ve converted one of my KVM hypervisors from CentOS 6 to Fedora 18 and now comes the task of migrating my virtual machines off of my single remaining CentOS 6 hypervisor.

Changing my ssh port from the default port (22) has been one of my standard processes for quite some time when I build new servers or virtual machines.

The latest versions of virt-manager don’t release the mouse pointer when you’re doing X forwarding to a machine running OS X.

I dragged out an old Aopen MP57-D tonight that was just sitting in the closet and decided to load up kvm on Fedora 18.

If you try to run Xen without libvirt on Fedora 17 with SELinux in enforcing mode, you’ll be butting heads with SELinux in no time.

Getting XenServer installed on some unusual platforms takes a bit of work and the AOpen MP57 is a challenging platform for a XenServer 6.

I originally wrote this post for the Rackspace Blog but I’ve posted it here just in case anyone following my blog’s feed finds it useful.

If you haven’t noticed already, full Xen dom0 support was added in the Linux 3.

Installing Xen can be a bit of a challenge for a beginner and it’s made especially difficult by distribution vendors who aren’t eager to include it in their current releases.

The discussions about the paravirt_ops, or “pvops”, support in upstream kernels at Xen Summit 2010 last month really piqued my interest.