After a whole lot of struggling, I’ve finally figured out the best way to install a Windows virtual machine under KVM, using the paravirtual (virtio) drivers. The basic idea is to use the virtio devices from the initial installation to avoid all the work and hassles involved with changing the drivers later. This avoids mistakes which can lead to an unbootable guest or “Local Area Connection 2” annoyances.
Thanks to Stefan Skotte and Andy for updates to simplify this procedure.
- Download the latest virtio drivers (in ISO format).
- Create a new virtual machine as you normally would for a Windows guest, stopping just before clicking Finish.
- If you have a new enough version of virt-manager, you can check the “Customize configuration before install” checkbox. Otherwise, click Finish, stop the virtual machine, open the details, reconnect the CD (or other installation media) if necessary, and reconfigure the guest to boot off the CD (or other installation media).
- Delete the IDE disk device and re-add the storage as a Virtio disk.
- Change the NIC’s device model to virtio.
- Switch to the console view, run the virtual machine, and start the installation as normal.
- When the disk configuration step comes up, no disk will be detected. This is normal.
- Click Load driver…
- Switch to the details view, disconnect the Windows installation CD, and connect the virtio ISO image.
- Switch back to the console view and click Rescan.
- Select the virtio block storage and virtio network drivers for the Windows version being installed, using the control key to select multiple items as always.
- Click Next.
- Switch to the details view, disconnect the drivers CD, and connect the Windows installation CD again.
- Proceed with the installation as normal.
- Reconfigure the boot options, if necessary, as desired.
- Disconnect the CD device, if necessary and desired.
So Ubuntu Lucid is changing the window title bar button placement.
I’m not sure why…other than Mark Shuttleworth seems to love copying Apple. 😉A colleague pointed out Mark Shuttleworth’s Window indicators post as the reason for this change.
However, this change made me realize one thing… I never use the menu from the title bar. I use it on the task bar a lot (for “Close”, “Always On Top”, “Move to Another Workspace”, and “Always on Visible Workspace”, in that order of frequency), but not from the title bar. This is a random observation, nothing more.
I just got back from a talk given by Richard Stallman at the University of Minnesota. It was about software freedom. If you’re looking for more information, I would encourage you to check out gnu.org and fsf.org. I’m not going to repeat all the points. I just wanted to note one thing:
I understand his push for “GNU/Linux” a lot more now. It’s one thing to talk about credit–there I disagree, because I don’t want to call it “GNU/Linux/X/GNOME/OpenOffice.org”. However, he made the point that calling the distro “Linux” points all the attention towards Linus, who isn’t pushing software freedom. I hadn’t thought about that before.
On a side note, RMS pronounces it “GNU slash Linux” or “GNU plus Linux”, where I think “GNU Linux” is a totally more reasonable… After all, nobody pronounces the slash in “and/or”.
Check out my photos of an exploding Ubuntu CD.
gnome-blog, version 0.8 has support for WordPress blogs. However, it seems that selecting wordpress appends “wordpress/xmlrpc.php” to the URL. This results in silent failures if you enter, for example: https://coderich.net I ended up choosing Self-run Other, then entered https://coderich.net/xmlrpc.php as the URL, and everything works. Yay!
Update: Apparently gnome-blog doesn’t set the title properly with BloggerAPI. I switched to MetaWeblog in the options and now it works!