<?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>Shlrm.org Blag &#187; fedora</title>
	<atom:link href="http://shlrm.org/wordpress/category/linux/fedora-linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://shlrm.org/wordpress</link>
	<description>Linux, Java, Ruby, and Politics.</description>
	<lastBuildDate>Mon, 10 Oct 2011 18:50:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Fedora, old MaraDNS, and IPv6 == FAIL</title>
		<link>http://shlrm.org/wordpress/2011/03/05/fedora-old-maradns-and-ipv6-fail/</link>
		<comments>http://shlrm.org/wordpress/2011/03/05/fedora-old-maradns-and-ipv6-fail/#comments</comments>
		<pubDate>Sat, 05 Mar 2011 18:16:46 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Gripes]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=430</guid>
		<description><![CDATA[MaraDNS sucks at IPv6 until 2.0, Fedora has 1.3 (two version behind 2.0 stable). FAIL]]></description>
			<content:encoded><![CDATA[<p>Given the &#8220;end of IPv4&#8243; I decided I shouldset up IPv6 on my network and see if I can&#8217;t start doing things over that instead. Unfortunately, however, it appears that my DNS server internal to my network, <a title="Bug Comments by Author" href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525188#15">maradns, sucks at IPv6 until version 2.0</a>. Fedora has it at 1.3.something. Debian has it at 1.4. WTF Fedora?</p>
<p>I&#8217;ve been working on building MaraDNS 2.0 RPMs for Fedora 13 and 14, but I don&#8217;t know the RPM SPEC structure very well. The 2.0 version of MaraDNS has separated the authoritative resolver from the recursive resolver, which is wise. But it means I need to build a spec file that produces two RPMs. I suppose I could build a separate spec file for each one, but that doesn&#8217;t seem like the right way to do things.</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2011/03/05/fedora-old-maradns-and-ipv6-fail/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Userspace cgroups in Fedora 14</title>
		<link>http://shlrm.org/wordpress/2010/11/21/userspace-cgroups-in-fedora-14/</link>
		<comments>http://shlrm.org/wordpress/2010/11/21/userspace-cgroups-in-fedora-14/#comments</comments>
		<pubDate>Mon, 22 Nov 2010 00:08:35 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[W00t!]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=420</guid>
		<description><![CDATA[There was a lot of buzz on the interblags about a 200-line kernel patch that enables per-tty cgroups automatically. Apparently, one can add them trivially to their home directory without having to patch any kernels. This blog post talks about how to do it, but it didn&#8217;t cooperate with Fedora 14 very well. A bit <a href='http://shlrm.org/wordpress/2010/11/21/userspace-cgroups-in-fedora-14/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>There was a lot of buzz on the interblags about a 200-line kernel patch that enables per-tty cgroups automatically. Apparently, one can add them trivially to their home directory without having to patch any kernels.</p>
<p><a href="http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html">This blog post</a> talks about how to do it, but it didn&#8217;t cooperate with Fedora 14 very well. A bit of googleing later and I found <a href="http://forum.nginx.org/read.php?30,151937,151954#msg-151954">this mailing list post</a> that did it for me. Now I have userspace cgroups for each terminal I open. Handy, I suppose. Might be more useful on an SSH server to guarantee that each person logging in can&#8217;t overwhelm the system for the others.</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/11/21/userspace-cgroups-in-fedora-14/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fedora 14 and Intel Gigabit Adaptors</title>
		<link>http://shlrm.org/wordpress/2010/11/21/fedora-14-and-intel-gigabit-adaptors/</link>
		<comments>http://shlrm.org/wordpress/2010/11/21/fedora-14-and-intel-gigabit-adaptors/#comments</comments>
		<pubDate>Sun, 21 Nov 2010 22:39:54 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[ethernet]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=414</guid>
		<description><![CDATA[The kernel that comes with Fedora 14 has a significant (IMHO) regression when it comes to Intel Gigabit adaptors that use the e1000e driver.]]></description>
			<content:encoded><![CDATA[<p>To be fair, it&#8217;s not Fedora 14 that&#8217;s at fault. The 2.6.35 kernel has a regression in the e1000e driver for <a href="http://sourceforge.net/tracker/index.php?func=detail&amp;aid=3035627&amp;group_id=42302&amp;atid=447449">some Ethernet adaptors</a>.</p>
<p>It was quite tricky to figure out, especially right after 14 came out, as I didn&#8217;t have an ethernet connection, and when I was able to get the connection up, and I asked on the IRC channel, no one had any insight. I let 14 stew a while, and the rest of the internet came up with similar problems. Turns out that the kernel driver included in 2.6.35 has issues. There&#8217;s some patches in the works, but I don&#8217;t know if they&#8217;ll get pulled down into 2.6.35. The fix is in 2.6.36.</p>
<p>Until then, you can get the latest driver directly from the e1000e&#8217;s SourceForge website <a href="http://sourceforge.net/projects/e1000/files/e1000e%20stable/1.2.20/e1000e-1.2.20.tar.gz/download">here</a>. Make, then make install it as root and you&#8217;ll be good to go. This driver version worked for me on a Intel Corporation 82566DC Gigabit Network Connection (rev 02).</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/11/21/fedora-14-and-intel-gigabit-adaptors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Attempted haxx0ring by a botnet</title>
		<link>http://shlrm.org/wordpress/2010/11/03/attempted-haxx0ring-by-a-botnet/</link>
		<comments>http://shlrm.org/wordpress/2010/11/03/attempted-haxx0ring-by-a-botnet/#comments</comments>
		<pubDate>Wed, 03 Nov 2010 19:55:25 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[botnet]]></category>
		<category><![CDATA[script kiddie]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sshd]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=401</guid>
		<description><![CDATA[It appears that someone['s botnet] was trying to hack my little server yesterday.]]></description>
			<content:encoded><![CDATA[<p>Hooray for Logwatch.</p>
<p>It appears that someone['s botnet] was trying to hack my little server yesterday. I have a good portion of attempted logins as root from a slew of hosts. 194 separate hosts with multiple attempts from more than a few. This might explain the horrible internet connectivity problems I was having the other day.</p>
<p>Not really sure what I did to piss off some script kiddie. Perhaps I got someone&#8217;s attention? I haven&#8217;t blagged about anything controversial recently. Not even in politics. I did submit my resume to <a href="http://www.monster.com">Monster.com</a>, perhaps someone is determining if they can <a href="http://shlrm.org/wordpress/my-resume/">hire me</a> as a Systems Administrator?</p>
<p>Logwatch entries follow after the break.</p>
<p><span id="more-401"></span>These are the relevant entries from the logwatch email I received today. I&#8217;ve sanitized them just a smidge.</p>
<p><a href="#pam_unix">Pam_unix&#8217;s logwatch section</a></p>
<p><a href="#sshd">sshd&#8217;s logwatch section</a></p>
<pre><a name="pam_unix">--------------------- pam_unix Begin ------------------------</a>

 dovecot:
    Authentication Failures:
       &lt;valid user&gt;: 139 Time(s)
    Unknown Entries:
       session closed for user &lt;valid user&gt;: 139 Time(s)
       session opened for user &lt;valid user&gt; by (uid=0): 139 Time(s)

 sshd:
    Authentication Failures:
       root (189.22.10.3): 6 Time(s)
       root (189.8.88.10): 4 Time(s)
       root (222.173.107.103): 4 Time(s)
       root (112.215.7.123): 3 Time(s)
       root (122.116.133.14): 3 Time(s)
       root (190.68.61.66): 3 Time(s)
       root (212.116.138.149): 3 Time(s)
       root (220.232.206.71): 3 Time(s)
       root (91.142.242.165): 3 Time(s)
       &lt;valid user&gt; (&lt;internal network address&gt;): 2 Time(s)
       root (119.62.128.110): 2 Time(s)
       root (12.234.198.58): 2 Time(s)
       root (122.117.211.109): 2 Time(s)
       root (130.231.15.12): 2 Time(s)
       root (133.42.149.193): 2 Time(s)
       root (189.2.187.4): 2 Time(s)
       root (189.20.205.210): 2 Time(s)
       root (189.210.153.50): 2 Time(s)
       root (190.1.171.108): 2 Time(s)
       root (190.248.8.19): 2 Time(s)
       root (190.253.223.162): 2 Time(s)
       root (190.29.2.204): 2 Time(s)
       root (190.68.117.18): 2 Time(s)
       root (190.68.117.82): 2 Time(s)
       root (194.2.25.13): 2 Time(s)
       root (195.78.46.99): 2 Time(s)
       root (195.81.144.28): 2 Time(s)
       root (200.105.228.202): 2 Time(s)
       root (200.111.111.51): 2 Time(s)
       root (200.187.60.60): 2 Time(s)
       root (200.242.100.30): 2 Time(s)
       root (200.248.10.200): 2 Time(s)
       root (201.238.197.3): 2 Time(s)
       root (202.53.225.162): 2 Time(s)
       root (212.224.142.100): 2 Time(s)
       root (212.92.23.139): 2 Time(s)
       root (213.129.249.99): 2 Time(s)
       root (213.23.211.11): 2 Time(s)
       root (218.241.156.219): 2 Time(s)
       root (219.117.236.219): 2 Time(s)
       root (222.107.61.161): 2 Time(s)
       root (41.204.194.154): 2 Time(s)
       root (58.246.85.122): 2 Time(s)
       root (59.106.27.49): 2 Time(s)
       root (62.97.49.6): 2 Time(s)
       root (64.182.136.46): 2 Time(s)
       root (70.247.71.201): 2 Time(s)
       root (74.55.60.90): 2 Time(s)
       root (75.125.235.162): 2 Time(s)
       root (81.221.15.140): 2 Time(s)
       root (82.119.240.3): 2 Time(s)
       root (85.22.60.6): 2 Time(s)
       root (85.24.138.173): 2 Time(s)
       root (87.86.55.4): 2 Time(s)
       root (89.250.247.28): 2 Time(s)
       root (91.144.170.50): 2 Time(s)
       root (93.104.243.162): 2 Time(s)
       root (93.152.158.141): 2 Time(s)
       root (93.157.210.254): 2 Time(s)
       root (93.93.191.186): 2 Time(s)
       root (115.186.131.106): 1 Time(s)
       root (122.115.35.242): 1 Time(s)
       root (122.221.65.18): 1 Time(s)
       root (123.231.21.19): 1 Time(s)
       root (124.92.251.2): 1 Time(s)
       root (125.255.49.179): 1 Time(s)
       root (140.115.155.221): 1 Time(s)
       root (146.134.30.157): 1 Time(s)
       root (146.83.216.201): 1 Time(s)
       root (147.83.52.103): 1 Time(s)
       root (161.132.77.16): 1 Time(s)
       root (163.19.1.92): 1 Time(s)
       root (163.247.46.150): 1 Time(s)
       root (174.143.234.81): 1 Time(s)
       root (180.168.5.184): 1 Time(s)
       root (189.112.139.83): 1 Time(s)
       root (189.114.56.253): 1 Time(s)
       root (189.47.135.118): 1 Time(s)
       root (189.47.206.203): 1 Time(s)
       root (190.128.29.4): 1 Time(s)
       root (190.144.1.98): 1 Time(s)
       root (190.144.103.146): 1 Time(s)
       root (190.152.145.54): 1 Time(s)
       root (190.165.136.11): 1 Time(s)
       root (190.182.3.143): 1 Time(s)
       root (190.2.3.85): 1 Time(s)
       root (190.254.197.10): 1 Time(s)
       root (190.255.182.106): 1 Time(s)
       root (194.94.121.238): 1 Time(s)
       root (195.162.22.59): 1 Time(s)
       root (195.24.37.122): 1 Time(s)
       root (196.0.5.114): 1 Time(s)
       root (196.10.224.108): 1 Time(s)
       root (196.12.232.100): 1 Time(s)
       root (196.20.71.66): 1 Time(s)
       root (196.201.230.18): 1 Time(s)
       root (196.43.83.170): 1 Time(s)
       root (200.101.12.86): 1 Time(s)
       root (200.123.4.25): 1 Time(s)
       root (200.160.121.246): 1 Time(s)
       root (200.175.79.150): 1 Time(s)
       root (200.182.126.166): 1 Time(s)
       root (200.25.180.75): 1 Time(s)
       root (200.79.53.211): 1 Time(s)
       root (201.155.88.252): 1 Time(s)
       root (201.21.49.185): 1 Time(s)
       root (201.227.239.11): 1 Time(s)
       root (201.238.211.133): 1 Time(s)
       root (201.41.215.154): 1 Time(s)
       root (202.120.46.2): 1 Time(s)
       root (202.147.244.165): 1 Time(s)
       root (202.171.148.106): 1 Time(s)
       root (202.177.24.199): 1 Time(s)
       root (202.39.49.109): 1 Time(s)
       root (202.53.250.42): 1 Time(s)
       root (202.71.140.165): 1 Time(s)
       root (203.110.245.243): 1 Time(s)
       root (203.122.225.226): 1 Time(s)
       root (203.183.81.155): 1 Time(s)
       root (203.58.188.17): 1 Time(s)
       root (203.72.59.6): 1 Time(s)
       root (204.38.191.170): 1 Time(s)
       root (208.115.111.200): 1 Time(s)
       root (208.179.176.66): 1 Time(s)
       root (209.203.18.122): 1 Time(s)
       root (209.88.156.132): 1 Time(s)
       root (210.196.168.137): 1 Time(s)
       root (210.51.57.139): 1 Time(s)
       root (211.234.100.205): 1 Time(s)
       root (211.239.172.188): 1 Time(s)
       root (211.9.48.203): 1 Time(s)
       root (212.155.135.204): 1 Time(s)
       root (212.92.23.24): 1 Time(s)
       root (213.215.10.116): 1 Time(s)
       root (213.215.247.194): 1 Time(s)
       root (213.235.133.209): 1 Time(s)
       root (213.97.211.74): 1 Time(s)
       root (217.119.231.143): 1 Time(s)
       root (217.15.197.136): 1 Time(s)
       root (217.159.148.62): 1 Time(s)
       root (217.166.213.218): 1 Time(s)
       root (217.220.124.90): 1 Time(s)
       root (217.8.80.9): 1 Time(s)
       root (219.234.81.209): 1 Time(s)
       root (219.94.144.73): 1 Time(s)
       root (24.75.21.4): 1 Time(s)
       root (38.112.30.222): 1 Time(s)
       root (58.215.75.55): 1 Time(s)
       root (58.221.249.66): 1 Time(s)
       root (59.124.223.238): 1 Time(s)
       root (59.124.78.179): 1 Time(s)
       root (61.31.200.49): 1 Time(s)
       root (62.129.164.36): 1 Time(s)
       root (62.94.161.156): 1 Time(s)
       root (64.117.46.243): 1 Time(s)
       root (64.164.215.91): 1 Time(s)
       root (64.185.113.237): 1 Time(s)
       root (65.111.177.12): 1 Time(s)
       root (65.111.177.212): 1 Time(s)
       root (65.70.247.20): 1 Time(s)
       root (66.115.174.80): 1 Time(s)
       root (66.240.254.216): 1 Time(s)
       root (67.222.236.19): 1 Time(s)
       root (69.159.244.44): 1 Time(s)
       root (72.51.43.242): 1 Time(s)
       root (72.54.128.19): 1 Time(s)
       root (72.90.111.10): 1 Time(s)
       root (74.189.117.98): 1 Time(s)
       root (74.80.48.25): 1 Time(s)
       root (75.125.69.82): 1 Time(s)
       root (75.160.204.13): 1 Time(s)
       root (79.170.186.119): 1 Time(s)
       root (79.38.79.53): 1 Time(s)
       root (80.26.69.233): 1 Time(s)
       root (81.168.103.177): 1 Time(s)
       root (81.18.250.224): 1 Time(s)
       root (81.255.107.145): 1 Time(s)
       root (82.145.241.5): 1 Time(s)
       root (82.187.183.124): 1 Time(s)
       root (83.238.170.128): 1 Time(s)
       root (84.19.182.97): 1 Time(s)
       root (84.40.53.32): 1 Time(s)
       root (85.145.196.239): 1 Time(s)
       root (85.214.25.226): 1 Time(s)
       root (87.244.204.196): 1 Time(s)
       root (87.63.208.238): 1 Time(s)
       root (88.40.179.242): 1 Time(s)
       root (89.251.106.242): 1 Time(s)
       root (89.39.28.239): 1 Time(s)
       root (93.82.242.114): 1 Time(s)
       root (94.127.136.74): 1 Time(s)
       root (94.83.231.154): 1 Time(s)

 ---------------------- pam_unix End -------------------------
</pre>
<p>Here&#8217;s the section from sshd itself. It&#8217;s a bit more noisier than just reporting authentication failures.</p>
<pre> <a name="sshd">--------------------- SSHD Begin ------------------------</a>

 Users logging in through sshd:
    &lt;valid user&gt;:
       &lt;internal network ip&gt; (raziel.shlrm.org): 2 times

 Refused incoming connections:
       110.8.75.19: 1 Time(s)
       165.Red-217-127-98.staticIP.rima-tde.net: 1 Time(s)
       190.144.1.98: 1 Time(s)
       221.232.155.6: 1 Time(s)
       222.237.78.139: 2 Time(s)
       60.191.47.54: 1 Time(s)
       60.195.250.54: 1 Time(s)
       74.203.204.99: 2 Time(s)
       78.97.93.150: 1 Time(s)
       ms.onpcs.com: 2 Time(s)
       nc-65-40-234-248.sta.embarqhsd.net: 1 Time(s)
       p23171-ipbffx02osakakita.osaka.ocn.ne.jp: 2 Time(s)
       sphinx.wbsconnect.com: 1 Time(s)

 Error in PAM authentication:
    User not known to the underlying authentication module for root from 112.215.7.123 : 3 Time(s)
    User not known to the underlying authentication module for root from 115.186.131.106 : 1 Time(s)
    User not known to the underlying authentication module for root from 119.62.128.110 : 2 Time(s)
    User not known to the underlying authentication module for root from 12.234.198.58 : 2 Time(s)
    User not known to the underlying authentication module for root from 122.115.35.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 122.116.133.14 : 3 Time(s)
    User not known to the underlying authentication module for root from 122.117.211.109 : 2 Time(s)
    User not known to the underlying authentication module for root from 122.221.65.18 : 1 Time(s)
    User not known to the underlying authentication module for root from 123.231.21.19 : 1 Time(s)
    User not known to the underlying authentication module for root from 124.92.251.2 : 1 Time(s)
    User not known to the underlying authentication module for root from 125.255.49.179 : 1 Time(s)
    User not known to the underlying authentication module for root from 130.231.15.12 : 2 Time(s)
    User not known to the underlying authentication module for root from 133.42.149.193 : 2 Time(s)
    User not known to the underlying authentication module for root from 140.115.155.221 : 1 Time(s)
    User not known to the underlying authentication module for root from 146.134.30.157 : 1 Time(s)
    User not known to the underlying authentication module for root from 146.83.216.201 : 1 Time(s)
    User not known to the underlying authentication module for root from 147.83.52.103 : 1 Time(s)
    User not known to the underlying authentication module for root from 161.132.77.16 : 1 Time(s)
    User not known to the underlying authentication module for root from 163.19.1.92 : 1 Time(s)
    User not known to the underlying authentication module for root from 163.247.46.150 : 1 Time(s)
    User not known to the underlying authentication module for root from 174.143.234.81 : 1 Time(s)
    User not known to the underlying authentication module for root from 180.168.5.184 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.112.139.83 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.114.56.253 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.2.187.4 : 2 Time(s)
    User not known to the underlying authentication module for root from 189.20.205.210 : 2 Time(s)
    User not known to the underlying authentication module for root from 189.210.153.50 : 2 Time(s)
    User not known to the underlying authentication module for root from 189.22.10.3 : 6 Time(s)
    User not known to the underlying authentication module for root from 189.47.135.118 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.47.206.203 : 1 Time(s)
    User not known to the underlying authentication module for root from 189.8.88.10 : 4 Time(s)
    User not known to the underlying authentication module for root from 190.1.171.108 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.128.29.4 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.144.1.98 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.144.103.146 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.152.145.54 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.165.136.11 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.182.3.143 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.2.3.85 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.248.8.19 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.253.223.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.254.197.10 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.255.182.106 : 1 Time(s)
    User not known to the underlying authentication module for root from 190.29.2.204 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.68.117.18 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.68.117.82 : 2 Time(s)
    User not known to the underlying authentication module for root from 190.68.61.66 : 3 Time(s)
    User not known to the underlying authentication module for root from 194.2.25.13 : 2 Time(s)
    User not known to the underlying authentication module for root from 194.94.121.238 : 1 Time(s)
    User not known to the underlying authentication module for root from 195.162.22.59 : 1 Time(s)
    User not known to the underlying authentication module for root from 195.24.37.122 : 1 Time(s)
    User not known to the underlying authentication module for root from 195.78.46.99 : 2 Time(s)
    User not known to the underlying authentication module for root from 195.81.144.28 : 2 Time(s)
    User not known to the underlying authentication module for root from 196.0.5.114 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.10.224.108 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.12.232.100 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.20.71.66 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.201.230.18 : 1 Time(s)
    User not known to the underlying authentication module for root from 196.43.83.170 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.101.12.86 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.105.228.202 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.111.111.51 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.123.4.25 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.160.121.246 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.175.79.150 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.182.126.166 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.187.60.60 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.242.100.30 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.248.10.200 : 2 Time(s)
    User not known to the underlying authentication module for root from 200.25.180.75 : 1 Time(s)
    User not known to the underlying authentication module for root from 200.79.53.211 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.155.88.252 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.21.49.185 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.227.239.11 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.238.197.3 : 2 Time(s)
    User not known to the underlying authentication module for root from 201.238.211.133 : 1 Time(s)
    User not known to the underlying authentication module for root from 201.41.215.154 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.120.46.2 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.147.244.165 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.171.148.106 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.177.24.199 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.39.49.109 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.53.225.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 202.53.250.42 : 1 Time(s)
    User not known to the underlying authentication module for root from 202.71.140.165 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.110.245.243 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.122.225.226 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.183.81.155 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.58.188.17 : 1 Time(s)
    User not known to the underlying authentication module for root from 203.72.59.6 : 1 Time(s)
    User not known to the underlying authentication module for root from 204.38.191.170 : 1 Time(s)
    User not known to the underlying authentication module for root from 208.115.111.200 : 1 Time(s)
    User not known to the underlying authentication module for root from 208.179.176.66 : 1 Time(s)
    User not known to the underlying authentication module for root from 209.203.18.122 : 1 Time(s)
    User not known to the underlying authentication module for root from 209.88.156.132 : 1 Time(s)
    User not known to the underlying authentication module for root from 210.196.168.137 : 1 Time(s)
    User not known to the underlying authentication module for root from 210.51.57.139 : 1 Time(s)
    User not known to the underlying authentication module for root from 211.234.100.205 : 1 Time(s)
    User not known to the underlying authentication module for root from 211.239.172.188 : 1 Time(s)
    User not known to the underlying authentication module for root from 211.9.48.203 : 1 Time(s)
    User not known to the underlying authentication module for root from 212.116.138.149 : 3 Time(s)
    User not known to the underlying authentication module for root from 212.155.135.204 : 1 Time(s)
    User not known to the underlying authentication module for root from 212.224.142.100 : 2 Time(s)
    User not known to the underlying authentication module for root from 212.92.23.139 : 2 Time(s)
    User not known to the underlying authentication module for root from 212.92.23.24 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.129.249.99 : 2 Time(s)
    User not known to the underlying authentication module for root from 213.215.10.116 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.215.247.194 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.23.211.11 : 2 Time(s)
    User not known to the underlying authentication module for root from 213.235.133.209 : 1 Time(s)
    User not known to the underlying authentication module for root from 213.97.211.74 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.119.231.143 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.15.197.136 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.159.148.62 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.166.213.218 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.220.124.90 : 1 Time(s)
    User not known to the underlying authentication module for root from 217.8.80.9 : 1 Time(s)
    User not known to the underlying authentication module for root from 218.241.156.219 : 2 Time(s)
    User not known to the underlying authentication module for root from 219.117.236.219 : 2 Time(s)
    User not known to the underlying authentication module for root from 219.234.81.209 : 1 Time(s)
    User not known to the underlying authentication module for root from 219.94.144.73 : 1 Time(s)
    User not known to the underlying authentication module for root from 220.232.206.71 : 3 Time(s)
    User not known to the underlying authentication module for root from 222.107.61.161 : 2 Time(s)
    User not known to the underlying authentication module for root from 222.173.107.103 : 4 Time(s)
    User not known to the underlying authentication module for root from 24.75.21.4 : 1 Time(s)
    User not known to the underlying authentication module for root from 38.112.30.222 : 1 Time(s)
    User not known to the underlying authentication module for root from 41.204.194.154 : 2 Time(s)
    User not known to the underlying authentication module for root from 58.215.75.55 : 1 Time(s)
    User not known to the underlying authentication module for root from 58.221.249.66 : 1 Time(s)
    User not known to the underlying authentication module for root from 58.246.85.122 : 2 Time(s)
    User not known to the underlying authentication module for root from 59.106.27.49 : 2 Time(s)
    User not known to the underlying authentication module for root from 59.124.223.238 : 1 Time(s)
    User not known to the underlying authentication module for root from 59.124.78.179 : 1 Time(s)
    User not known to the underlying authentication module for root from 61.31.200.49 : 1 Time(s)
    User not known to the underlying authentication module for root from 62.129.164.36 : 1 Time(s)
    User not known to the underlying authentication module for root from 62.94.161.156 : 1 Time(s)
    User not known to the underlying authentication module for root from 62.97.49.6 : 2 Time(s)
    User not known to the underlying authentication module for root from 64.117.46.243 : 1 Time(s)
    User not known to the underlying authentication module for root from 64.164.215.91 : 1 Time(s)
    User not known to the underlying authentication module for root from 64.182.136.46 : 2 Time(s)
    User not known to the underlying authentication module for root from 64.185.113.237 : 1 Time(s)
    User not known to the underlying authentication module for root from 65.111.177.12 : 1 Time(s)
    User not known to the underlying authentication module for root from 65.111.177.212 : 1 Time(s)
    User not known to the underlying authentication module for root from 65.70.247.20 : 1 Time(s)
    User not known to the underlying authentication module for root from 66.115.174.80 : 1 Time(s)
    User not known to the underlying authentication module for root from 66.240.254.216 : 1 Time(s)
    User not known to the underlying authentication module for root from 67.222.236.19 : 1 Time(s)
    User not known to the underlying authentication module for root from 69.159.244.44 : 1 Time(s)
    User not known to the underlying authentication module for root from 70.247.71.201 : 2 Time(s)
    User not known to the underlying authentication module for root from 72.51.43.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 72.54.128.19 : 1 Time(s)
    User not known to the underlying authentication module for root from 72.90.111.10 : 1 Time(s)
    User not known to the underlying authentication module for root from 74.189.117.98 : 1 Time(s)
    User not known to the underlying authentication module for root from 74.55.60.90 : 2 Time(s)
    User not known to the underlying authentication module for root from 74.80.48.25 : 1 Time(s)
    User not known to the underlying authentication module for root from 75.125.235.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 75.125.69.82 : 1 Time(s)
    User not known to the underlying authentication module for root from 75.160.204.13 : 1 Time(s)
    User not known to the underlying authentication module for root from 79.170.186.119 : 1 Time(s)
    User not known to the underlying authentication module for root from 79.38.79.53 : 1 Time(s)
    User not known to the underlying authentication module for root from 80.26.69.233 : 1 Time(s)
    User not known to the underlying authentication module for root from 81.168.103.177 : 1 Time(s)
    User not known to the underlying authentication module for root from 81.18.250.224 : 1 Time(s)
    User not known to the underlying authentication module for root from 81.221.15.140 : 2 Time(s)
    User not known to the underlying authentication module for root from 81.255.107.145 : 1 Time(s)
    User not known to the underlying authentication module for root from 82.119.240.3 : 2 Time(s)
    User not known to the underlying authentication module for root from 82.145.241.5 : 1 Time(s)
    User not known to the underlying authentication module for root from 82.187.183.124 : 1 Time(s)
    User not known to the underlying authentication module for root from 83.238.170.128 : 1 Time(s)
    User not known to the underlying authentication module for root from 84.19.182.97 : 1 Time(s)
    User not known to the underlying authentication module for root from 84.40.53.32 : 1 Time(s)
    User not known to the underlying authentication module for root from 85.145.196.239 : 1 Time(s)
    User not known to the underlying authentication module for root from 85.214.25.226 : 1 Time(s)
    User not known to the underlying authentication module for root from 85.22.60.6 : 2 Time(s)
    User not known to the underlying authentication module for root from 85.24.138.173 : 2 Time(s)
    User not known to the underlying authentication module for root from 87.244.204.196 : 1 Time(s)
    User not known to the underlying authentication module for root from 87.63.208.238 : 1 Time(s)
    User not known to the underlying authentication module for root from 87.86.55.4 : 2 Time(s)
    User not known to the underlying authentication module for root from 88.40.179.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 89.250.247.28 : 2 Time(s)
    User not known to the underlying authentication module for root from 89.251.106.242 : 1 Time(s)
    User not known to the underlying authentication module for root from 89.39.28.239 : 1 Time(s)
    User not known to the underlying authentication module for root from 91.142.242.165 : 3 Time(s)
    User not known to the underlying authentication module for root from 91.144.170.50 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.104.243.162 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.152.158.141 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.157.210.254 : 2 Time(s)
    User not known to the underlying authentication module for root from 93.82.242.114 : 1 Time(s)
    User not known to the underlying authentication module for root from 93.93.191.186 : 2 Time(s)
    User not known to the underlying authentication module for root from 94.127.136.74 : 1 Time(s)
    User not known to the underlying authentication module for root from 94.83.231.154 : 1 Time(s)

 **Unmatched Entries**
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(adsl-pool2-130.metrotel.net.co) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(208-115-111-200-reverse.wowrack.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(189-20-205-210.customer.tdatabrasil.net.br) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(5a.3c.374a.static.theplanet.com) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(host89-251-106-242.hnet.ru) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(12-177-111-65.serverpronto.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(74-203-204-99.static.twtelecom.net) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(adsl-pool2-143.metrotel.net.co) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(222-237-78-139.tongkni.co.kr) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(fw.mairie-rueilmalmaison.fr) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(host148-106.ipaddress.jp) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(196.201.230.18.reverse.kdn.co.ke) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(170.83-43-196.Admin.morogoro.ttcldata.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(74-80-48-25.GLB.dyn.lusfiber.net.48.80.74.in-addr.arpa) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(189-210-153-50.static.axtel.net) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(212-177-111-65.serverpronto.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(pin-064-185-113-237.cust.pocketinet.com) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(su93254216.aspadmin.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(75.25-180.uio.satnet.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(slavierobsb253.static.gvt.net.br) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(austrodach-trading-fo.b.astral.ro) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(q-224.n-81.18.250.qore.nl) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(dsl-201-155-88-252-sta.prod-empresarial.com.mx) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(static-Adsl190-248-8-19.une.net.co) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(ns.km20838-05.keymachine.de) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(adsl-pool2-108.metrotel.net.co) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(pcpQLOGICpcs) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(server150.fiscalia.cl) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(217-220-124-90-static.albacom.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(202-177-24-199.kddi.net.hk) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(93-93-191-186.aspserveur.com) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(dweb35.webfaction.com) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(server.colo250-042.indo.net.id) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(static-adsl190-29-2-204.une.net.co) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(mail.tbmg.com.au) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(89-39-28-239.samtv.ro) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(201-41-215-154.bnut3300.ipd.brasiltelecom.net.br) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(host-49-6.pool.intred.it) failed : 2 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(HOST.FLGR.BG) failed : 3 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(static.kpn.net) failed : 1 time(s)
 syslogin_perform_logout: logout() returned an error : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(customer-static-2-3-85.iplannetworks.net) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(0x573fd0ee.cpe.ge-0-1-0-1101.arcnqu1.customer.tele.dk) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(202.204.244.87.in-addr.arpa) failed : 1 time(s)
 warning: /etc/hosts.allow, line 8: can't verify hostname: gethostbyname(payweb.surguttel.ru) failed : 1 time(s)

 ---------------------- SSHD End -------------------------
</pre>
<p>I&#8217;m reasonably confident that syslogin_perform_logout error is from a botched VM. Fedora 14 needs a more recent kernel than my DomU&#8217;s are getting and so that box is hosed. My two attempts to update to Fedora 14 have ended horribly, but that&#8217;s a different story.</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/11/03/attempted-haxx0ring-by-a-botnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building ruby 1.9 on Fedora 13</title>
		<link>http://shlrm.org/wordpress/2010/06/19/building-ruby-1-9-on-fedora-13/</link>
		<comments>http://shlrm.org/wordpress/2010/06/19/building-ruby-1-9-on-fedora-13/#comments</comments>
		<pubDate>Sat, 19 Jun 2010 18:19:23 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=378</guid>
		<description><![CDATA[Was harder than it should&#8217;ve been. I got annoyed. You need to install openssl-devel, zlib-devel, bison, gcc, make, patch, tar, and maybe gcc-c++ (although I don&#8217;t think this one is needed). Go get the latest ruby 1.9 source, as of this writing 1.9-p378, and extract it somewhere. Then go get the patches on this bug, <a href='http://shlrm.org/wordpress/2010/06/19/building-ruby-1-9-on-fedora-13/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>Was harder than it should&#8217;ve been. I got annoyed.</p>
<p>You need to install openssl-devel, zlib-devel, bison, gcc, make, patch, tar, and maybe gcc-c++ (although I don&#8217;t think this one is needed).</p>
<p>Go get the <a href="ftp://ftp.ruby-lang.org//pub/ruby/1.9/ruby-1.9.1-p378.tar.gz">latest ruby 1.9 source</a>, as of this writing 1.9-p378, and extract it somewhere. Then go get the patches on <a href="http://redmine.ruby-lang.org/issues/show/2022#note-11">this bug, at the specific comment</a>. You will need to apply at least the openssl-build-fix patch, since fedora uses openssl 1.0 and it&#8217;s not yet into ruby 1.9. Then follow your typical ./cofnigure, make, and make install stuff. I installed mine into a prefix of /opt/ruby so that it wouldn&#8217;t affect any fedora ruby stuff that it might want. I then added ruby&#8217;s path to the end of my user&#8217;s PATH variable.</p>
<p>That&#8217;ll get you a working ruby 1.9 in Fedora.</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/06/19/building-ruby-1-9-on-fedora-13/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>xm pause testing</title>
		<link>http://shlrm.org/wordpress/2010/05/01/xm-pause-testing/</link>
		<comments>http://shlrm.org/wordpress/2010/05/01/xm-pause-testing/#comments</comments>
		<pubDate>Sun, 02 May 2010 00:05:31 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[pvops]]></category>
		<category><![CDATA[suspend]]></category>
		<category><![CDATA[xen]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=358</guid>
		<description><![CDATA[When I got xm pause working, I was quite excited. However, it doesn&#8217;t work in all cases. I&#8217;ve done some testing to figure out what combination of things cause it to fail. All of this is using xen 4.0 hypervisor, the kernel from here, and a pvops domU kernel built by hand. Using blktap2 backed <a href='http://shlrm.org/wordpress/2010/05/01/xm-pause-testing/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>When I got xm pause working, I was quite excited. However, it doesn&#8217;t work in all cases. I&#8217;ve done some testing to figure out what combination of things cause it to fail.</p>
<p>All of this is using xen 4.0 hypervisor, the kernel from <a href="http://fedorapeople.org/~myoung/dom0/">here</a>, and a <a href="http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git">pvops domU kernel</a> built by hand.</p>
<ul>
<li>Using <a href="http://lxr.xensource.com/lxr/source/tools/blktap2/README">blktap2</a> backed disks in the vhd format (vhd-util create -n name -s 1024) xm pause fails. The user-space disk devices are never released, and only a hard reboot will get it to function again.</li>
<li>Using a different driver for the blktap2, tap:tapdisk:aio, also fails to pause.</li>
<li>Using phy:/ backed disks, say through LVM works fine. The domU will pause, and resume nicely.</li>
</ul>
<p>It would seem that there is something not quite ready to be used regarding the blktap2 backend, so I wouldn&#8217;t reccomend using it.</p>
<p>I also tried to use the original tap:aio drivers, but I cannot as they don&#8217;t seem to exist. I guess I&#8217;ll be using the plain old phy:/ drivers for now. That&#8217;s not a big deal as I don&#8217;t have any second xen machine to do anything fancy that the tap:aio drivers would provide. I guess I should poke on a mailing list or something.</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/05/01/xm-pause-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>xen pv_ops domU</title>
		<link>http://shlrm.org/wordpress/2010/05/01/xen-pv_ops-domu/</link>
		<comments>http://shlrm.org/wordpress/2010/05/01/xen-pv_ops-domu/#comments</comments>
		<pubDate>Sat, 01 May 2010 23:30:19 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Source Mage]]></category>
		<category><![CDATA[W00t!]]></category>
		<category><![CDATA[pvops]]></category>
		<category><![CDATA[xen]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=354</guid>
		<description><![CDATA[&#8230;means I can finally pause/suspend a domU vm again! Finding this information should&#8217;ve been obvious, but for some reason it wasn&#8217;t. Maybe I had some silly mental block or something. Anyways, get the kernel source from here. Then build it for your architecture. If you want to build a 32-bit kernel for some 32-bit domUs, <a href='http://shlrm.org/wordpress/2010/05/01/xen-pv_ops-domu/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>&#8230;means I can finally pause/suspend a domU vm again!</p>
<p>Finding this information should&#8217;ve been obvious, but for some reason it wasn&#8217;t. Maybe I had some silly mental block or something. Anyways, get the kernel source from <a href="http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git">here</a>. Then build it for your architecture. If you want to build a 32-bit kernel for some 32-bit domUs, and you&#8217;re running on 64-bit, it&#8217;s as easy as make ARCH=i386 &lt;target&gt;. This does work and I&#8217;ve verified it. Had to fool a Fedora domU into beleiving that it really was a 32-bit system.</p>
<p>I&#8217;ve found make tarbz2-pkg to be quite handy in packaging up the kernel to be deployed.</p>
<p>I have verified that this works in Xen 3.4.2 on a patched 2.6.29.6 kernel.</p>
<p>On my Xen 4.0 test box, it fails to suspend. I&#8217;m using the blktap2 stuff, and perhaps that doesn&#8217;t pause well. As far as I understand it, that blktap2 should not affect suspending, but I&#8217;m going to test it with some logical volume based vms. I usually use the lvm backed disks anyway, but the blktap2 stuff offers some interesting features, if it were to work. Not being able to pause stuff probably isn&#8217;t good, but again, I&#8217;m not sure what&#8217;s causing it.</p>
<p>Apparently, that is what&#8217;s causing it. The domU will pause and unpause just fine when using an lvm backed disk, rather than the blktap2 ones. I should test a couple of other combinations to see if things like tap:aio will behave, as that&#8217;s needed for nifty things like remus.</p>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/05/01/xen-pv_ops-domu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Xen 4.0 released</title>
		<link>http://shlrm.org/wordpress/2010/04/07/xen-4-0-released/</link>
		<comments>http://shlrm.org/wordpress/2010/04/07/xen-4-0-released/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 12:37:45 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Source Mage]]></category>
		<category><![CDATA[W00t!]]></category>
		<category><![CDATA[rpms]]></category>
		<category><![CDATA[xen]]></category>
		<category><![CDATA[xen 4.0]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=337</guid>
		<description><![CDATA[Finally! From the official page: The Xen 4.0 release contains a number of important new features and updates including: Blktap2 – High performance VHD implementation supporting snaphots and clonces including live snapshots Netchannel2 – Support for new Smart NICs with multi-queue and SR-IOV functionality Fault Tolerance – Live transactional synchronization of VM state between physical <a href='http://shlrm.org/wordpress/2010/04/07/xen-4-0-released/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<div>
<p>Finally!</p>
<p>From the <a href="http://www.xen.org/products/xen_source.html">official   page</a>:</p>
<blockquote><p>The Xen 4.0 release contains a number of important new  features and  updates including:</p>
<ul>
<li>Blktap2 – High performance VHD implementation supporting snaphots   and clonces including live snapshots</li>
<li>Netchannel2 – Support for new Smart NICs with multi-queue and SR-IOV   functionality</li>
<li>Fault Tolerance – Live transactional synchronization of VM state   between physical servers</li>
<li>Libxenlight – New library providing higher-level control of Xen   between various toolstacks</li>
<li>PV-USB and VGA Pass-through</li>
</ul>
</blockquote>
<p>SourceMage has already updated packages for it.</p>
<p>There’s a repository and src RPMs available for Fedora <a href="http://fedorapeople.org/%7Emyoung/dom0/">here</a>. Specifically  the <a href="http://fedorapeople.org/%7Emyoung/dom0/src/xen-4.0.0-0.7.fc12.src.rpm">Xen   4.0 src RPM</a>. I’ll try to remember to fire up a build on my xen DomU  that I use to build RPMs for me :)</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2010/04/07/xen-4-0-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fedora 12 Xen RPMs</title>
		<link>http://shlrm.org/wordpress/2009/11/17/fedora-12-xen-rpms/</link>
		<comments>http://shlrm.org/wordpress/2009/11/17/fedora-12-xen-rpms/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 20:02:57 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[constantine]]></category>
		<category><![CDATA[rpm]]></category>
		<category><![CDATA[xen]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=301</guid>
		<description><![CDATA[I built these on a recently updated Fedora 12 box. I haven&#8217;t yet had an opportunity to test them. If you do use them and they work great, or not, post in the comments please. xen-3.4.2-1.fc12.x86_64.rpm xen-debuginfo-3.4.2-1.fc12.x86_64.rpm xen-devel-3.4.2-1.fc12.x86_64.rpm xen-doc-3.4.2-1.fc12.x86_64.rpm xen-hypervisor-3.4.2-1.fc12.x86_64.rpm xen-libs-3.4.2-1.fc12.x86_64.rpm xen-runtime-3.4.2-1.fc12.x86_64.rpm]]></description>
			<content:encoded><![CDATA[<p>I built these on a recently updated Fedora 12 box. I haven&#8217;t yet had an opportunity to test them. If you do use them and they work great, or not, post in the comments please.</p>
<ul>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-3.4.2-1.fc12.x86_64.rpm"> xen-3.4.2-1.fc12.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-debuginfo-3.4.2-1.fc12.x86_64.rpm"> xen-debuginfo-3.4.2-1.fc12.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-devel-3.4.2-1.fc12.x86_64.rpm"> xen-devel-3.4.2-1.fc12.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-doc-3.4.2-1.fc12.x86_64.rpm"> xen-doc-3.4.2-1.fc12.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-hypervisor-3.4.2-1.fc12.x86_64.rpm"> xen-hypervisor-3.4.2-1.fc12.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-libs-3.4.2-1.fc12.x86_64.rpm"> xen-libs-3.4.2-1.fc12.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/f12/xen/xen-runtime-3.4.2-1.fc12.x86_64.rpm"> xen-runtime-3.4.2-1.fc12.x86_64.rpm</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2009/11/17/fedora-12-xen-rpms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Xen 3.4.2 rpms for Fedora 11 x86_64</title>
		<link>http://shlrm.org/wordpress/2009/11/12/xen-3-4-2-rpms-for-fedora-11-x86_64/</link>
		<comments>http://shlrm.org/wordpress/2009/11/12/xen-3-4-2-rpms-for-fedora-11-x86_64/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 15:46:46 +0000</pubDate>
		<dc:creator>David Kowis</dc:creator>
				<category><![CDATA[fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[W00t!]]></category>
		<category><![CDATA[rpm]]></category>
		<category><![CDATA[xen]]></category>

		<guid isPermaLink="false">http://shlrm.org/wordpress/?p=297</guid>
		<description><![CDATA[I was using xen 3.4.1 on my fedora 11 Domain0, but I couldn&#8217;t ever suspend anything. xm save always failed. Someone on IRC suggested that it was the guest kernel that was to blame. Turns out it was xen 3.4.1. After many hours searching the intertubes for a srpm or a spec file for building <a href='http://shlrm.org/wordpress/2009/11/12/xen-3-4-2-rpms-for-fedora-11-x86_64/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>I was using xen 3.4.1 on my fedora 11 Domain0, but I couldn&#8217;t ever suspend anything. xm save always failed. Someone on IRC suggested that it was the guest kernel that was to blame. Turns out it was xen 3.4.1.</p>
<p>After many hours searching the intertubes for a srpm or a spec file for building xen 3.4.2 for fedora, I decided that I would hack <a href="http://bderzhavets.wordpress.com/2009/08/20/setup-libvirt-0-7-0-6-xen-3-4-1-dom0-on-to-fedora-11-64-bit/">an existing one</a> to 3.4.2 and hope for the best.</p>
<p>It built after I removed a few patches. The patches mostly complained about being already applied, so I assume the bugs the patches were addressing were fixed in 3.4.2. I have generated <a href="http://shlrm.org/rpms/xen/">rpms for x86_64</a> and put the <a href="http://shlrm.org/rpms/xen/xen-3.4.2.spec">spec file</a> up on my site. Enjoy.</p>
<ul>
<li><a href="http://shlrm.org/rpms/xen/xen-3.4.2-5.fc11.x86_64.rpm"> xen-3.4.2-5.fc11.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/xen/xen-debuginfo-3.4.2-5.fc11.x86_64.rpm"> xen-debuginfo-3.4.2-5.fc11.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/xen/xen-devel-3.4.2-5.fc11.x86_64.rpm"> xen-devel-3.4.2-5.fc11.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/xen/xen-doc-3.4.2-5.fc11.x86_64.rpm"> xen-doc-3.4.2-5.fc11.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/xen/xen-hypervisor-3.4.2-5.fc11.x86_64.rpm"> xen-hypervisor-3.4.2-5.fc11.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/xen/xen-libs-3.4.2-5.fc11.x86_64.rpm"> xen-libs-3.4.2-5.fc11.x86_64.rpm</a></li>
<li><a href="http://shlrm.org/rpms/xen/xen-runtime-3.4.2-5.fc11.x86_64.rpm"> xen-runtime-3.4.2-5.fc11.x86_64.rpm</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://shlrm.org/wordpress/2009/11/12/xen-3-4-2-rpms-for-fedora-11-x86_64/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

