<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Finding a Safe Mac OS GPU for VMs	</title>
	<atom:link href="/finding-a-safe-mac-os-gpu-for-vms/feed/" rel="self" type="application/rss+xml" />
	<link>/finding-a-safe-mac-os-gpu-for-vms/</link>
	<description>Your baremetal source for virtual news</description>
	<lastBuildDate>Fri, 06 Nov 2020 21:25:27 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.2.2</generator>
	<item>
		<title>
		By: IntoGraphics		</title>
		<link>/finding-a-safe-mac-os-gpu-for-vms/#comment-140</link>

		<dc:creator><![CDATA[IntoGraphics]]></dc:creator>
		<pubDate>Fri, 06 Nov 2020 21:25:27 +0000</pubDate>
		<guid isPermaLink="false">/?p=2833#comment-140</guid>

					<description><![CDATA[According to The PCI ID Repository a few of the Device IDs, marked with ???, have a deletion request because they are &quot;Not Used&quot;. &lt;a href=&quot;https://pci-ids.ucw.cz/&quot; rel=&quot;nofollow ugc&quot;&gt;https://pci-ids.ucw.cz/&lt;/a&gt;]]></description>
			<content:encoded><![CDATA[<p>According to The PCI ID Repository a few of the Device IDs, marked with ???, have a deletion request because they are &#8220;Not Used&#8221;. <a href="https://pci-ids.ucw.cz/" rel="nofollow ugc">https://pci-ids.ucw.cz/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nicholas Sherlock		</title>
		<link>/finding-a-safe-mac-os-gpu-for-vms/#comment-117</link>

		<dc:creator><![CDATA[Nicholas Sherlock]]></dc:creator>
		<pubDate>Sun, 05 Jul 2020 09:51:27 +0000</pubDate>
		<guid isPermaLink="false">/?p=2833#comment-117</guid>

					<description><![CDATA[I bought the exact Sapphire Radeon RX 580 Pulse model mentioned but unfortunately I do have VM hangs on subsequent boots:

&lt;code&gt;vfio-pci 0000:03:00.0: Refused to change power state, currently in D3
vfio-pci 0000:03:00.1: Refused to change power state, currently in D3
vfio-pci 0000:03:00.0: Refused to change power state, currently in D3
vfio-pci 0000:03:00.1: Refused to change power state, currently in D3
vfio-pci 0000:03:00.0: Refused to change power state, currently in D3
vfio-pci 0000:03:00.0: timed out waiting for pending transaction; performing function level reset anyway
vfio-pci 0000:03:00.0: not ready 1023ms after FLR; waiting
vfio-pci 0000:03:00.0: not ready 2047ms after FLR; waiting
vfio-pci 0000:03:00.0: not ready 4095ms after FLR; waiting
vfio-pci 0000:03:00.0: not ready 8191ms after FLR; waiting
vfio-pci 0000:03:00.0: not ready 16383ms after FLR; waiting
vfio-pci 0000:03:00.0: not ready 32767ms after FLR; waiting&lt;/code&gt;

Sometimes it does boot that second time successfully, I think it just depends on exactly what internal states the previous VM left the card in. (Booting a guest a second time has about a 50% success rate)]]></description>
			<content:encoded><![CDATA[<p>I bought the exact Sapphire Radeon RX 580 Pulse model mentioned but unfortunately I do have VM hangs on subsequent boots:</p>
<p><code>vfio-pci 0000:03:00.0: Refused to change power state, currently in D3<br />
vfio-pci 0000:03:00.1: Refused to change power state, currently in D3<br />
vfio-pci 0000:03:00.0: Refused to change power state, currently in D3<br />
vfio-pci 0000:03:00.1: Refused to change power state, currently in D3<br />
vfio-pci 0000:03:00.0: Refused to change power state, currently in D3<br />
vfio-pci 0000:03:00.0: timed out waiting for pending transaction; performing function level reset anyway<br />
vfio-pci 0000:03:00.0: not ready 1023ms after FLR; waiting<br />
vfio-pci 0000:03:00.0: not ready 2047ms after FLR; waiting<br />
vfio-pci 0000:03:00.0: not ready 4095ms after FLR; waiting<br />
vfio-pci 0000:03:00.0: not ready 8191ms after FLR; waiting<br />
vfio-pci 0000:03:00.0: not ready 16383ms after FLR; waiting<br />
vfio-pci 0000:03:00.0: not ready 32767ms after FLR; waiting</code></p>
<p>Sometimes it does boot that second time successfully, I think it just depends on exactly what internal states the previous VM left the card in. (Booting a guest a second time has about a 50% success rate)</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 32/47 objects using disk
Page Caching using disk 
Minified using disk

Served from: passthroughpo.st @ 2023-05-24 22:11:09 by W3 Total Cache
-->