I’vve been running KVM for quite a while on my lab server. It’s been running without issue but with the release of vSphere/ESXi 6.0 I felt it was time to move back to VMware. I wanted to preserve the virtual machines already running so I set out to move these to ESXi. I ran into some issues which I’m not sure is a generic problem or specific to ESXi 6.0 but I’ll describe what I have done....
I have recently moved my hosting to a couple of VPSes at ChicagoVPS and wanted to use IPv6 tunnelbroker.net ChicagoVPS uses OpenVZ which presents a couple of problems $ ifconfig sit0 sit0: error fetching interface information: Device not found $ sudo modprobe ipv6 FATAL: Module ipv6 not found. It turns out, this is a fairly common problem though OpenVZ is supposed to support IPv6. Luckily, someone made a small userland program tb-tun, which “tunnels” IPv6 tunnels through a TUN/TAP device....
iptables is not always easy to deal with so I prefer to use Uncomplicated firewall (ufw) in Ubuntu, because it simplifies configuring and maintaining my firewall rules. Unfortunately, ufw does not play nice with OpenVZ containers so I decided to find something else. In the end (after testing various things) I decided to install the package iptables-persistent which is not as sexy as ufw but gets the job done. iptables-persistent uses two configuration files /etc/iptables-persistent/rules....
It’s been a while since I last had to run Windows on my laptop; back then I used Ext2 Installable File System For Windows to access data on my Linux-formated partitions. In the meantime a few things have changed: Windows 7 and Ubuntu formating ext3 with a inode size of 256 – none of these are supported by ext3 ifs. Ext2read supports Windows 7 (as well as ext4 and LVM2) but it’s more like a file browser and does not support assigning drive letters to Linux filesystems and since my /home is formatted with XFS it does not help me anyway....
Just a quick heads-up. Virtualbox does not yet officially support Xorg 1.9 (which is shipped with Ubuntu 10.10). According to this ticket the problem will be fixed in 3.2.10. In the meantime, try you your luck which with this unsupported Additions build; it didn’t work for me though....
Background In the past I have written a couple of articles on how to run Windows applications using SeamlessRDP and Sun xVM (Virtualbox) and [Linux KVM](http://www.linux-kvm.org/page/Main_Page Linux KVM) (Kernel-based Virtual Machine). After reviewing both articles I have decided to write a new article encompassing both hypervisors and correcting some of the mistakes I have found as well improvements made by a couple of guys who have done quite a deal of testing: Thomas Hansson and Peter Clarén....
Please go to the updated article. Since I wrote the post about running Windows applications on Linux with Sun xVM VirtualBox and SeamlessRDPI have been using the system almost daily to run some applications needed at work. It has been running well except for crashes in VirtualBox from time to time. Two new releases of VirtualBox has not fixed the problem.<p class="wp-caption-text"> Setting connection limit in Terminal Services </p> <p class="wp-caption-text"> Redirected local resource in RDP </p> ...
Yesterday Sun released the second maintenance release for VirtualBox 2.1 See the Changelog for more details. Actually my Windows VM has been running smoothly since I upgraded to 2.1.2 but as usual there is a bunch of bugfixes in this release. Download it here....