I faced similar issues with my R270, in my case *entirely removing* the
vmport=off option (its presence alone caused issues) and attaching the GPU
to a ioh3420 device instead of directly to the PCI bus fixed the issue:
https://www.redhat.com/archives/vfio-users/2015-December/msg00211.html
Like
On 2016-01-21 12:32 PM, Eric Griffith wrote:
On Jan 17, 2016 16:10, "Stewart Adam" mailto:maill...@diffingo.com>> wrote:
>
> On 2016-01-17 1:27 PM, Eric Griffith wrote:
>>
>> On Jan 17, 2016 13:15, "Stewart Adam" mailto:maill...@diffingo.com>
On 2016-01-17 1:27 PM, Eric Griffith wrote:
On Jan 17, 2016 13:15, "Stewart Adam" mailto:maill...@diffingo.com>> wrote:
>
> On 2016-01-07 11:30 AM, Eric Griffith wrote:
>>
>> My problem is.. The Win7 (and Win8.1) guests are perfectly fine and stable
>>
On 2016-01-07 11:30 AM, Eric Griffith wrote:
My problem is.. The Win7 (and Win8.1) guests are perfectly fine and stable
until I try to install the amd crimson drivers. Then Windows BSODs, yelling
about an unhandled exception. If I unpack the install and install things
piecemeal, then I can instal
Based on my research, the version of SeaBIOS included with Fedora 23 w/
virt-preview (1.9.0) should support booting from VFIO disks, both BLK and
SCSI. However, getting "No bootable device" back from SeaBIOS after changing
my virtio-blk disks to virtio-scsi. Any ideas as to why?
Thanks,
Stewar
Hi all,
I've had BIOS Q35-based Windows 7 guest with a Radeon R9 270X GPU
passthrough working very well with F21, but recently I upgraded to F23 and
also needed to reformat my guest so I started from scratch.
Using virt-manager I created a new BIOS Q35 machine using the
script wrapper trick
