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

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin...