<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Virsh on A Random Walk Down Tech Street</title>
    <link>https://dustymabe.com/tags/virsh/</link>
    <description>Recent content in Virsh on A Random Walk Down Tech Street</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Jan 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dustymabe.com/tags/virsh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>virt-install: boot from specific kernel/initrd just for install</title>
      <link>https://dustymabe.com/2020/01/30/virt-install-boot-from-specific-kernel/initrd-just-for-install/</link>
      <pubDate>Thu, 30 Jan 2020 00:00:00 +0000</pubDate>
      <guid>https://dustymabe.com/2020/01/30/virt-install-boot-from-specific-kernel/initrd-just-for-install/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;For some time now with&#xA;&lt;a href=&#34;https://www.mankier.com/1/virt-install&#34;&gt;virt-install&lt;/a&gt;&#xA;(developed under &lt;a href=&#34;https://virt-manager.org/&#34;&gt;virt-manager&lt;/a&gt;)&#xA;you have been able to specify a kernel and initial ramdisk to&#xA;start a VM with. The only problem is that the VM will always&#xA;start with that kernel/initrd (unless you change the definition&#xA;manually). If you are rapidly testing operating system installations&#xA;this can be problematic.&lt;/p&gt;&#xA;&lt;p&gt;On the one hand, providing the kernel/initrd allows one to automate&#xA;the install process from a Linux terminal, or even a script, by&#xA;specifying the kernel/initrd and also the kernel command line options.&#xA;However, it only gives us half the picture, because you&amp;rsquo;d then have to&#xA;hand edit the libvirt definition of the machine to see if the&#xA;installed machine was viable, &lt;strong&gt;OR&lt;/strong&gt; you&amp;rsquo;d be lazy and just throw away&#xA;the installed machine and assume it was good because the installation&#xA;process finished without error; &lt;strong&gt;BAD&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
