Hi Xen community,
I''ve been playing with gpu passthrough for a while now, without
success, so
i''m starting to think that my hardware is the problem.
My config:
Motherboard: supermicro x9scl+
CPU: Intel® Xeon® Processor E3-1230 V2
Memory: 32GB ECC
GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1.
http://wiki.xen.org/wiki/VTd_HowTo
Only devices with FLR capabilities are supported.
so did the lspci -vv, this gives me the output:
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
FLReset not supported by my GPU. Hmm, So? Can i forget about it, and get a
new gpu? or are there any workarounds availble?
Also i see that my motherboard + cpu is not on the supported list inhere:
http://wiki.xen.org/wiki/VTd_HowTo
What hardware could i switch to get a working config? New motherboard, and
keep the cpu + memory? Only new GPU?
Running on Xen 4.3 unstable on debian squeeze with custom kernel on linux
3.6.1. pciback works fine. I can add all pci devices to the vm, install
the amd drivers without problems, but when starting the windows 7 x64
ultimate machine after the install it hangs at Starting Windows.
Any tips would be great.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
Hi, I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and Windows 8 Preview/Consumer and lspci -vv outputs exactly the same string. A quick Google search does identify both CPU and motherboard has having VT-d support on manufacturer homepages. So in terms of hardware you''re pretty much ok. However I''m using Debian Wheezy, distro''s Xen 4.1.3, kernel 3.2.0 and 3.5-trunk, xm toolstack and pci-stub. However I''m unable to successfully passthrough using pciback. Haven''t tried Windows 7 though. Best regards, Ricardo Jesus. On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf <d.vander.wurf@gmail.com> wrote:> Hi Xen community, > > > I''ve been playing with gpu passthrough for a while now, without success, so > i''m starting to think that my hardware is the problem. > > > > My config: > > Motherboard: supermicro x9scl+ > > CPU: Intel® Xeon® Processor E3-1230 V2 > > Memory: 32GB ECC > > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. > > > > http://wiki.xen.org/wiki/VTd_HowTo > > Only devices with FLR capabilities are supported. > > > > so did the lspci -vv, this gives me the output: > > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > > > > FLReset not supported by my GPU. Hmm, So? Can i forget about it, and get a > new gpu? or are there any workarounds availble? > > > > Also i see that my motherboard + cpu is not on the supported list inhere: > http://wiki.xen.org/wiki/VTd_HowTo > > > > What hardware could i switch to get a working config? New motherboard, and > keep the cpu + memory? Only new GPU? > > > > Running on Xen 4.3 unstable on debian squeeze with custom kernel on linux > 3.6.1. pciback works fine. I can add all pci devices to the vm, install the > amd drivers without problems, but when starting the windows 7 x64 ultimate > machine after the install it hangs at Starting Windows. > > Any tips would be great. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
My hardware supports vt-d without a doubt because i am able to passthrough other devices without a problem but still i can''t get vga passthrough to work. Als tried a windows 8 dom-u now. - built the dom-u without passhtrough first. Windows 8 runs like a charm. - then i add the pci devices. Windows detects the ATI Mobility Radeon HD 5000 Series and uses the built-in WDDM v1.20 driver, but cannot start the device (Code 10) in device manager. - i see the passthrough HD Audio device without exclamation mark. - i see the passthrough usb devices, and can plug in a usb stick and copy files from it. - then i installed the current catalyst driver package 12.8 for win8, and the vm hangs during installation. Still i am thinking about if my hardware is the root cause? it''s not on the supported list, and i read a lot of things about finding the right hardware combination to get it working. Especcialy on esx (didn''t work for me), xenserver (also no success) and now Xen which also doesn''t seem to work. So are there any people out there who use my hardware, and got it working? (motherboard, cpu and gpu?). 2012/10/12 Ricardo Jesus <ricardo.meb.jesus@gmail.com>> Hi, > > I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 > and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and > Windows 8 Preview/Consumer and lspci -vv outputs exactly the same > string. > > A quick Google search does identify both CPU and motherboard has > having VT-d support on manufacturer homepages. So in terms of hardware > you''re pretty much ok. > > However I''m using Debian Wheezy, distro''s Xen 4.1.3, kernel 3.2.0 and > 3.5-trunk, xm toolstack and pci-stub. However I''m unable to > successfully passthrough using pciback. > > Haven''t tried Windows 7 though. > > > Best regards, > Ricardo Jesus. > > > On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf > <d.vander.wurf@gmail.com> wrote: > > Hi Xen community, > > > > > > I''ve been playing with gpu passthrough for a while now, without success, > so > > i''m starting to think that my hardware is the problem. > > > > > > > > My config: > > > > Motherboard: supermicro x9scl+ > > > > CPU: Intel® Xeon® Processor E3-1230 V2 > > > > Memory: 32GB ECC > > > > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. > > > > > > > > http://wiki.xen.org/wiki/VTd_HowTo > > > > Only devices with FLR capabilities are supported. > > > > > > > > so did the lspci -vv, this gives me the output: > > > > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > > > > > > > > FLReset not supported by my GPU. Hmm, So? Can i forget about it, and get > a > > new gpu? or are there any workarounds availble? > > > > > > > > Also i see that my motherboard + cpu is not on the supported list inhere: > > http://wiki.xen.org/wiki/VTd_HowTo > > > > > > > > What hardware could i switch to get a working config? New motherboard, > and > > keep the cpu + memory? Only new GPU? > > > > > > > > Running on Xen 4.3 unstable on debian squeeze with custom kernel on linux > > 3.6.1. pciback works fine. I can add all pci devices to the vm, install > the > > amd drivers without problems, but when starting the windows 7 x64 > ultimate > > machine after the install it hangs at Starting Windows. > > > > Any tips would be great. > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
One more question. I read that for nvidia some patches need to be applied. So in my understanding for AMD, no patches are needed. It should just work out of the box? Donald 2012/10/13 Donald van der Wurf <d.vander.wurf@gmail.com>> My hardware supports vt-d without a doubt because i am able to passthrough > other devices without a problem but still i can''t get vga passthrough to > work. > > Als tried a windows 8 dom-u now. > - built the dom-u without passhtrough first. Windows 8 runs like a charm. > - then i add the pci devices. Windows detects the ATI Mobility Radeon HD > 5000 Series and uses the built-in WDDM v1.20 driver, but cannot start the > device (Code 10) in device manager. > - i see the passthrough HD Audio device without exclamation mark. > - i see the passthrough usb devices, and can plug in a usb stick and copy > files from it. > - then i installed the current catalyst driver package 12.8 for win8, and > the vm hangs during installation. > > Still i am thinking about if my hardware is the root cause? it''s not on > the supported list, and i read a lot of things about finding the right > hardware combination to get it working. Especcialy on esx (didn''t work for > me), xenserver (also no success) and now Xen which also doesn''t seem to > work. > So are there any people out there who use my hardware, and got it working? > (motherboard, cpu and gpu?). > > > > > 2012/10/12 Ricardo Jesus <ricardo.meb.jesus@gmail.com> > >> Hi, >> >> I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 >> and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and >> Windows 8 Preview/Consumer and lspci -vv outputs exactly the same >> string. >> >> A quick Google search does identify both CPU and motherboard has >> having VT-d support on manufacturer homepages. So in terms of hardware >> you''re pretty much ok. >> >> However I''m using Debian Wheezy, distro''s Xen 4.1.3, kernel 3.2.0 and >> 3.5-trunk, xm toolstack and pci-stub. However I''m unable to >> successfully passthrough using pciback. >> >> Haven''t tried Windows 7 though. >> >> >> Best regards, >> Ricardo Jesus. >> >> >> On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf >> <d.vander.wurf@gmail.com> wrote: >> > Hi Xen community, >> > >> > >> > I''ve been playing with gpu passthrough for a while now, without >> success, so >> > i''m starting to think that my hardware is the problem. >> > >> > >> > >> > My config: >> > >> > Motherboard: supermicro x9scl+ >> > >> > CPU: Intel® Xeon® Processor E3-1230 V2 >> > >> > Memory: 32GB ECC >> > >> > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. >> > >> > >> > >> > http://wiki.xen.org/wiki/VTd_HowTo >> > >> > Only devices with FLR capabilities are supported. >> > >> > >> > >> > so did the lspci -vv, this gives me the output: >> > >> > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- >> > >> > >> > >> > FLReset not supported by my GPU. Hmm, So? Can i forget about it, and >> get a >> > new gpu? or are there any workarounds availble? >> > >> > >> > >> > Also i see that my motherboard + cpu is not on the supported list >> inhere: >> > http://wiki.xen.org/wiki/VTd_HowTo >> > >> > >> > >> > What hardware could i switch to get a working config? New motherboard, >> and >> > keep the cpu + memory? Only new GPU? >> > >> > >> > >> > Running on Xen 4.3 unstable on debian squeeze with custom kernel on >> linux >> > 3.6.1. pciback works fine. I can add all pci devices to the vm, >> install the >> > amd drivers without problems, but when starting the windows 7 x64 >> ultimate >> > machine after the install it hangs at Starting Windows. >> > >> > Any tips would be great. >> > >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xen.org >> > http://lists.xen.org/xen-users >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I didn''t apply any patches just used the stock Debian 4.1.3 package. As I said I have pretty the same GPU... and it works. Though I too had the domU Win8 crashing when trying to install Catalyst 12.8 and 12.9. Worked around the issue by extracting the files and installing the drivers through Device Manager point to the extracted files directory. I should noted that Win8 was installed via VNC, updated .cfg with PCI devices used gfx_passthrouh=0, booted to Win8, defined the HD5450 powered screen has the primary display and then proceeded to install AMD driver - though the VM worked just fine with MS supplied drivers. Sent from my Android device. On Oct 13, 2012 11:35 AM, "Donald van der Wurf" <d.vander.wurf@gmail.com> wrote:> > One more question. > I read that for nvidia some patches need to be applied. > So in my understanding for AMD, no patches are needed. It should justwork out of the box?> > Donald > > > 2012/10/13 Donald van der Wurf <d.vander.wurf@gmail.com> >> >> My hardware supports vt-d without a doubt because i am able topassthrough other devices without a problem but still i can''t get vga passthrough to work.>> >> Als tried a windows 8 dom-u now. >> - built the dom-u without passhtrough first. Windows 8 runs like acharm.>> - then i add the pci devices. Windows detects the ATI Mobility Radeon HD5000 Series and uses the built-in WDDM v1.20 driver, but cannot start the device (Code 10) in device manager.>> - i see the passthrough HD Audio device without exclamation mark. >> - i see the passthrough usb devices, and can plug in a usb stick andcopy files from it.>> - then i installed the current catalyst driver package 12.8 for win8,and the vm hangs during installation.>> >> Still i am thinking about if my hardware is the root cause? it''s not onthe supported list, and i read a lot of things about finding the right hardware combination to get it working. Especcialy on esx (didn''t work for me), xenserver (also no success) and now Xen which also doesn''t seem to work.>> So are there any people out there who use my hardware, and got itworking? (motherboard, cpu and gpu?).>> >> >> >> >> 2012/10/12 Ricardo Jesus <ricardo.meb.jesus@gmail.com> >>> >>> Hi, >>> >>> I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 >>> and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and >>> Windows 8 Preview/Consumer and lspci -vv outputs exactly the same >>> string. >>> >>> A quick Google search does identify both CPU and motherboard has >>> having VT-d support on manufacturer homepages. So in terms of hardware >>> you''re pretty much ok. >>> >>> However I''m using Debian Wheezy, distro''s Xen 4.1.3, kernel 3.2.0 and >>> 3.5-trunk, xm toolstack and pci-stub. However I''m unable to >>> successfully passthrough using pciback. >>> >>> Haven''t tried Windows 7 though. >>> >>> >>> Best regards, >>> Ricardo Jesus. >>> >>> >>> On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf >>> <d.vander.wurf@gmail.com> wrote: >>> > Hi Xen community, >>> > >>> > >>> > I''ve been playing with gpu passthrough for a while now, withoutsuccess, so>>> > i''m starting to think that my hardware is the problem. >>> > >>> > >>> > >>> > My config: >>> > >>> > Motherboard: supermicro x9scl+ >>> > >>> > CPU: Intel® Xeon® Processor E3-1230 V2 >>> > >>> > Memory: 32GB ECC >>> > >>> > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. >>> > >>> > >>> > >>> > http://wiki.xen.org/wiki/VTd_HowTo >>> > >>> > Only devices with FLR capabilities are supported. >>> > >>> > >>> > >>> > so did the lspci -vv, this gives me the output: >>> > >>> > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+FLReset->>> > >>> > >>> > >>> > FLReset not supported by my GPU. Hmm, So? Can i forget about it, andget a>>> > new gpu? or are there any workarounds availble? >>> > >>> > >>> > >>> > Also i see that my motherboard + cpu is not on the supported listinhere:>>> > http://wiki.xen.org/wiki/VTd_HowTo >>> > >>> > >>> > >>> > What hardware could i switch to get a working config? Newmotherboard, and>>> > keep the cpu + memory? Only new GPU? >>> > >>> > >>> > >>> > Running on Xen 4.3 unstable on debian squeeze with custom kernel onlinux>>> > 3.6.1. pciback works fine. I can add all pci devices to the vm,install the>>> > amd drivers without problems, but when starting the windows 7 x64ultimate>>> > machine after the install it hangs at Starting Windows. >>> > >>> > Any tips would be great. >>> > >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xen.org >>> > http://lists.xen.org/xen-users >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
2012/10/13 Donald van der Wurf <d.vander.wurf@gmail.com>> One more question. > I read that for nvidia some patches need to be applied. > So in my understanding for AMD, no patches are needed. It should just work > out of the box? > > Donald > > > Yes, the patches are applied only for nvidia gfx''s.And about VTd how to wiki page, it is just outdated and many motherboards just isn''t listed in there. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Donald, I didn't have to install any patches when I got my system up and running, however its a little different from yours; I'm running an AMD Phenom II x4 965 on an ASUS Sabretooth 990FX r1.0 motherboard. The system has two graphics cards; an NVidia GeForce 550Ti (used by dom0) and an ATI Radeon HD 6770 passed through to a Windows 7 domU. Some things I've noted so far: I've not been able to have the GPLPV drivers installed at the same time as the Catalyst drivers; it would cause issues such as the Catalyst installer to crash or the system to blue-screen on bootup. I had to add on the option 'iommu=soft' when nooting my dom0 (this might not still be needed but isn't hurting anything). I also was having issues with the 12.8 Catalyst drivers; I used the 12.7 instead and had less issues getting them installed. Regards, David ----- Original Message ----- From: "Donald van der Wurf" <d.vander.wurf@gmail.com> To: "Ricardo Jesus" <ricardo.meb.jesus@gmail.com> Cc: xen-users@lists.xen.org Sent: Saturday, October 13, 2012 5:35:59 AM Subject: Re: [Xen-users] vga passthrough help needed. One more question. I read that for nvidia some patches need to be applied. So in my understanding for AMD, no patches are needed. It should just work out of the box? Donald 2012/10/13 Donald van der Wurf < d.vander.wurf@gmail.com > My hardware supports vt-d without a doubt because i am able to passthrough other devices without a problem but still i can't get vga passthrough to work. Als tried a windows 8 dom-u now. - built the dom-u without passhtrough first. Windows 8 runs like a charm. - then i add the pci devices. Windows detects the ATI Mobility Radeon HD 5000 Series and uses the built-in WDDM v1.20 driver, but cannot start the device (Code 10) in device manager. - i see the passthrough HD Audio device without exclamation mark. - i see the passthrough usb devices, and can plug in a usb stick and copy files from it. - then i installed the current catalyst driver package 12.8 for win8, and the vm hangs during installation. Still i am thinking about if my hardware is the root cause? it's not on the supported list, and i read a lot of things about finding the right hardware combination to get it working. Especcialy on esx (didn't work for me), xenserver (also no success) and now Xen which also doesn't seem to work. So are there any people out there who use my hardware, and got it working? (motherboard, cpu and gpu?). 2012/10/12 Ricardo Jesus < ricardo.meb.jesus@gmail.com > Hi, I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and Windows 8 Preview/Consumer and lspci -vv outputs exactly the same string. A quick Google search does identify both CPU and motherboard has having VT-d support on manufacturer homepages. So in terms of hardware you're pretty much ok. However I'm using Debian Wheezy, distro's Xen 4.1.3, kernel 3.2.0 and 3.5-trunk, xm toolstack and pci-stub. However I'm unable to successfully passthrough using pciback. Haven't tried Windows 7 though. Best regards, Ricardo Jesus. On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf < d.vander.wurf@gmail.com > wrote:> Hi Xen community, > > > I've been playing with gpu passthrough for a while now, without success, so > i'm starting to think that my hardware is the problem. > > > > My config: > > Motherboard: supermicro x9scl+ > > CPU: Intel® Xeon® Processor E3-1230 V2 > > Memory: 32GB ECC > > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. > > > > http://wiki.xen.org/wiki/VTd_HowTo > > Only devices with FLR capabilities are supported. > > > > so did the lspci -vv, this gives me the output: > > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > > > > FLReset not supported by my GPU. Hmm, So? Can i forget about it, and get a > new gpu? or are there any workarounds availble? > > > > Also i see that my motherboard + cpu is not on the supported list inhere: > http://wiki.xen.org/wiki/VTd_HowTo > > > > What hardware could i switch to get a working config? New motherboard, and > keep the cpu + memory? Only new GPU? > > > > Running on Xen 4.3 unstable on debian squeeze with custom kernel on linux > 3.6.1. pciback works fine. I can add all pci devices to the vm, install the > amd drivers without problems, but when starting the windows 7 x64 ultimate > machine after the install it hangs at Starting Windows. > > Any tips would be great. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I did a rebuild of my host: - Ubuntu 12.10 Quantal Quetzal - Did a custom firmware build like described in: http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial - installed the xen 4.1 included with 12.10. - I experience the same problems as before. - I''m posting my log in hope that someone understands the errors i see: - googled the errors, and i see some posts that talk about extracting the bios of the vga card, but only for nvidia video adapters. My adapter is AMD, so then this is not required? - also some posts about BAR issues, for which i''m a little lost what to do with them. Can someone put me on track how to solve this? donald@xen01:/var/log/xen$ cat qemu-dm-mc01.log domid: 3 -c config qemu network with xen bridge for vif3.0-emu xenbr0 Using file /dev/vg0/mc01.s in read-write mode Using file /iso/Windows8EnterpriseV.1.0.iso in read-only mode Watching /local/domain/0/device-model/3/logdirty/cmd Watching /local/domain/0/device-model/3/command Watching /local/domain/3/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 8aa3304f-c86f-6768-d23f-129e3f15395a Time offset set 0 populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/8aa3304f-c86f-6768-d23f-129e3f15395a/vncpasswd. medium change watch on `hdb'' (index: 1): /iso/HunterWindows8EnterpriseV.1.0.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. xs_read(/local/domain/3/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/3/log-throttling'' medium change watch on `/local/domain/3/log-throttling'' - unknown device, ignored dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 02:00.0 ... register_real_device: Enable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such file or directory: 0x2:0x0.0x0 pt_register_regions: IO region registered (size=0x00020000 base_addr=0xdfb20004) pt_register_regions: IO region registered (size=0x00000100 base_addr=0x00002001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xdfb40000) pt_msi_setup: msi mapped with pirq 37 pci_intx: intx=1 register_real_device: Real physical device 02:00.0 registered successfuly! IRQ type = MSI-INTx dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 02:00.1 ... register_real_device: Enable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such file or directory: 0x2:0x0.0x1 pt_register_regions: IO region registered (size=0x00004000 base_addr=0xdfb00004) pt_msi_setup: msi mapped with pirq 36 pci_intx: intx=2 register_real_device: Real physical device 02:00.1 registered successfuly! IRQ type = MSI-INTx dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 00:1a.0 ... register_real_device: Enable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1a.0x0 pt_register_regions: IO region registered (size=0x00000400 base_addr=0xdfc04000) pci_intx: intx=1 register_real_device: Real physical device 00:1a.0 registered successfuly! IRQ type = INTx dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 00:1d.0 ... register_real_device: Enable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x1d.0x0 pt_register_regions: IO region registered (size=0x00000400 base_addr=0xdfc03000) pci_intx: intx=1 register_real_device: Real physical device 00:1d.0 registered successfuly! IRQ type = INTx pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:10h][Length:4] pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:10h][Length:4] cirrus vga map change while on lfb mode pt_iomem_map: e_phys=f3020000 maddr=dfb20000 type=0 len=131072 index=2 first_map=1 pt_iomem_map: e_phys=f3060000 maddr=dfb00000 type=0 len=16384 index=0 first_map=1 pt_iomem_map: e_phys=f3065000 maddr=dfc04000 type=0 len=4096 index=0 first_map=1 pt_iomem_map: e_phys=f3066000 maddr=dfc03000 type=0 len=4096 index=0 first_map=1 pt_ioport_map: e_phys=c100 pio_base=2000 len=256 index=4 first_map=1 mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:05.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_pci_read_config: Error: Failed to read register with invalid access size alignment. [00:06.0][Offset:0eh][Length:4] pt_iomem_map: e_phys=ffffffff maddr=dfb20000 type=0 len=131072 index=2 first_map=0 pt_ioport_map: e_phys=ffff pio_base=2000 len=256 index=4 first_map=0 pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:10h][Length:4] pt_iomem_map: e_phys=f3020000 maddr=dfb20000 type=0 len=131072 index=2 first_map=0 pt_ioport_map: e_phys=c100 pio_base=2000 len=256 index=4 first_map=0 pt_iomem_map: e_phys=ffffffff maddr=dfb00000 type=0 len=16384 index=0 first_map=0 pt_iomem_map: e_phys=f3060000 maddr=dfb00000 type=0 len=16384 index=0 first_map=0 pt_iomem_map: e_phys=ffffffff maddr=dfc04000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=f3065000 maddr=dfc04000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=ffffffff maddr=dfc03000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=f3066000 maddr=dfc03000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=ffffffff maddr=dfb20000 type=0 len=131072 index=2 first_map=0 pt_ioport_map: e_phys=ffff pio_base=2000 len=256 index=4 first_map=0 pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:10h][Length:4] pt_iomem_map: e_phys=f3020000 maddr=dfb20000 type=0 len=131072 index=2 first_map=0 pt_ioport_map: e_phys=c100 pio_base=2000 len=256 index=4 first_map=0 pt_msgctrl_reg_write: guest enabling MSI, disable MSI-INTx translation pci_intx: intx=1 pt_msi_update: Update msi with pirq 37 gvec a2 gflags 1303 pt_iomem_map: e_phys=ffffffff maddr=dfc04000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=ffffffff maddr=dfb00000 type=0 len=16384 index=0 first_map=0 pt_iomem_map: e_phys=f3065000 maddr=dfc04000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=f3060000 maddr=dfb00000 type=0 len=16384 index=0 first_map=0 pt_iomem_map: e_phys=ffffffff maddr=dfc03000 type=0 len=4096 index=0 first_map=0 pt_iomem_map: e_phys=f3066000 maddr=dfc03000 type=0 len=4096 index=0 first_map=0 2012/10/13 David Sutton <pere@kantras.info>> Donald, > > I didn''t have to install any patches when I got my system up and > running, however its a little different from yours; > > I''m running an AMD Phenom II x4 965 on an ASUS Sabretooth 990FX r1.0 > motherboard. The system has two graphics cards; an NVidia GeForce 550Ti > (used by dom0) and an ATI Radeon HD 6770 passed through to a Windows 7 > domU. Some things I''ve noted so far: I''ve not been able to have the GPLPV > drivers installed at the same time as the Catalyst drivers; it would cause > issues such as the Catalyst installer to crash or the system to blue-screen > on bootup. I had to add on the option ''iommu=soft'' when nooting my dom0 > (this might not still be needed but isn''t hurting anything). I also was > having issues with the 12.8 Catalyst drivers; I used the 12.7 instead and > had less issues getting them installed. > > Regards, > > David > > ----- Original Message ----- > From: "Donald van der Wurf" <d.vander.wurf@gmail.com> > To: "Ricardo Jesus" <ricardo.meb.jesus@gmail.com> > Cc: xen-users@lists.xen.org > Sent: Saturday, October 13, 2012 5:35:59 AM > Subject: Re: [Xen-users] vga passthrough help needed. > > One more question. > I read that for nvidia some patches need to be applied. > So in my understanding for AMD, no patches are needed. It should just work > out of the box? > > Donald > > 2012/10/13 Donald van der Wurf < d.vander.wurf@gmail.com > > > > My hardware supports vt-d without a doubt because i am able to passthrough > other devices without a problem but still i can''t get vga passthrough to > work. > > Als tried a windows 8 dom-u now. > - built the dom-u without passhtrough first. Windows 8 runs like a charm. > - then i add the pci devices. Windows detects the ATI Mobility Radeon HD > 5000 Series and uses the built-in WDDM v1.20 driver, but cannot start the > device (Code 10) in device manager. > - i see the passthrough HD Audio device without exclamation mark. > - i see the passthrough usb devices, and can plug in a usb stick and copy > files from it. > - then i installed the current catalyst driver package 12.8 for win8, and > the vm hangs during installation. > > Still i am thinking about if my hardware is the root cause? it''s not on > the supported list, and i read a lot of things about finding the right > hardware combination to get it working. Especcialy on esx (didn''t work for > me), xenserver (also no success) and now Xen which also doesn''t seem to > work. > So are there any people out there who use my hardware, and got it working? > (motherboard, cpu and gpu?). > > > > 2012/10/12 Ricardo Jesus < ricardo.meb.jesus@gmail.com > > > > Hi, > > I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 > and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and > Windows 8 Preview/Consumer and lspci -vv outputs exactly the same > string. > > A quick Google search does identify both CPU and motherboard has > having VT-d support on manufacturer homepages. So in terms of hardware > you''re pretty much ok. > > However I''m using Debian Wheezy, distro''s Xen 4.1.3, kernel 3.2.0 and > 3.5-trunk, xm toolstack and pci-stub. However I''m unable to > successfully passthrough using pciback. > > Haven''t tried Windows 7 though. > > > Best regards, > Ricardo Jesus. > > > On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf > < d.vander.wurf@gmail.com > wrote: > > Hi Xen community, > > > > > > I''ve been playing with gpu passthrough for a while now, without success, > so > > i''m starting to think that my hardware is the problem. > > > > > > > > My config: > > > > Motherboard: supermicro x9scl+ > > > > CPU: Intel® Xeon® Processor E3-1230 V2 > > > > Memory: 32GB ECC > > > > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. > > > > > > > > http://wiki.xen.org/wiki/VTd_HowTo > > > > Only devices with FLR capabilities are supported. > > > > > > > > so did the lspci -vv, this gives me the output: > > > > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > > > > > > > > FLReset not supported by my GPU. Hmm, So? Can i forget about it, and get > a > > new gpu? or are there any workarounds availble? > > > > > > > > Also i see that my motherboard + cpu is not on the supported list inhere: > > http://wiki.xen.org/wiki/VTd_HowTo > > > > > > > > What hardware could i switch to get a working config? New motherboard, > and > > keep the cpu + memory? Only new GPU? > > > > > > > > Running on Xen 4.3 unstable on debian squeeze with custom kernel on linux > > 3.6.1. pciback works fine. I can add all pci devices to the vm, install > the > > amd drivers without problems, but when starting the windows 7 x64 > ultimate > > machine after the install it hangs at Starting Windows. > > > > Any tips would be great. > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
My proposition is to try with setup You have now but with windows xp or windows 7. Windows 8 is pretty new and it maybe have some problems under xen. If You will confirm that linux/xen installation work with windows system then will be easier for You to find where the problem is. 2012/10/21 Donald van der Wurf <d.vander.wurf@gmail.com>> I did a rebuild of my host: > - Ubuntu 12.10 Quantal Quetzal > - Did a custom firmware build like described in: > http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial > - installed the xen 4.1 included with 12.10. > - I experience the same problems as before. > > - I''m posting my log in hope that someone understands the errors i see: > - googled the errors, and i see some posts that talk about extracting the > bios of the vga card, but only for nvidia video adapters. My adapter is > AMD, so then this is not required? > - also some posts about BAR issues, for which i''m a little lost what to do > with them. > Can someone put me on track how to solve this? > > donald@xen01:/var/log/xen$ cat qemu-dm-mc01.log > domid: 3 > -c config qemu network with xen bridge for > vif3.0-emu xenbr0 > Using file /dev/vg0/mc01.s in read-write mode > Using file /iso/Windows8EnterpriseV.1.0.iso in read-only mode > Watching /local/domain/0/device-model/3/logdirty/cmd > Watching /local/domain/0/device-model/3/command > Watching /local/domain/3/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 8aa3304f-c86f-6768-d23f-129e3f15395a > Time offset set 0 > > populating video RAM at ff000000 > > mapping video RAM from ff000000 > > Register xen platform. > > Done register platform. > > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read > error > xs_read(): vncpasswd get error. > /vm/8aa3304f-c86f-6768-d23f-129e3f15395a/vncpasswd. > > medium change watch on `hdb'' (index: 1): > /iso/HunterWindows8EnterpriseV.1.0.iso > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > > Log-dirty: no command yet. > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > > vcpu-set: watch node error. > xs_read(/local/domain/3/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/3/log-throttling'' > medium change watch on `/local/domain/3/log-throttling'' - unknown device, > ignored > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 02:00.0 ... > register_real_device: Enable MSI translation via per device option > register_real_device: Disable power management > pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No > such file or directory: 0x2:0x0.0x0 > pt_register_regions: IO region registered (size=0x00020000 > base_addr=0xdfb20004) > pt_register_regions: IO region registered (size=0x00000100 > base_addr=0x00002001) > pt_register_regions: Expansion ROM registered (size=0x00020000 > base_addr=0xdfb40000) > pt_msi_setup: msi mapped with pirq 37 > pci_intx: intx=1 > register_real_device: Real physical device 02:00.0 registered successfuly! > IRQ type = MSI-INTx > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 02:00.1 ... > register_real_device: Enable MSI translation via per device option > register_real_device: Disable power management > pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No > such file or directory: 0x2:0x0.0x1 > pt_register_regions: IO region registered (size=0x00004000 > base_addr=0xdfb00004) > pt_msi_setup: msi mapped with pirq 36 > pci_intx: intx=2 > register_real_device: Real physical device 02:00.1 registered successfuly! > IRQ type = MSI-INTx > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 00:1a.0 ... > register_real_device: Enable MSI translation via per device option > register_real_device: Disable power management > pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No > such file or directory: 0x0:0x1a.0x0 > pt_register_regions: IO region registered (size=0x00000400 > base_addr=0xdfc04000) > pci_intx: intx=1 > register_real_device: Real physical device 00:1a.0 registered successfuly! > IRQ type = INTx > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 00:1d.0 ... > register_real_device: Enable MSI translation via per device option > register_real_device: Disable power management > pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No > such file or directory: 0x0:0x1d.0x0 > pt_register_regions: IO region registered (size=0x00000400 > base_addr=0xdfc03000) > pci_intx: intx=1 > register_real_device: Real physical device 00:1d.0 registered successfuly! > IRQ type = INTx > pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:05.0][Offset:10h][Length:4] > pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:05.0][Offset:10h][Length:4] > cirrus vga map change while on lfb mode > pt_iomem_map: e_phys=f3020000 maddr=dfb20000 type=0 len=131072 index=2 > first_map=1 > pt_iomem_map: e_phys=f3060000 maddr=dfb00000 type=0 len=16384 index=0 > first_map=1 > pt_iomem_map: e_phys=f3065000 maddr=dfc04000 type=0 len=4096 index=0 > first_map=1 > pt_iomem_map: e_phys=f3066000 maddr=dfc03000 type=0 len=4096 index=0 > first_map=1 > pt_ioport_map: e_phys=c100 pio_base=2000 len=256 index=4 first_map=1 > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro > state. > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:05.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_pci_read_config: Error: Failed to read register with invalid access > size alignment. [00:06.0][Offset:0eh][Length:4] > pt_iomem_map: e_phys=ffffffff maddr=dfb20000 type=0 len=131072 index=2 > first_map=0 > pt_ioport_map: e_phys=ffff pio_base=2000 len=256 index=4 first_map=0 > pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:05.0][Offset:10h][Length:4] > pt_iomem_map: e_phys=f3020000 maddr=dfb20000 type=0 len=131072 index=2 > first_map=0 > pt_ioport_map: e_phys=c100 pio_base=2000 len=256 index=4 first_map=0 > pt_iomem_map: e_phys=ffffffff maddr=dfb00000 type=0 len=16384 index=0 > first_map=0 > pt_iomem_map: e_phys=f3060000 maddr=dfb00000 type=0 len=16384 index=0 > first_map=0 > pt_iomem_map: e_phys=ffffffff maddr=dfc04000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=f3065000 maddr=dfc04000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=ffffffff maddr=dfc03000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=f3066000 maddr=dfc03000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=ffffffff maddr=dfb20000 type=0 len=131072 index=2 > first_map=0 > pt_ioport_map: e_phys=ffff pio_base=2000 len=256 index=4 first_map=0 > pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:05.0][Offset:10h][Length:4] > pt_iomem_map: e_phys=f3020000 maddr=dfb20000 type=0 len=131072 index=2 > first_map=0 > pt_ioport_map: e_phys=c100 pio_base=2000 len=256 index=4 first_map=0 > pt_msgctrl_reg_write: guest enabling MSI, disable MSI-INTx translation > pci_intx: intx=1 > pt_msi_update: Update msi with pirq 37 gvec a2 gflags 1303 > pt_iomem_map: e_phys=ffffffff maddr=dfc04000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=ffffffff maddr=dfb00000 type=0 len=16384 index=0 > first_map=0 > pt_iomem_map: e_phys=f3065000 maddr=dfc04000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=f3060000 maddr=dfb00000 type=0 len=16384 index=0 > first_map=0 > pt_iomem_map: e_phys=ffffffff maddr=dfc03000 type=0 len=4096 index=0 > first_map=0 > pt_iomem_map: e_phys=f3066000 maddr=dfc03000 type=0 len=4096 index=0 > first_map=0 > > 2012/10/13 David Sutton <pere@kantras.info> > >> Donald, >> >> I didn''t have to install any patches when I got my system up and >> running, however its a little different from yours; >> >> I''m running an AMD Phenom II x4 965 on an ASUS Sabretooth 990FX r1.0 >> motherboard. The system has two graphics cards; an NVidia GeForce 550Ti >> (used by dom0) and an ATI Radeon HD 6770 passed through to a Windows 7 >> domU. Some things I''ve noted so far: I''ve not been able to have the GPLPV >> drivers installed at the same time as the Catalyst drivers; it would cause >> issues such as the Catalyst installer to crash or the system to blue-screen >> on bootup. I had to add on the option ''iommu=soft'' when nooting my dom0 >> (this might not still be needed but isn''t hurting anything). I also was >> having issues with the 12.8 Catalyst drivers; I used the 12.7 instead and >> had less issues getting them installed. >> >> Regards, >> >> David >> >> ----- Original Message ----- >> From: "Donald van der Wurf" <d.vander.wurf@gmail.com> >> To: "Ricardo Jesus" <ricardo.meb.jesus@gmail.com> >> Cc: xen-users@lists.xen.org >> Sent: Saturday, October 13, 2012 5:35:59 AM >> Subject: Re: [Xen-users] vga passthrough help needed. >> >> One more question. >> I read that for nvidia some patches need to be applied. >> So in my understanding for AMD, no patches are needed. It should just >> work out of the box? >> >> Donald >> >> 2012/10/13 Donald van der Wurf < d.vander.wurf@gmail.com > >> >> >> My hardware supports vt-d without a doubt because i am able to >> passthrough other devices without a problem but still i can''t get vga >> passthrough to work. >> >> Als tried a windows 8 dom-u now. >> - built the dom-u without passhtrough first. Windows 8 runs like a charm. >> - then i add the pci devices. Windows detects the ATI Mobility Radeon HD >> 5000 Series and uses the built-in WDDM v1.20 driver, but cannot start the >> device (Code 10) in device manager. >> - i see the passthrough HD Audio device without exclamation mark. >> - i see the passthrough usb devices, and can plug in a usb stick and copy >> files from it. >> - then i installed the current catalyst driver package 12.8 for win8, and >> the vm hangs during installation. >> >> Still i am thinking about if my hardware is the root cause? it''s not on >> the supported list, and i read a lot of things about finding the right >> hardware combination to get it working. Especcialy on esx (didn''t work for >> me), xenserver (also no success) and now Xen which also doesn''t seem to >> work. >> So are there any people out there who use my hardware, and got it >> working? (motherboard, cpu and gpu?). >> >> >> >> 2012/10/12 Ricardo Jesus < ricardo.meb.jesus@gmail.com > >> >> >> Hi, >> >> I have a similar GPU PowerColor Go! Green HD5450 1024MB DDR3 PCIEx16 >> and it sure does support VGA/PCI passthrough on Ubuntu 12.04 LTS and >> Windows 8 Preview/Consumer and lspci -vv outputs exactly the same >> string. >> >> A quick Google search does identify both CPU and motherboard has >> having VT-d support on manufacturer homepages. So in terms of hardware >> you''re pretty much ok. >> >> However I''m using Debian Wheezy, distro''s Xen 4.1.3, kernel 3.2.0 and >> 3.5-trunk, xm toolstack and pci-stub. However I''m unable to >> successfully passthrough using pciback. >> >> Haven''t tried Windows 7 though. >> >> >> Best regards, >> Ricardo Jesus. >> >> >> On Thu, Oct 11, 2012 at 10:26 PM, Donald van der Wurf >> < d.vander.wurf@gmail.com > wrote: >> > Hi Xen community, >> > >> > >> > I''ve been playing with gpu passthrough for a while now, without >> success, so >> > i''m starting to think that my hardware is the problem. >> > >> > >> > >> > My config: >> > >> > Motherboard: supermicro x9scl+ >> > >> > CPU: Intel® Xeon® Processor E3-1230 V2 >> > >> > Memory: 32GB ECC >> > >> > GPU: PowerColor Go! Green HD5450 512MB DDR2 PCIEx1. >> > >> > >> > >> > http://wiki.xen.org/wiki/VTd_HowTo >> > >> > Only devices with FLR capabilities are supported. >> > >> > >> > >> > so did the lspci -vv, this gives me the output: >> > >> > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- >> > >> > >> > >> > FLReset not supported by my GPU. Hmm, So? Can i forget about it, and >> get a >> > new gpu? or are there any workarounds availble? >> > >> > >> > >> > Also i see that my motherboard + cpu is not on the supported list >> inhere: >> > http://wiki.xen.org/wiki/VTd_HowTo >> > >> > >> > >> > What hardware could i switch to get a working config? New motherboard, >> and >> > keep the cpu + memory? Only new GPU? >> > >> > >> > >> > Running on Xen 4.3 unstable on debian squeeze with custom kernel on >> linux >> > 3.6.1. pciback works fine. I can add all pci devices to the vm, install >> the >> > amd drivers without problems, but when starting the windows 7 x64 >> ultimate >> > machine after the install it hangs at Starting Windows. >> > >> > Any tips would be great. >> > >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xen.org >> > http://lists.xen.org/xen-users >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users