Geniuses, I''ve been trying to get VGA pass-through working on Windows 8, however I''ve been running into a few issues. Currently I can get Windows 8 running flawlessly without VGA pass-through, however I''m planning on using it for gaming, so this wont work. When I start windows 8, I am able to get past the install portion of the DVD, however it hangs on "Getting devices ready.. (n%)". Hardware Information : AMD Fx6300 ASUS M5a99x evo r2.0 16GB RAM 6670 Radeon HD - Dom0 7850 Radeon HD - Win8 Attached is a zip with the following debugging files: dmesg-boot : xl dmesg right after boot dmesg-win : xl dmesg after windows 8 fails grub : My grub configuration file win8.cfg : My Windows 8 configuration file xen-info : The result of xl info If I''ve left out anything, don''t hesitate to ask. Thanks for your time, -John _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 10/26/2013 09:58 PM, John Wargo wrote:> Geniuses, > > I''ve been trying to get VGA pass-through working on Windows 8, however > I''ve been running into a few issues. > Currently I can get Windows 8 running flawlessly without VGA > pass-through, however I''m planning on using it for gaming, so this wont > work. > > When I start windows 8, I am able to get past the install portion of the > DVD, however it hangs on "Getting devices ready.. (n%)". > > Hardware Information : > AMD Fx6300 > ASUS M5a99x evo r2.0 > 16GB RAM > 6670 Radeon HD - Dom0 > 7850 Radeon HD - Win8I have recently (recently as in over the past 48 hours) re-tried to get ATI VGA passthrough working, and the results are... interesting. HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough ever seems to work (slowdown + white lines when dragging windows after a domU reboot). I am using XP64 domU so I can''t eject the GPU (it says it is being used). But shutting down the domU, doing echo 1 > reset for the GPU from dom0 (I don''t know how this is implemented and whether it does anything) and then starting it up again sometimes recovers it. GPU-Z runs and reports the GPU correctly. HD4850 dom0 + HD7970 domU results in the entire host locking up as soon as the driver is loaded in domU. My solution is to swap the dom0 GPU for an 8800GT, and the problem now doesn''t occur. If I had to guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on the bus, tries to do something to it, and ends up crashing the host. This could also be exacerbated by the fact that I have to run with relaxed checking and no PCI ACS due to NF200 bridges on my motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU _hard_ (but not the host, thankfully). It crashes it so hard, that the only cure is to reboot the host. Reseting the GPU via /sys/ doesn''t seem to do anything to help. Are you using gfx_passthru=1 in your config? The way most people have this kind of thing working is with gfx_passthru=0, i.e. secondary passthru. Don''t assign the PCI device in the config when installing. Once the domU install is complete, shut it down, and add the GPU you want to pass through. Then fire up domU in VNC, install the driver, and with a bit of luck it will come up with output on the external monitor. Also make sure that radeon or radeonfb kernel drivers DO NOT load before the device is assigned to xen-pciback. The exact way to ensure this will depend on what distro and dom0 kernel you are using. Gordan
On 10/27/2013 04:30 AM, Gordan Bobic wrote:> On 10/26/2013 09:58 PM, John Wargo wrote: >> Geniuses, >> >> I''ve been trying to get VGA pass-through working on Windows 8, however >> I''ve been running into a few issues. >> Currently I can get Windows 8 running flawlessly without VGA >> pass-through, however I''m planning on using it for gaming, so this wont >> work. >> >> When I start windows 8, I am able to get past the install portion of the >> DVD, however it hangs on "Getting devices ready.. (n%)". >> >> Hardware Information : >> AMD Fx6300 >> ASUS M5a99x evo r2.0 >> 16GB RAM >> 6670 Radeon HD - Dom0 >> 7850 Radeon HD - Win8 > > I have recently (recently as in over the past 48 hours) re-tried to > get ATI VGA passthrough working, and the results are... interesting. > > HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough > ever seems to work (slowdown + white lines when dragging windows after > a domU reboot). I am using XP64 domU so I can''t eject the GPU (it says > it is being used). But shutting down the domU, doing echo 1 > reset > for the GPU from dom0 (I don''t know how this is implemented and > whether it does anything) and then starting it up again sometimes > recovers it. GPU-Z runs and reports the GPU correctly. > > HD4850 dom0 + HD7970 domU results in the entire host locking up as > soon as the driver is loaded in domU. My solution is to swap the dom0 > GPU for an 8800GT, and the problem now doesn''t occur. If I had to > guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on > the bus, tries to do something to it, and ends up crashing the host. > This could also be exacerbated by the fact that I have to run with > relaxed checking and no PCI ACS due to NF200 bridges on my > motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU > _hard_ (but not the host, thankfully). It crashes it so hard, that the > only cure is to reboot the host. Reseting the GPU via /sys/ doesn''t > seem to do anything to help. > > Are you using gfx_passthru=1 in your config? The way most people have > this kind of thing working is with gfx_passthru=0, i.e. secondary > passthru. Don''t assign the PCI device in the config when installing. > Once the domU install is complete, shut it down, and add the GPU you > want to pass through. Then fire up domU in VNC, install the driver, > and with a bit of luck it will come up with output on the external > monitor. > > Also make sure that radeon or radeonfb kernel drivers DO NOT load > before the device is assigned to xen-pciback. The exact way to ensure > this will depend on what distro and dom0 kernel you are using. > > GordanStatus update: The catalyst drivers appear to be working perfectly fine, device manager shows no errors, and everything works great, except that when I plug my monitor into the second card, I get "No Signal" on the monitor, then it shuts off. I though that secondary passthrough meant that it would pass the virtual adapter in as primary, but I could use my GPU that I passed through, so where am I wrong, and how do I do that? -John
On 10/27/2013 09:27 AM, John Wargo wrote:> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >> On 10/26/2013 09:58 PM, John Wargo wrote: >>> Geniuses, >>> >>> I''ve been trying to get VGA pass-through working on Windows 8, however >>> I''ve been running into a few issues. >>> Currently I can get Windows 8 running flawlessly without VGA >>> pass-through, however I''m planning on using it for gaming, so this wont >>> work. >>> >>> When I start windows 8, I am able to get past the install portion of >>> the >>> DVD, however it hangs on "Getting devices ready.. (n%)". >>> >>> Hardware Information : >>> AMD Fx6300 >>> ASUS M5a99x evo r2.0 >>> 16GB RAM >>> 6670 Radeon HD - Dom0 >>> 7850 Radeon HD - Win8 >> >> I have recently (recently as in over the past 48 hours) re-tried to >> get ATI VGA passthrough working, and the results are... interesting. >> >> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >> ever seems to work (slowdown + white lines when dragging windows >> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >> (it says it is being used). But shutting down the domU, doing echo 1 >> > reset for the GPU from dom0 (I don''t know how this is implemented >> and whether it does anything) and then starting it up again sometimes >> recovers it. GPU-Z runs and reports the GPU correctly. >> >> HD4850 dom0 + HD7970 domU results in the entire host locking up as >> soon as the driver is loaded in domU. My solution is to swap the dom0 >> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >> the bus, tries to do something to it, and ends up crashing the host. >> This could also be exacerbated by the fact that I have to run with >> relaxed checking and no PCI ACS due to NF200 bridges on my >> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >> _hard_ (but not the host, thankfully). It crashes it so hard, that >> the only cure is to reboot the host. Reseting the GPU via /sys/ >> doesn''t seem to do anything to help. >> >> Are you using gfx_passthru=1 in your config? The way most people have >> this kind of thing working is with gfx_passthru=0, i.e. secondary >> passthru. Don''t assign the PCI device in the config when installing. >> Once the domU install is complete, shut it down, and add the GPU you >> want to pass through. Then fire up domU in VNC, install the driver, >> and with a bit of luck it will come up with output on the external >> monitor. >> >> Also make sure that radeon or radeonfb kernel drivers DO NOT load >> before the device is assigned to xen-pciback. The exact way to ensure >> this will depend on what distro and dom0 kernel you are using. >> >> Gordan > Status update: > > The catalyst drivers appear to be working perfectly fine, device > manager shows no errors, and everything works great, except that when > I plug my monitor into the second card, I get "No Signal" on the > monitor, then it shuts off. > > I though that secondary passthrough meant that it would pass the > virtual adapter in as primary, but I could use my GPU that I passed > through, so where am I wrong, and how do I do that? > > -JohnI''ve been doing some research into my VGA passthrough, so I''ve gone through the various debugging steps, and the only thing that I''ve found out of place is with "xl dmesg" (attached). Where do I go from here? -John _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
I''ve made quite a bit of changes since my last email, and so far here''s what I''ve got: AMD FX6300 ASUS M5A99X evo r2.0 ASUS Radeon 6670 (Dom0) XFX Radeon 7850 (Win8) Right now I''ve got AMD Catalyst (latest stable) installed in windows 8, and device manager shows my Radeon 7850 reporting no issues. I''m currently passing it through as secondary (gfx_passthrough=0), however I cannot plug my monitor into it. After taking debugging steps, I''ve come up with the attached debugging info: info - xl info dmesg - xl dmesg grub - a copy of ''/etc/default/grub'' win8.cfg - the configuration I''m using to launch windows 8 Fedora bug reporting tool caught a kernel bug at ''drivers/gpu/drm/ttm/ttm_bo.c:210'', I have compiled xen from source, and I''m using it as a kernel (or really part of it). Is there some sort of AMD Radeon patch I need to use (I saw one on the wiki, but it appeared to be several years old), or is it a needed configuration? Thanks for your time, -John _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 10/27/2013 02:14 PM, John Wargo wrote:> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >> On 10/26/2013 09:58 PM, John Wargo wrote: >>> Geniuses, >>> >>> I''ve been trying to get VGA pass-through working on Windows 8, however >>> I''ve been running into a few issues. >>> Currently I can get Windows 8 running flawlessly without VGA >>> pass-through, however I''m planning on using it for gaming, so this wont >>> work. >>> >>> When I start windows 8, I am able to get past the install portion of the >>> DVD, however it hangs on "Getting devices ready.. (n%)". >>> >>> Hardware Information : >>> AMD Fx6300 >>> ASUS M5a99x evo r2.0 >>> 16GB RAM >>> 6670 Radeon HD - Dom0 >>> 7850 Radeon HD - Win8 >> >> I have recently (recently as in over the past 48 hours) re-tried to >> get ATI VGA passthrough working, and the results are... interesting. >> >> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >> ever seems to work (slowdown + white lines when dragging windows after >> a domU reboot). I am using XP64 domU so I can''t eject the GPU (it says >> it is being used). But shutting down the domU, doing echo 1 > reset >> for the GPU from dom0 (I don''t know how this is implemented and >> whether it does anything) and then starting it up again sometimes >> recovers it. GPU-Z runs and reports the GPU correctly. >> >> HD4850 dom0 + HD7970 domU results in the entire host locking up as >> soon as the driver is loaded in domU. My solution is to swap the dom0 >> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >> the bus, tries to do something to it, and ends up crashing the host. >> This could also be exacerbated by the fact that I have to run with >> relaxed checking and no PCI ACS due to NF200 bridges on my >> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >> _hard_ (but not the host, thankfully). It crashes it so hard, that the >> only cure is to reboot the host. Reseting the GPU via /sys/ doesn''t >> seem to do anything to help. >> >> Are you using gfx_passthru=1 in your config? The way most people have >> this kind of thing working is with gfx_passthru=0, i.e. secondary >> passthru. Don''t assign the PCI device in the config when installing. >> Once the domU install is complete, shut it down, and add the GPU you >> want to pass through. Then fire up domU in VNC, install the driver, >> and with a bit of luck it will come up with output on the external >> monitor. >> >> Also make sure that radeon or radeonfb kernel drivers DO NOT load >> before the device is assigned to xen-pciback. The exact way to ensure >> this will depend on what distro and dom0 kernel you are using. >> >> Gordan > > After messing with a few of the options, and a bit of trickery, It > appears that I''ve got it passed-through, however when viewing it in the > device manager I get Error Code 43 : Not enough system resources. I''m > currently working on installing the latest stable drivers from AMD on > hopes that it will fix it, however I don''t see it making a ton of > difference. > > Is there some sort of patch I need to apply, or something I''m missing?Are you using traditional or upstream qemu? Gordan
On 10/27/2013 02:27 PM, John Wargo wrote:> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >> On 10/26/2013 09:58 PM, John Wargo wrote: >>> Geniuses, >>> >>> I''ve been trying to get VGA pass-through working on Windows 8, however >>> I''ve been running into a few issues. >>> Currently I can get Windows 8 running flawlessly without VGA >>> pass-through, however I''m planning on using it for gaming, so this wont >>> work. >>> >>> When I start windows 8, I am able to get past the install portion of the >>> DVD, however it hangs on "Getting devices ready.. (n%)". >>> >>> Hardware Information : >>> AMD Fx6300 >>> ASUS M5a99x evo r2.0 >>> 16GB RAM >>> 6670 Radeon HD - Dom0 >>> 7850 Radeon HD - Win8 >> >> I have recently (recently as in over the past 48 hours) re-tried to >> get ATI VGA passthrough working, and the results are... interesting. >> >> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >> ever seems to work (slowdown + white lines when dragging windows after >> a domU reboot). I am using XP64 domU so I can''t eject the GPU (it says >> it is being used). But shutting down the domU, doing echo 1 > reset >> for the GPU from dom0 (I don''t know how this is implemented and >> whether it does anything) and then starting it up again sometimes >> recovers it. GPU-Z runs and reports the GPU correctly. >> >> HD4850 dom0 + HD7970 domU results in the entire host locking up as >> soon as the driver is loaded in domU. My solution is to swap the dom0 >> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >> the bus, tries to do something to it, and ends up crashing the host. >> This could also be exacerbated by the fact that I have to run with >> relaxed checking and no PCI ACS due to NF200 bridges on my >> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >> _hard_ (but not the host, thankfully). It crashes it so hard, that the >> only cure is to reboot the host. Reseting the GPU via /sys/ doesn''t >> seem to do anything to help. >> >> Are you using gfx_passthru=1 in your config? The way most people have >> this kind of thing working is with gfx_passthru=0, i.e. secondary >> passthru. Don''t assign the PCI device in the config when installing. >> Once the domU install is complete, shut it down, and add the GPU you >> want to pass through. Then fire up domU in VNC, install the driver, >> and with a bit of luck it will come up with output on the external >> monitor. >> >> Also make sure that radeon or radeonfb kernel drivers DO NOT load >> before the device is assigned to xen-pciback. The exact way to ensure >> this will depend on what distro and dom0 kernel you are using. >> >> Gordan > Status update: > > The catalyst drivers appear to be working perfectly fine, device manager > shows no errors, and everything works great, except that when I plug my > monitor into the second card, I get "No Signal" on the monitor, then it > shuts off. > > I though that secondary passthrough meant that it would pass the virtual > adapter in as primary, but I could use my GPU that I passed through, so > where am I wrong, and how do I do that?Your understanding is correct - real VGA card will be passed as secondary, and the driver, when it loads, should start it up, and this normally takes over from the primary. Two things come to mind: 1) I find that sometimes I have to disable the primary emulated VGA adapter. 2) Make sure your desktop settings are correctly set up to use the real VGA card as the primary desktop. Gordan
On 10/27/2013 04:21 PM, John Wargo wrote:> On 10/27/2013 09:27 AM, John Wargo wrote: >> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >>> On 10/26/2013 09:58 PM, John Wargo wrote: >>>> Geniuses, >>>> >>>> I''ve been trying to get VGA pass-through working on Windows 8, however >>>> I''ve been running into a few issues. >>>> Currently I can get Windows 8 running flawlessly without VGA >>>> pass-through, however I''m planning on using it for gaming, so this wont >>>> work. >>>> >>>> When I start windows 8, I am able to get past the install portion of >>>> the >>>> DVD, however it hangs on "Getting devices ready.. (n%)". >>>> >>>> Hardware Information : >>>> AMD Fx6300 >>>> ASUS M5a99x evo r2.0 >>>> 16GB RAM >>>> 6670 Radeon HD - Dom0 >>>> 7850 Radeon HD - Win8 >>> >>> I have recently (recently as in over the past 48 hours) re-tried to >>> get ATI VGA passthrough working, and the results are... interesting. >>> >>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >>> ever seems to work (slowdown + white lines when dragging windows >>> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >>> (it says it is being used). But shutting down the domU, doing echo 1 >>> > reset for the GPU from dom0 (I don''t know how this is implemented >>> and whether it does anything) and then starting it up again sometimes >>> recovers it. GPU-Z runs and reports the GPU correctly. >>> >>> HD4850 dom0 + HD7970 domU results in the entire host locking up as >>> soon as the driver is loaded in domU. My solution is to swap the dom0 >>> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >>> the bus, tries to do something to it, and ends up crashing the host. >>> This could also be exacerbated by the fact that I have to run with >>> relaxed checking and no PCI ACS due to NF200 bridges on my >>> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >>> _hard_ (but not the host, thankfully). It crashes it so hard, that >>> the only cure is to reboot the host. Reseting the GPU via /sys/ >>> doesn''t seem to do anything to help. >>> >>> Are you using gfx_passthru=1 in your config? The way most people have >>> this kind of thing working is with gfx_passthru=0, i.e. secondary >>> passthru. Don''t assign the PCI device in the config when installing. >>> Once the domU install is complete, shut it down, and add the GPU you >>> want to pass through. Then fire up domU in VNC, install the driver, >>> and with a bit of luck it will come up with output on the external >>> monitor. >>> >>> Also make sure that radeon or radeonfb kernel drivers DO NOT load >>> before the device is assigned to xen-pciback. The exact way to ensure >>> this will depend on what distro and dom0 kernel you are using. >>> >>> Gordan >> Status update: >> >> The catalyst drivers appear to be working perfectly fine, device >> manager shows no errors, and everything works great, except that when >> I plug my monitor into the second card, I get "No Signal" on the >> monitor, then it shuts off. >> >> I though that secondary passthrough meant that it would pass the >> virtual adapter in as primary, but I could use my GPU that I passed >> through, so where am I wrong, and how do I do that? >> >> -John > I''ve been doing some research into my VGA passthrough, so I''ve gone > through the various debugging steps, and the only thing that I''ve found > out of place is with "xl dmesg" (attached). > > Where do I go from here?Sounds like your IOMMU may be buggy. You may need to set permissive=1 on your xen-pciback module. I cannot remember if xl uses the same configuration, but for xm you could try putting this in your /etc/xen/xend-config.sxp: (pci-passthrough-strict-check no) (pci-dev-assign-strict-check no) Gordan
On 10/27/2013 02:35 PM, Gordan Bobic wrote:> On 10/27/2013 04:21 PM, John Wargo wrote: >> On 10/27/2013 09:27 AM, John Wargo wrote: >>> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >>>> On 10/26/2013 09:58 PM, John Wargo wrote: >>>>> Geniuses, >>>>> >>>>> I''ve been trying to get VGA pass-through working on Windows 8, >>>>> however >>>>> I''ve been running into a few issues. >>>>> Currently I can get Windows 8 running flawlessly without VGA >>>>> pass-through, however I''m planning on using it for gaming, so this >>>>> wont >>>>> work. >>>>> >>>>> When I start windows 8, I am able to get past the install portion of >>>>> the >>>>> DVD, however it hangs on "Getting devices ready.. (n%)". >>>>> >>>>> Hardware Information : >>>>> AMD Fx6300 >>>>> ASUS M5a99x evo r2.0 >>>>> 16GB RAM >>>>> 6670 Radeon HD - Dom0 >>>>> 7850 Radeon HD - Win8 >>>> >>>> I have recently (recently as in over the past 48 hours) re-tried to >>>> get ATI VGA passthrough working, and the results are... interesting. >>>> >>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >>>> ever seems to work (slowdown + white lines when dragging windows >>>> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >>>> (it says it is being used). But shutting down the domU, doing echo 1 >>>> > reset for the GPU from dom0 (I don''t know how this is implemented >>>> and whether it does anything) and then starting it up again sometimes >>>> recovers it. GPU-Z runs and reports the GPU correctly. >>>> >>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as >>>> soon as the driver is loaded in domU. My solution is to swap the dom0 >>>> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >>>> the bus, tries to do something to it, and ends up crashing the host. >>>> This could also be exacerbated by the fact that I have to run with >>>> relaxed checking and no PCI ACS due to NF200 bridges on my >>>> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >>>> _hard_ (but not the host, thankfully). It crashes it so hard, that >>>> the only cure is to reboot the host. Reseting the GPU via /sys/ >>>> doesn''t seem to do anything to help. >>>> >>>> Are you using gfx_passthru=1 in your config? The way most people have >>>> this kind of thing working is with gfx_passthru=0, i.e. secondary >>>> passthru. Don''t assign the PCI device in the config when installing. >>>> Once the domU install is complete, shut it down, and add the GPU you >>>> want to pass through. Then fire up domU in VNC, install the driver, >>>> and with a bit of luck it will come up with output on the external >>>> monitor. >>>> >>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load >>>> before the device is assigned to xen-pciback. The exact way to ensure >>>> this will depend on what distro and dom0 kernel you are using. >>>> >>>> Gordan >>> Status update: >>> >>> The catalyst drivers appear to be working perfectly fine, device >>> manager shows no errors, and everything works great, except that when >>> I plug my monitor into the second card, I get "No Signal" on the >>> monitor, then it shuts off. >>> >>> I though that secondary passthrough meant that it would pass the >>> virtual adapter in as primary, but I could use my GPU that I passed >>> through, so where am I wrong, and how do I do that? >>> >>> -John >> I''ve been doing some research into my VGA passthrough, so I''ve gone >> through the various debugging steps, and the only thing that I''ve found >> out of place is with "xl dmesg" (attached). >> >> Where do I go from here? > > Sounds like your IOMMU may be buggy. You may need to set permissive=1 > on your xen-pciback module. > > I cannot remember if xl uses the same configuration, but for xm you > could try putting this in your /etc/xen/xend-config.sxp: > (pci-passthrough-strict-check no) > (pci-dev-assign-strict-check no) > > Gordan >Gordan, I have fough IOMMU in the past, so this sounds very likely, I''ll try it. For future reference, I''m fairly certain that in xl you specify permissive in the cfg file: pci = [x:x.x, permissive=1...] -John
On 10/27/2013 02:35 PM, Gordan Bobic wrote:> On 10/27/2013 04:21 PM, John Wargo wrote: >> On 10/27/2013 09:27 AM, John Wargo wrote: >>> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >>>> On 10/26/2013 09:58 PM, John Wargo wrote: >>>>> Geniuses, >>>>> >>>>> I''ve been trying to get VGA pass-through working on Windows 8, >>>>> however >>>>> I''ve been running into a few issues. >>>>> Currently I can get Windows 8 running flawlessly without VGA >>>>> pass-through, however I''m planning on using it for gaming, so this >>>>> wont >>>>> work. >>>>> >>>>> When I start windows 8, I am able to get past the install portion of >>>>> the >>>>> DVD, however it hangs on "Getting devices ready.. (n%)". >>>>> >>>>> Hardware Information : >>>>> AMD Fx6300 >>>>> ASUS M5a99x evo r2.0 >>>>> 16GB RAM >>>>> 6670 Radeon HD - Dom0 >>>>> 7850 Radeon HD - Win8 >>>> >>>> I have recently (recently as in over the past 48 hours) re-tried to >>>> get ATI VGA passthrough working, and the results are... interesting. >>>> >>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >>>> ever seems to work (slowdown + white lines when dragging windows >>>> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >>>> (it says it is being used). But shutting down the domU, doing echo 1 >>>> > reset for the GPU from dom0 (I don''t know how this is implemented >>>> and whether it does anything) and then starting it up again sometimes >>>> recovers it. GPU-Z runs and reports the GPU correctly. >>>> >>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as >>>> soon as the driver is loaded in domU. My solution is to swap the dom0 >>>> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >>>> the bus, tries to do something to it, and ends up crashing the host. >>>> This could also be exacerbated by the fact that I have to run with >>>> relaxed checking and no PCI ACS due to NF200 bridges on my >>>> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >>>> _hard_ (but not the host, thankfully). It crashes it so hard, that >>>> the only cure is to reboot the host. Reseting the GPU via /sys/ >>>> doesn''t seem to do anything to help. >>>> >>>> Are you using gfx_passthru=1 in your config? The way most people have >>>> this kind of thing working is with gfx_passthru=0, i.e. secondary >>>> passthru. Don''t assign the PCI device in the config when installing. >>>> Once the domU install is complete, shut it down, and add the GPU you >>>> want to pass through. Then fire up domU in VNC, install the driver, >>>> and with a bit of luck it will come up with output on the external >>>> monitor. >>>> >>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load >>>> before the device is assigned to xen-pciback. The exact way to ensure >>>> this will depend on what distro and dom0 kernel you are using. >>>> >>>> Gordan >>> Status update: >>> >>> The catalyst drivers appear to be working perfectly fine, device >>> manager shows no errors, and everything works great, except that when >>> I plug my monitor into the second card, I get "No Signal" on the >>> monitor, then it shuts off. >>> >>> I though that secondary passthrough meant that it would pass the >>> virtual adapter in as primary, but I could use my GPU that I passed >>> through, so where am I wrong, and how do I do that? >>> >>> -John >> I''ve been doing some research into my VGA passthrough, so I''ve gone >> through the various debugging steps, and the only thing that I''ve found >> out of place is with "xl dmesg" (attached). >> >> Where do I go from here? > > Sounds like your IOMMU may be buggy. You may need to set permissive=1 > on your xen-pciback module. > > I cannot remember if xl uses the same configuration, but for xm you > could try putting this in your /etc/xen/xend-config.sxp: > (pci-passthrough-strict-check no) > (pci-dev-assign-strict-check no) > > Gordan >Gordan, According to the xenbits page on xl.cfg, it appears the permissive will only work with PV guests, not HVM.. -John
On 10/27/2013 02:35 PM, Gordan Bobic wrote:> On 10/27/2013 04:21 PM, John Wargo wrote: >> On 10/27/2013 09:27 AM, John Wargo wrote: >>> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >>>> On 10/26/2013 09:58 PM, John Wargo wrote: >>>>> Geniuses, >>>>> >>>>> I''ve been trying to get VGA pass-through working on Windows 8, >>>>> however >>>>> I''ve been running into a few issues. >>>>> Currently I can get Windows 8 running flawlessly without VGA >>>>> pass-through, however I''m planning on using it for gaming, so this >>>>> wont >>>>> work. >>>>> >>>>> When I start windows 8, I am able to get past the install portion of >>>>> the >>>>> DVD, however it hangs on "Getting devices ready.. (n%)". >>>>> >>>>> Hardware Information : >>>>> AMD Fx6300 >>>>> ASUS M5a99x evo r2.0 >>>>> 16GB RAM >>>>> 6670 Radeon HD - Dom0 >>>>> 7850 Radeon HD - Win8 >>>> >>>> I have recently (recently as in over the past 48 hours) re-tried to >>>> get ATI VGA passthrough working, and the results are... interesting. >>>> >>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >>>> ever seems to work (slowdown + white lines when dragging windows >>>> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >>>> (it says it is being used). But shutting down the domU, doing echo 1 >>>> > reset for the GPU from dom0 (I don''t know how this is implemented >>>> and whether it does anything) and then starting it up again sometimes >>>> recovers it. GPU-Z runs and reports the GPU correctly. >>>> >>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as >>>> soon as the driver is loaded in domU. My solution is to swap the dom0 >>>> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >>>> the bus, tries to do something to it, and ends up crashing the host. >>>> This could also be exacerbated by the fact that I have to run with >>>> relaxed checking and no PCI ACS due to NF200 bridges on my >>>> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >>>> _hard_ (but not the host, thankfully). It crashes it so hard, that >>>> the only cure is to reboot the host. Reseting the GPU via /sys/ >>>> doesn''t seem to do anything to help. >>>> >>>> Are you using gfx_passthru=1 in your config? The way most people have >>>> this kind of thing working is with gfx_passthru=0, i.e. secondary >>>> passthru. Don''t assign the PCI device in the config when installing. >>>> Once the domU install is complete, shut it down, and add the GPU you >>>> want to pass through. Then fire up domU in VNC, install the driver, >>>> and with a bit of luck it will come up with output on the external >>>> monitor. >>>> >>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load >>>> before the device is assigned to xen-pciback. The exact way to ensure >>>> this will depend on what distro and dom0 kernel you are using. >>>> >>>> Gordan >>> Status update: >>> >>> The catalyst drivers appear to be working perfectly fine, device >>> manager shows no errors, and everything works great, except that when >>> I plug my monitor into the second card, I get "No Signal" on the >>> monitor, then it shuts off. >>> >>> I though that secondary passthrough meant that it would pass the >>> virtual adapter in as primary, but I could use my GPU that I passed >>> through, so where am I wrong, and how do I do that? >>> >>> -John >> I''ve been doing some research into my VGA passthrough, so I''ve gone >> through the various debugging steps, and the only thing that I''ve found >> out of place is with "xl dmesg" (attached). >> >> Where do I go from here? > > Sounds like your IOMMU may be buggy. You may need to set permissive=1 > on your xen-pciback module. > > I cannot remember if xl uses the same configuration, but for xm you > could try putting this in your /etc/xen/xend-config.sxp: > (pci-passthrough-strict-check no) > (pci-dev-assign-strict-check no) > > Gordan >Gordan, After a bit of research, I was able to activate permissive mode on xen, but I''ve got nothing, I''m still getting page faults. The page faults occur when the loading screen goes black (I''d assume when it''s trying to pass to the GPU) I''ve also tried setting (pci_msitranslate=0, along with changing qemu=qemu-xen, but it doesn''t help -John
On 10/27/2013 09:01 PM, John Wargo wrote:> On 10/27/2013 02:35 PM, Gordan Bobic wrote: >> On 10/27/2013 04:21 PM, John Wargo wrote: >>> On 10/27/2013 09:27 AM, John Wargo wrote: >>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >>>>> On 10/26/2013 09:58 PM, John Wargo wrote: >>>>>> Geniuses, >>>>>> >>>>>> I''ve been trying to get VGA pass-through working on Windows 8, >>>>>> however >>>>>> I''ve been running into a few issues. >>>>>> Currently I can get Windows 8 running flawlessly without VGA >>>>>> pass-through, however I''m planning on using it for gaming, so this >>>>>> wont >>>>>> work. >>>>>> >>>>>> When I start windows 8, I am able to get past the install portion of >>>>>> the >>>>>> DVD, however it hangs on "Getting devices ready.. (n%)". >>>>>> >>>>>> Hardware Information : >>>>>> AMD Fx6300 >>>>>> ASUS M5a99x evo r2.0 >>>>>> 16GB RAM >>>>>> 6670 Radeon HD - Dom0 >>>>>> 7850 Radeon HD - Win8 >>>>> >>>>> I have recently (recently as in over the past 48 hours) re-tried to >>>>> get ATI VGA passthrough working, and the results are... interesting. >>>>> >>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI passthrough >>>>> ever seems to work (slowdown + white lines when dragging windows >>>>> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >>>>> (it says it is being used). But shutting down the domU, doing echo 1 >>>>> > reset for the GPU from dom0 (I don''t know how this is implemented >>>>> and whether it does anything) and then starting it up again sometimes >>>>> recovers it. GPU-Z runs and reports the GPU correctly. >>>>> >>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as >>>>> soon as the driver is loaded in domU. My solution is to swap the dom0 >>>>> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >>>>> guess, BIOS on the HD7970 does something bizzare, finds the HD4850 on >>>>> the bus, tries to do something to it, and ends up crashing the host. >>>>> This could also be exacerbated by the fact that I have to run with >>>>> relaxed checking and no PCI ACS due to NF200 bridges on my >>>>> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that >>>>> the only cure is to reboot the host. Reseting the GPU via /sys/ >>>>> doesn''t seem to do anything to help. >>>>> >>>>> Are you using gfx_passthru=1 in your config? The way most people have >>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary >>>>> passthru. Don''t assign the PCI device in the config when installing. >>>>> Once the domU install is complete, shut it down, and add the GPU you >>>>> want to pass through. Then fire up domU in VNC, install the driver, >>>>> and with a bit of luck it will come up with output on the external >>>>> monitor. >>>>> >>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load >>>>> before the device is assigned to xen-pciback. The exact way to ensure >>>>> this will depend on what distro and dom0 kernel you are using. >>>>> >>>>> Gordan >>>> Status update: >>>> >>>> The catalyst drivers appear to be working perfectly fine, device >>>> manager shows no errors, and everything works great, except that when >>>> I plug my monitor into the second card, I get "No Signal" on the >>>> monitor, then it shuts off. >>>> >>>> I though that secondary passthrough meant that it would pass the >>>> virtual adapter in as primary, but I could use my GPU that I passed >>>> through, so where am I wrong, and how do I do that? >>>> >>>> -John >>> I''ve been doing some research into my VGA passthrough, so I''ve gone >>> through the various debugging steps, and the only thing that I''ve found >>> out of place is with "xl dmesg" (attached). >>> >>> Where do I go from here? >> >> Sounds like your IOMMU may be buggy. You may need to set permissive=1 >> on your xen-pciback module. >> >> I cannot remember if xl uses the same configuration, but for xm you >> could try putting this in your /etc/xen/xend-config.sxp: >> (pci-passthrough-strict-check no) >> (pci-dev-assign-strict-check no) >> >> Gordan >> > Gordan, > > After a bit of research, I was able to activate permissive mode on xen, > but I''ve got nothing, I''m still getting page faults. > > The page faults occur when the loading screen goes black (I''d assume > when it''s trying to pass to the GPU) > > I''ve also tried setting (pci_msitranslate=0, along with changing > qemu=qemu-xen, but it doesn''t helpThe correct incantation you seek is to put this in the config: device_model_version="qemu-xen-traditional" Gordan
On 10/27/2013 05:51 PM, Gordan Bobic wrote:> On 10/27/2013 09:01 PM, John Wargo wrote: >> On 10/27/2013 02:35 PM, Gordan Bobic wrote: >>> On 10/27/2013 04:21 PM, John Wargo wrote: >>>> On 10/27/2013 09:27 AM, John Wargo wrote: >>>>> On 10/27/2013 04:30 AM, Gordan Bobic wrote: >>>>>> On 10/26/2013 09:58 PM, John Wargo wrote: >>>>>>> Geniuses, >>>>>>> >>>>>>> I''ve been trying to get VGA pass-through working on Windows 8, >>>>>>> however >>>>>>> I''ve been running into a few issues. >>>>>>> Currently I can get Windows 8 running flawlessly without VGA >>>>>>> pass-through, however I''m planning on using it for gaming, so this >>>>>>> wont >>>>>>> work. >>>>>>> >>>>>>> When I start windows 8, I am able to get past the install >>>>>>> portion of >>>>>>> the >>>>>>> DVD, however it hangs on "Getting devices ready.. (n%)". >>>>>>> >>>>>>> Hardware Information : >>>>>>> AMD Fx6300 >>>>>>> ASUS M5a99x evo r2.0 >>>>>>> 16GB RAM >>>>>>> 6670 Radeon HD - Dom0 >>>>>>> 7850 Radeon HD - Win8 >>>>>> >>>>>> I have recently (recently as in over the past 48 hours) re-tried to >>>>>> get ATI VGA passthrough working, and the results are... interesting. >>>>>> >>>>>> HD4850 dom0 + HD7450 domU worked fine - or as fine as ATI >>>>>> passthrough >>>>>> ever seems to work (slowdown + white lines when dragging windows >>>>>> after a domU reboot). I am using XP64 domU so I can''t eject the GPU >>>>>> (it says it is being used). But shutting down the domU, doing echo 1 >>>>>> > reset for the GPU from dom0 (I don''t know how this is implemented >>>>>> and whether it does anything) and then starting it up again >>>>>> sometimes >>>>>> recovers it. GPU-Z runs and reports the GPU correctly. >>>>>> >>>>>> HD4850 dom0 + HD7970 domU results in the entire host locking up as >>>>>> soon as the driver is loaded in domU. My solution is to swap the >>>>>> dom0 >>>>>> GPU for an 8800GT, and the problem now doesn''t occur. If I had to >>>>>> guess, BIOS on the HD7970 does something bizzare, finds the >>>>>> HD4850 on >>>>>> the bus, tries to do something to it, and ends up crashing the host. >>>>>> This could also be exacerbated by the fact that I have to run with >>>>>> relaxed checking and no PCI ACS due to NF200 bridges on my >>>>>> motherboard. Even so, however, GPU-Z crashes the domU and it''s GPU >>>>>> _hard_ (but not the host, thankfully). It crashes it so hard, that >>>>>> the only cure is to reboot the host. Reseting the GPU via /sys/ >>>>>> doesn''t seem to do anything to help. >>>>>> >>>>>> Are you using gfx_passthru=1 in your config? The way most people >>>>>> have >>>>>> this kind of thing working is with gfx_passthru=0, i.e. secondary >>>>>> passthru. Don''t assign the PCI device in the config when installing. >>>>>> Once the domU install is complete, shut it down, and add the GPU you >>>>>> want to pass through. Then fire up domU in VNC, install the driver, >>>>>> and with a bit of luck it will come up with output on the external >>>>>> monitor. >>>>>> >>>>>> Also make sure that radeon or radeonfb kernel drivers DO NOT load >>>>>> before the device is assigned to xen-pciback. The exact way to >>>>>> ensure >>>>>> this will depend on what distro and dom0 kernel you are using. >>>>>> >>>>>> Gordan >>>>> Status update: >>>>> >>>>> The catalyst drivers appear to be working perfectly fine, device >>>>> manager shows no errors, and everything works great, except that when >>>>> I plug my monitor into the second card, I get "No Signal" on the >>>>> monitor, then it shuts off. >>>>> >>>>> I though that secondary passthrough meant that it would pass the >>>>> virtual adapter in as primary, but I could use my GPU that I passed >>>>> through, so where am I wrong, and how do I do that? >>>>> >>>>> -John >>>> I''ve been doing some research into my VGA passthrough, so I''ve gone >>>> through the various debugging steps, and the only thing that I''ve >>>> found >>>> out of place is with "xl dmesg" (attached). >>>> >>>> Where do I go from here? >>> >>> Sounds like your IOMMU may be buggy. You may need to set permissive=1 >>> on your xen-pciback module. >>> >>> I cannot remember if xl uses the same configuration, but for xm you >>> could try putting this in your /etc/xen/xend-config.sxp: >>> (pci-passthrough-strict-check no) >>> (pci-dev-assign-strict-check no) >>> >>> Gordan >>> >> Gordan, >> >> After a bit of research, I was able to activate permissive mode on xen, >> but I''ve got nothing, I''m still getting page faults. >> >> The page faults occur when the loading screen goes black (I''d assume >> when it''s trying to pass to the GPU) >> >> I''ve also tried setting (pci_msitranslate=0, along with changing >> qemu=qemu-xen, but it doesn''t help > > The correct incantation you seek is to put this in the config: > device_model_version="qemu-xen-traditional" > > GordanGordan, Sorry for the confusion, I think that''s what I meant by changing "qemu=qemu-xen", and I''ve been running off of "qemu-xen-traditional" up until I changed it. I''m giving it another shot right now just in case though. -John
On Sun, Oct 27, 2013 at 12:21:14PM -0500, John Wargo wrote:> I''ve made quite a bit of changes since my last email, and so far > here''s what I''ve got: > > AMD FX6300 > ASUS M5A99X evo r2.0 > ASUS Radeon 6670 (Dom0) > XFX Radeon 7850 (Win8) > > Right now I''ve got AMD Catalyst (latest stable) installed in windows > 8, and device manager shows my Radeon 7850 reporting no issues. > > I''m currently passing it through as secondary (gfx_passthrough=0), > however I cannot plug my monitor into it. > > After taking debugging steps, I''ve come up with the attached debugging info: > info - xl info > dmesg - xl dmesg > grub - a copy of ''/etc/default/grub'' > win8.cfg - the configuration I''m using to launch windows 8 > > Fedora bug reporting tool caught a kernel bug at > ''drivers/gpu/drm/ttm/ttm_bo.c:210'', I have compiled xen from source, > and I''m using it as a kernel (or really part of it).OK, what was the rest of it? And what version of the kernel? You also seem to have a debug.zip attached - but it has nothing it it?> > Is there some sort of AMD Radeon patch I need to use (I saw one on > the wiki, but it appeared to be several years old), or is it a > needed configuration? > > Thanks for your time, > -John> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
On Sunday, October 27, 2013 1:21 PM, John Wargo wrote:>I''ve made quite a bit of changes since my last email, and so far here''s what I''ve got: > >AMD FX6300 >ASUS M5A99X evo r2.0 >ASUS Radeon 6670 (Dom0) >XFX Radeon 7850 (Win8) > >... > >Is there some sort of AMD Radeon patch I need to use (I saw one on the wiki, but it appeared to be several years old), or is it a needed configuration? > >Thanks for your time, >-JohnHi John, I am using XEN4.2 with QEMU-traditional and I have identified a couple of issues in regards to passing through a video adapter as the primary (VGA enabled) adapter. The patch that you referenced attempts to get around one of the issues but it is not complete and doesn''t cover all of the cases. If you apply the patch it will definitely help but not guaranteed to fix all of your problems. The second issue is related to the fact that you are using two different graphics adapters. I am assuming that the Radeon 6670 is the primary (boot/VGA) adapter and that the 7850 is the secondary. From reading your thread I assume that you want to pass the 7850 through to the DomU as the primary. I have been able to do this successfully with a few fixes. The problem is in the way QEMU/hvmloader handle the VBios code. When you boot with the 6670 as the primary the VBios code for the graphics adapter is copied to memory at address 0xc0000. When QEMU passes the 7850 through to the DomU it copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU memory space. DomU is effectively executing the VBios for the wrong video card. The correct fix is to have the hvmloader read a fresh copy of VBios from the 7850 and copy it into the DomU address space at 0xc0000. Sometimes you can get away with executing the wrong VBios, sometimes you get stung. Hope the explanation helps, Kelly
This sounds about right, what then is the fix though? How do i get qemu/hvm load the right vbios? On a side note, I assume that i need to install the mentioned patch, if so, whats the best way to apply it? (It seems dated, and i get errors when i try to patch with it) Sorry for asking such basic questions, -John On Monday, October 28, 2013, Zytaruk, Kelly <Kelly.Zytaruk@amd.com> wrote:> On Sunday, October 27, 2013 1:21 PM, John Wargo wrote: >>I''ve made quite a bit of changes since my last email, and so far here''swhat I''ve got:>> >>AMD FX6300 >>ASUS M5A99X evo r2.0 >>ASUS Radeon 6670 (Dom0) >>XFX Radeon 7850 (Win8) >> >>... >> >>Is there some sort of AMD Radeon patch I need to use (I saw one on thewiki, but it appeared to be several years old), or is it a needed configuration?>> >>Thanks for your time, >>-John > > Hi John, > > I am using XEN4.2 with QEMU-traditional and I have identified a couple ofissues in regards to passing through a video adapter as the primary (VGA enabled) adapter.> > The patch that you referenced attempts to get around one of the issuesbut it is not complete and doesn''t cover all of the cases. If you apply the patch it will definitely help but not guaranteed to fix all of your problems.> > The second issue is related to the fact that you are using two differentgraphics adapters. I am assuming that the Radeon 6670 is the primary (boot/VGA) adapter and that the 7850 is the secondary.> > From reading your thread I assume that you want to pass the 7850 throughto the DomU as the primary. I have been able to do this successfully with a few fixes. The problem is in the way QEMU/hvmloader handle the VBios code. When you boot with the 6670 as the primary the VBios code for the graphics adapter is copied to memory at address 0xc0000. When QEMU passes the 7850 through to the DomU it copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU memory space. DomU is effectively executing the VBios for the wrong video card. The correct fix is to have the hvmloader read a fresh copy of VBios from the 7850 and copy it into the DomU address space at 0xc0000.> > Sometimes you can get away with executing the wrong VBios, sometimes youget stung.> > Hope the explanation helps, > Kelly > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
I''d focus more on why exactly do you think you need primary passthrough. Is your requirement for seeing the SeaBIOS POST and the Windows loading animation strong enough to bother with the amount of extra pain that it is going to require? On 10/28/2013 08:31 PM, John Wargo wrote:> This sounds about right, what then is the fix though? How do i get > qemu/hvm load the right vbios? On a side note, I assume that i need to > install the mentioned patch, if so, whats the best way to apply it? (It > seems dated, and i get errors when i try to patch with it) > > Sorry for asking such basic questions, > -John > > On Monday, October 28, 2013, Zytaruk, Kelly <Kelly.Zytaruk@amd.com > <mailto:Kelly.Zytaruk@amd.com>> wrote: > > On Sunday, October 27, 2013 1:21 PM, John Wargo wrote: > >>I''ve made quite a bit of changes since my last email, and so far > here''s what I''ve got: > >> > >>AMD FX6300 > >>ASUS M5A99X evo r2.0 > >>ASUS Radeon 6670 (Dom0) > >>XFX Radeon 7850 (Win8) > >> > >>... > >> > >>Is there some sort of AMD Radeon patch I need to use (I saw one on > the wiki, but it appeared to be several years old), or is it a needed > configuration? > >> > >>Thanks for your time, > >>-John > > > > Hi John, > > > > I am using XEN4.2 with QEMU-traditional and I have identified a > couple of issues in regards to passing through a video adapter as the > primary (VGA enabled) adapter. > > > > The patch that you referenced attempts to get around one of the > issues but it is not complete and doesn''t cover all of the cases. If > you apply the patch it will definitely help but not guaranteed to fix > all of your problems. > > > > The second issue is related to the fact that you are using two > different graphics adapters. I am assuming that the Radeon 6670 is the > primary (boot/VGA) adapter and that the 7850 is the secondary. > > > > From reading your thread I assume that you want to pass the 7850 > through to the DomU as the primary. I have been able to do this > successfully with a few fixes. The problem is in the way > QEMU/hvmloader handle the VBios code. When you boot with the 6670 as > the primary the VBios code for the graphics adapter is copied to memory > at address 0xc0000. When QEMU passes the 7850 through to the DomU it > copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU > memory space. DomU is effectively executing the VBios for the wrong > video card. The correct fix is to have the hvmloader read a fresh copy > of VBios from the 7850 and copy it into the DomU address space at 0xc0000. > > > > Sometimes you can get away with executing the wrong VBios, sometimes > you get stung. > > > > Hope the explanation helps, > > Kelly > > > > > >
I dont want primary passthrough, im currently just trying for secondary.. On Monday, October 28, 2013, Gordan Bobic <gordan@bobich.net> wrote:> I''d focus more on why exactly do you think you need primary passthrough.Is your requirement for seeing the SeaBIOS POST and the Windows loading animation strong enough to bother with the amount of extra pain that it is going to require?> > On 10/28/2013 08:31 PM, John Wargo wrote: >> >> This sounds about right, what then is the fix though? How do i get >> qemu/hvm load the right vbios? On a side note, I assume that i need to >> install the mentioned patch, if so, whats the best way to apply it? (It >> seems dated, and i get errors when i try to patch with it) >> >> Sorry for asking such basic questions, >> -John >> >> On Monday, October 28, 2013, Zytaruk, Kelly <Kelly.Zytaruk@amd.com >> <mailto:Kelly.Zytaruk@amd.com>> wrote: >> > On Sunday, October 27, 2013 1:21 PM, John Wargo wrote: >> >>I''ve made quite a bit of changes since my last email, and so far >> here''s what I''ve got: >> >> >> >>AMD FX6300 >> >>ASUS M5A99X evo r2.0 >> >>ASUS Radeon 6670 (Dom0) >> >>XFX Radeon 7850 (Win8) >> >> >> >>... >> >> >> >>Is there some sort of AMD Radeon patch I need to use (I saw one on >> the wiki, but it appeared to be several years old), or is it a needed >> configuration? >> >> >> >>Thanks for your time, >> >>-John >> > >> > Hi John, >> > >> > I am using XEN4.2 with QEMU-traditional and I have identified a >> couple of issues in regards to passing through a video adapter as the >> primary (VGA enabled) adapter. >> > >> > The patch that you referenced attempts to get around one of the >> issues but it is not complete and doesn''t cover all of the cases. If >> you apply the patch it will definitely help but not guaranteed to fix >> all of your problems. >> > >> > The second issue is related to the fact that you are using two >> different graphics adapters. I am assuming that the Radeon 6670 is the >> primary (boot/VGA) adapter and that the 7850 is the secondary. >> > >> > From reading your thread I assume that you want to pass the 7850 >> through to the DomU as the primary. I have been able to do this >> successfully with a few fixes. The problem is in the way >> QEMU/hvmloader handle the VBios code. When you boot with the 6670 as >> the primary the VBios code for the graphics adapter is copied to memory >> at address 0xc0000. When QEMU passes the 7850 through to the DomU it >> copies VBios from 0xc0000 in Dom0 memory space into 0xc0000 in DomU >> memory space. DomU is effectively executing the VBios for the wrong >> video card. The correct fix is to have the hvmloader read a fresh copy >> of VBios from the 7850 and copy it into the DomU address space at0xc0000.>> > >> > Sometimes you can get away with executing the wrong VBios, sometimes >> you get stung. >> > >> > Hope the explanation helps, >> > Kelly >> > >> > >> > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Sorry for the delay, when i get home ill get both to you. On Monday, October 28, 2013, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:> On Sun, Oct 27, 2013 at 12:21:14PM -0500, John Wargo wrote: >> I''ve made quite a bit of changes since my last email, and so far >> here''s what I''ve got: >> >> AMD FX6300 >> ASUS M5A99X evo r2.0 >> ASUS Radeon 6670 (Dom0) >> XFX Radeon 7850 (Win8) >> >> Right now I''ve got AMD Catalyst (latest stable) installed in windows >> 8, and device manager shows my Radeon 7850 reporting no issues. >> >> I''m currently passing it through as secondary (gfx_passthrough=0), >> however I cannot plug my monitor into it. >> >> After taking debugging steps, I''ve come up with the attached debugginginfo:>> info - xl info >> dmesg - xl dmesg >> grub - a copy of ''/etc/default/grub'' >> win8.cfg - the configuration I''m using to launch windows 8 >> >> Fedora bug reporting tool caught a kernel bug at >> ''drivers/gpu/drm/ttm/ttm_bo.c:210'', I have compiled xen from source, >> and I''m using it as a kernel (or really part of it). > > OK, what was the rest of it? And what version of the kernel? > > You also seem to have a debug.zip attached - but it has nothing it it? >> >> Is there some sort of AMD Radeon patch I need to use (I saw one on >> the wiki, but it appeared to be several years old), or is it a >> needed configuration? >> >> Thanks for your time, >> -John > > >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Mon, 28 Oct 2013 16:29:49 -0500 John Wargo wrote;>I dont want primary passthrough, im currently just trying for secondary.. > >On Monday, October 28, 2013, Gordan Bobic <gordan@xxxxxxxxxx<mailto:gordan@xxxxxxxxxx>> wrote: >> I'd focus more on why exactly do you think you need primary passthrough. Is your requirement >>for seeing the SeaBIOS POST and the Windows loading animation strong enough to bother with >>the amount of extra pain that it is going to require?And on Sunday, October 27, 2013 10:28 AM John Wargo also wrote;> I though that secondary passthrough meant that it would pass the virtual adapter in as primary,>but I could use my GPU that I passed through, so where am I wrong, and how do I do that?John, I’m not totally clear what you are trying to accomplish. Let me start with some groundwork and you can help me from there. You have 2 adapters; Radeon HD 6670 and Radeon HD 7850 Correct me if I am wrong but it sounds like you have booted on the 6670. This make the 6670 the primary (VGA boot adapter) and the 7850 is the secondary adapter. 6670 = primary 7850 = secondary There are 4 possible adapter configurations for DomU; - Pass through primary as primary (6670 is primary in DomU) - Pass through primary as secondary (6670 is secondary in DomU, Cirrus emulated is primary) - Pass through secondary as primary (7850 is primary in DomU) - Pass through secondary as secondary (7850 is secondary in DomU, Cirrus emulated is primary) You said you wanted Dom0 = 6670 and DomU = 7850. Looking at the list above, there are two possible configurations for the 7850 in DomU; 7850 as primary or 7850 as secondary. If you set “gfx_passthru=1” in your .cfg file for DomU you will pass the 7850 through as a primary. This means that the DomU will use the 7850 as a boot VGA adapter. Your desktop will be accelerated using the 7850. If you set “gfx_passthru=0” in your .cfg file for DomU you will pass the 7850 through as a secondary. This means that the DomU will use the Cirrus emulated VGA VBios as the boot device. Your desktop will use the emulated adapter and the 7850 will be a secondary (extended) adapter. So, the question is; what are you trying to accomplish? Thanks, Kelly _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel