<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EVE-NG PA booting issue in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/eve-ng-pa-booting-issue/m-p/456630#M1414</link>
    <description>&lt;P&gt;Just ran into the same problem.&amp;nbsp; For me it was because the disk image was missing from the paloalto directory in /opt/unetlab/addons/qemu/ .&amp;nbsp; Moving the file virtioa.qcow2 into the correct folder fixed it for me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jan 2022 06:34:41 GMT</pubDate>
    <dc:creator>JoeLentz</dc:creator>
    <dc:date>2022-01-04T06:34:41Z</dc:date>
    <item>
      <title>EVE-NG PA booting issue</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/eve-ng-pa-booting-issue/m-p/357021#M1028</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a eve-ng laptop that i'm planning to use for practice. I have installed the KVM file and activated it as well as added it to the eve-ng lab. However, when i start the device. I get the error message "No bootable Device". This device is currently configured to use PA8.0.5 in the EVE-NG environment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have Attached a screenshot of the boot messages to this post. Please, help me take a look at it and advice what to do. I'm just learning to setup my own EVE-NG lab to start practicing on my own. So, any help will be much appreciated. Also, you can see the booting messages below.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;###########################################&lt;/P&gt;&lt;P&gt;.......... No configuration methods s&lt;BR /&gt;ucceeded (&lt;A href="http://ipxe.org/040ee119" target="_blank"&gt;http://ipxe.org/040ee119&lt;/A&gt;)&lt;BR /&gt;No more network devices&lt;/P&gt;&lt;P&gt;Booting from ROM...&lt;BR /&gt;iPXE (PCI 00:04.0) starting execution...ok&lt;BR /&gt;iPXE initialising devices...ok&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;iPXE 1.0.0+ (0600d) -- Open Source Network Boot Firmware -- &lt;A href="http://ipxe.org" target="_blank"&gt;http://ipxe.org&lt;/A&gt;&lt;BR /&gt;Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT&lt;/P&gt;&lt;P&gt;net1: 50:00:00:01:00:01 using 82540em on 0000:00:04.0 (open)&lt;BR /&gt;[Link:up, TX:0 TXE:0 RX:0 RXE:0]&lt;BR /&gt;Configuring (net1 50:00:00:01:00:01)................. No configuration methods s&lt;BR /&gt;ucceeded (&lt;A href="http://ipxe.org/040ee119" target="_blank"&gt;http://ipxe.org/040ee119&lt;/A&gt;)&lt;BR /&gt;No more network devices&lt;/P&gt;&lt;P&gt;Booting from ROM...&lt;BR /&gt;iPXE (PCI 00:05.0) starting execution...ok&lt;BR /&gt;iPXE initialising devices...ok&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;iPXE 1.0.0+ (0600d) -- Open Source Network Boot Firmware -- &lt;A href="http://ipxe.org" target="_blank"&gt;http://ipxe.org&lt;/A&gt;&lt;BR /&gt;Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT&lt;/P&gt;&lt;P&gt;net2: 50:00:00:01:00:02 using 82540em on 0000:00:05.0 (open)&lt;BR /&gt;[Link:up, TX:0 TXE:0 RX:0 RXE:0]&lt;BR /&gt;Configuring (net2 50:00:00:01:00:02)................. No configuration methods s&lt;BR /&gt;ucceeded (&lt;A href="http://ipxe.org/040ee119" target="_blank"&gt;http://ipxe.org/040ee119&lt;/A&gt;)&lt;BR /&gt;No more network devices&lt;/P&gt;&lt;P&gt;Booting from ROM...&lt;BR /&gt;iPXE (PCI 00:06.0) starting execution...ok&lt;BR /&gt;iPXE initialising devices...ok&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;iPXE 1.0.0+ (0600d) -- Open Source Network Boot Firmware -- &lt;A href="http://ipxe.org" target="_blank"&gt;http://ipxe.org&lt;/A&gt;&lt;BR /&gt;Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT&lt;/P&gt;&lt;P&gt;net3: 50:00:00:01:00:03 using 82540em on 0000:00:06.0 (open)&lt;BR /&gt;[Link:up, TX:0 TXE:0 RX:0 RXE:0]&lt;BR /&gt;Configuring (net3 50:00:00:01:00:03)................. No configuration methods s&lt;BR /&gt;ucceeded (&lt;A href="http://ipxe.org/040ee119" target="_blank"&gt;http://ipxe.org/040ee119&lt;/A&gt;)&lt;BR /&gt;No more network devices&lt;/P&gt;&lt;P&gt;No bootable device.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2020 19:18:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/eve-ng-pa-booting-issue/m-p/357021#M1028</guid>
      <dc:creator>donphila2006</dc:creator>
      <dc:date>2020-10-18T19:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: EVE-NG PA booting issue</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/eve-ng-pa-booting-issue/m-p/456630#M1414</link>
      <description>&lt;P&gt;Just ran into the same problem.&amp;nbsp; For me it was because the disk image was missing from the paloalto directory in /opt/unetlab/addons/qemu/ .&amp;nbsp; Moving the file virtioa.qcow2 into the correct folder fixed it for me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 06:34:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/eve-ng-pa-booting-issue/m-p/456630#M1414</guid>
      <dc:creator>JoeLentz</dc:creator>
      <dc:date>2022-01-04T06:34:41Z</dc:date>
    </item>
  </channel>
</rss>

