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....
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....
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> ...
The fastest way of determining the UUID of a LUN on ESX is through /proc: # grep "Id:" /proc/vmware/scsi/vmhba1/8:5 Id: 60 5 7 68 1 90 81 1a d8 0 0 0 0 0 0 34 32 31 34 35 20 20 This corresponds to a UUID of 600507680190811ad800000000000034 On ESX 3.5 go to /vmfs/devices/disks to see the mapping to a vmhba....
Symptom: Various keys not working in VMware Workstation, Player and probably other produtcs. In my case the cursor keys (left, right, up, down) didn’t work. In fact pressing up or down in a Linux/GNOME session brought up the screenshot application. Solution: Add the following line to VMware’s configuration (~/.vmware/config): xkeymap.nokeycodeMap = true or as a one-liner: echo 'xkeymap.nokeycodeMap = true' > ~/.vmware/config that fixed it for me. More information....
First of all I didn’t fall of the face of the planet. I’ve just been really busy with work, travelling a lot. After upgrading my kernel to 2.6.27 as part of the Ubuntu Intrepid test cycle I’ve sort of given up on VMware Workstation, considering switching to VirtualBox or kvm. Luckily it caught my attention that VMware had released Workstation version 6.5. I installed it and lo and behold! It’s working out of the box with kernel 2....
Update 01-11-08: VMware Workstation 6.5 is out and seems to have done away with the need for patching the installation After upgradering my workstation to Ubuntu Intrepid Ibex (8.10) I have run into the same problem as always with VMware Workstation. It will not compile against the installed kernel (in this case 2.6.26). This problem is not isolated to Ubuntu but affects all distributions using a 2.6.25 or 2.6.26 kernel (from what I gather)....