Skip to main content

Installing Windows 7 x64 on KVM (QEMU)

VMware Workstation 8 has been somewhat of a challenge for me on my current laptop using Fedora 16 x86_64.  Installing 8.0.0 required some hand-built patch that someone published, and 8.0.1 seems to lock up my display manager to the point where CTRL-ALT-Backspace is the only way out of the situation (followed by forcefully taking ownership of the VM, etc..)

I decided to see if KVM would work any better.  It was no love-fest either.  But, it is working and free... ;-)

I created an LVM volume and mounted it as /var/lib/libvirt prior to installing the Virtualization packages via yum.  Using the Virtual Machine Manager (VMM) I created the Windows 7 VM and essentially left all the defaults.  I was unable to get the floppy added to my machine and subsequently added a 2nd CD-ROM to install the VirtIO drivers during the install.

Some items I found to be positives:

  • The virbr0 (NAT) network was able to utilize my wireless or my Ethernet connection, without ANY intervention on my part.  That is really quite awesome.  I don't recall that being the case previously.
  • The VMM GUI is actually fairly decent.
  • The Windows client installation was reasonably painless.
Some items I feel need improvement:
  • I found conflicting documentation/blogs/etc.. (mostly due to my lack of knowledge on the product) regarding the different types of Virtualization and when/why you would chose one over the other.  VMware workstation seems rather straight-forward as you simply install the product (in theory) and build your Guest OS, then install the VMware Tools.  There really were no choices.  As opposed to KVM/libvirt which I wasn't sure if I should use VirtIO, SCSI, etc... and if I did choose to go one direction, or the other, how did that impact what I was trying to accomplish.

Comments

Post a Comment

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...
1 comment
Read more