<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Stuff... &#187; Virtualisation</title>
	<atom:link href="http://www.moe.co.uk/category/operating-system/virtualisation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.moe.co.uk</link>
	<description>I know I will forget.</description>
	<lastBuildDate>Wed, 04 Jan 2012 04:35:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>pci_add_option_rom: failed to find romfile &#8220;pxe-rtl8139.bin&#8221;</title>
		<link>http://www.moe.co.uk/2011/01/07/pci_add_option_rom-failed-to-find-romfile-pxe-rtl8139-bin/</link>
		<comments>http://www.moe.co.uk/2011/01/07/pci_add_option_rom-failed-to-find-romfile-pxe-rtl8139-bin/#comments</comments>
		<pubDate>Fri, 07 Jan 2011 11:55:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Operating System]]></category>
		<category><![CDATA[Virtualisation]]></category>

		<guid isPermaLink="false">http://www.moe.co.uk/?p=702</guid>
		<description><![CDATA[Was having two small issues with starting a KVM virtual server on Ubuntu 10.04 LTS: pci_add_option_rom: failed to find romfile &#8220;pxe-rtl8139.bin&#8221; inet_parse: ipv4 parse error (1) root@hostname:~/qemu-test# qemu -m 256 -vnc 1 -hda linux.small.img -cdrom dsl-n-01RC4.iso -boot d pci_add_option_rom: failed to find romfile &#8220;pxe-rtl8139.bin&#8221; inet_parse: ipv4 parse error (1) root@hostname:~/qemu-test# apt-get install kvm-pxe Reading package [...]]]></description>
		<wfw:commentRss>http://www.moe.co.uk/2011/01/07/pci_add_option_rom-failed-to-find-romfile-pxe-rtl8139-bin/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Change linux virtuozzo VE/CT quota via command line</title>
		<link>http://www.moe.co.uk/2010/01/13/change-linux-virtuozzo-vect-quota-via-command-line/</link>
		<comments>http://www.moe.co.uk/2010/01/13/change-linux-virtuozzo-vect-quota-via-command-line/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 19:14:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Operating System]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Virtualisation]]></category>
		<category><![CDATA[hardlimit]]></category>
		<category><![CDATA[resource]]></category>
		<category><![CDATA[setlimit]]></category>
		<category><![CDATA[show]]></category>
		<category><![CDATA[softlimit]]></category>
		<category><![CDATA[usage]]></category>
		<category><![CDATA[virtuozzo]]></category>
		<category><![CDATA[vzquota]]></category>

		<guid isPermaLink="false">http://www.moe.co.uk/?p=277</guid>
		<description><![CDATA[~]# vzquota show 102 vzquota : (warning) Quota is running, so data reported from quota file may not reflect current values    resource          usage       softlimit      hardlimit    grace   1k-blocks       95325856       104857600      104857600      inodes         683893         2000000        2200000  ~]# vzquota setlimit 102 -b 113246208 -B 113246208  ~]# vzquota show 102 vzquota : (warning) Quota is running, [...]]]></description>
		<wfw:commentRss>http://www.moe.co.uk/2010/01/13/change-linux-virtuozzo-vect-quota-via-command-line/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows VE/CT EFD mount/check</title>
		<link>http://www.moe.co.uk/2009/02/01/windows-vect-efd-mountcheck/</link>
		<comments>http://www.moe.co.uk/2009/02/01/windows-vect-efd-mountcheck/#comments</comments>
		<pubDate>Sun, 01 Feb 2009 11:08:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Virtualisation]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[ct]]></category>
		<category><![CDATA[ve]]></category>
		<category><![CDATA[virtuozzo]]></category>

		<guid isPermaLink="false">http://www.moe.co.uk/2009/02/01/windows-vect-efd-mountcheck/</guid>
		<description><![CDATA[Was having a problem with a Windows Virtuozzo VE/CT and needed to check the VE/CT virtual disk for file system corruption. URLs: http://kb.parallels.com/en/1008 Commands issued to check the virtual disk file for errors: C:\Documents and Settings\Administrator&#62;vzcfgt get 100 GUID {A88D866B-0382-47FC-9BFB-37056F286745} C:\Documents and Settings\Administrator&#62;vzdskctl mount d:\vz\private\100\root.ef d {A88D866B-0382-47FC-9BFB-37056F286745} SUCCESS C:\Documents and Settings\Administrator&#62;chkdsk /f \\?\Volume{A88D866B-0382-47FC- 9BFB-37056F286745} C:\Documents [...]]]></description>
		<wfw:commentRss>http://www.moe.co.uk/2009/02/01/windows-vect-efd-mountcheck/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Virtuozzo for Linux VE/CT was locked for some reason and couldn&#8217;t start it</title>
		<link>http://www.moe.co.uk/2008/06/18/vect-was-locked-for-some-reason-and-couldnt-start-it/</link>
		<comments>http://www.moe.co.uk/2008/06/18/vect-was-locked-for-some-reason-and-couldnt-start-it/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 08:45:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Operating System]]></category>
		<category><![CDATA[Virtualisation]]></category>
		<category><![CDATA[ct]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[locked]]></category>
		<category><![CDATA[parallels]]></category>
		<category><![CDATA[ve]]></category>
		<category><![CDATA[virtuozzo]]></category>

		<guid isPermaLink="false">http://www.moe.co.uk/wordpress/2008/06/18/vect-was-locked-for-some-reason-and-couldnt-start-it/</guid>
		<description><![CDATA[A VE/CT on Linux started and then stopped mysteriously. I couldn&#8217;t manually restart it with vzctl start 101. The following URL showed how to determine which PID had locked the VE/CT: http://faq.swsoft.com/article_133_655_en.html In this case running cat /vz/lock/101.lck showed that vzquota was recalculating the quota for the virtual environment.]]></description>
		<wfw:commentRss>http://www.moe.co.uk/2008/06/18/vect-was-locked-for-some-reason-and-couldnt-start-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

