<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on the bin</title><link>https://thebin.net/tags/windows/</link><description>Recent content in Windows on the bin</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 06 Feb 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://thebin.net/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>KVM Guests: Graceful Shutdown</title><link>https://thebin.net/2012/02/kvm-guests-graceful-shutdown/</link><pubDate>Mon, 06 Feb 2012 00:00:00 +0000</pubDate><guid>https://thebin.net/2012/02/kvm-guests-graceful-shutdown/</guid><description>&lt;p&gt;So a fairly trivial (but critical) aspect of using KVM is of course performing graceful shutdowns of your domains, without having to reach inside of the guest to perform the shutdown.  Now when it comes to turning off your guests you have two ways of proceeding (with virsh)…&lt;/p&gt;&#10;&lt;div class="codeblock" data-lang="bash"&gt;&#10; &lt;div class="codeblock__bar"&gt;&#10; &lt;span class="codeblock__lang"&gt;bash&lt;/span&gt;&#10; &lt;button type="button" class="codeblock__copy" aria-label="Copy code"&gt;&#10; &lt;span class="codeblock__copy-label"&gt;Copy&lt;/span&gt;&#10; &lt;/button&gt;&#10; &lt;/div&gt;&#10; &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;virsh destroy vmname&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;Which is a HARD power off of your guest.  This is the same as pulling the power cord from the wall, nothing is shutdown, but the noise stops just the same.  This method can result in data corruption if writes are interrupted.&lt;/p&gt;</description></item><item><title>KVM Guests: Install VirtIO Drivers for Windows Guests</title><link>https://thebin.net/2011/03/kvm-guests-install-virtio-drivers-for-windows-guests/</link><pubDate>Tue, 22 Mar 2011 00:00:00 +0000</pubDate><guid>https://thebin.net/2011/03/kvm-guests-install-virtio-drivers-for-windows-guests/</guid><description>&lt;p&gt;Windows guests on the KVM hypervisors can get a very large kick in the pants when it comes to performance if you install the drivers necessary to leverage the VirtIO bus.  So first here are the necessary download links so that you can download the drivers.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-1.1.16.iso"&gt;http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-1.1.16.iso&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/"&gt;http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Inside of the ISO we will find four directories Balloon, NetKVM, vioserial, and viostor.  We are only concerned with viostor and NetKVM, for the storage and networking drivers.  Vioserial is a serial interface which essentially lifts the single serial device limitation within KVM, and Balloon is a balloon memory driver I personally do not find this necessary due to the efficacy of the Kernel Samepage Merging (KSM) which is essentially memory deduplication.&lt;/p&gt;</description></item><item><title>Linux-KVM: Managing KVM Guests Using Virt-Manager on Windows</title><link>https://thebin.net/2011/03/linux-kvm-managing-kvm-guests-using-virt-manager-on-windows/</link><pubDate>Mon, 21 Mar 2011 00:00:00 +0000</pubDate><guid>https://thebin.net/2011/03/linux-kvm-managing-kvm-guests-using-virt-manager-on-windows/</guid><description>&lt;p&gt;When I first started using KVM, I was quite disappointed with the graphical management abilities of KVM.  Basically if you want to manage via the command line KVM is a fantasical dream world where anything is possible and it is all “musical sunshine” and “double rainbows” but if you want the ability to manage graphically it was a world which was very one sided in that if you wanted the ability to graphically manage your VMs then you had to use Linux.  Or so I thought…&lt;/p&gt;</description></item></channel></rss>