Hi, everyone. I''m Guilherme Suzuki (brazillian, by the way) and really interested in xen-vga-passthru. Lately, I bought a brand new Saphire HD 7950 (OC Boost) because I saw in a wiki somewhere that users have been able to passthru these VGA devices to domU (win7, win-xp and so on). But, after I installed it, I executed *lspci -vv* to check if FLR in DevCap was present (which it''s *not*). I''ve managed, though, to put my virtual machine to work out with the HD 7950 as a secondary device. Sometimes, I have to reboot dom0 to make things work. So, here''s my question: is there any patch to help me out and solve this problem? Here''s a short description about my equipment: *fedora 18*, kernel 3.6-10 rebuilt with xen-kernel features (instead of kernel modules), *xen-unstable*rev *26667*, *saphire HD 7950 11196-16-20G*! Thanks a lot, ** <http://www.guilhermesuzuki.com>*Guilherme Suzuki* Consultor em TI para projetos Microsoft *http://www.guilhermesuzuki.com* 11 - 992360535 11 - 20990757 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi, ehm, I may be missing something, but what exactly is your problem? Or better phrased: Do you have any functional problems like BSODs or something? Also, what distro and kernel are you using? 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>:> Hi, everyone. I''m Guilherme Suzuki (brazillian, by the way) and really > interested in xen-vga-passthru. > > Lately, I bought a brand new Saphire HD 7950 (OC Boost) because I saw in a > wiki somewhere that users have been able to passthru these VGA devices to > domU (win7, win-xp and so on). > > But, after I installed it, I executed lspci -vv to check if FLR in DevCap > was present (which it''s not). > > I''ve managed, though, to put my virtual machine to work out with the HD 7950 > as a secondary device. Sometimes, I have to reboot dom0 to make things work. > > So, here''s my question: is there any patch to help me out and solve this > problem? > > Here''s a short description about my equipment: fedora 18, kernel 3.6-10 > rebuilt with xen-kernel features (instead of kernel modules), xen-unstable > rev 26667, saphire HD 7950 11196-16-20G! > > Thanks a lot, > > Guilherme Suzuki > Consultor em TI para projetos Microsoft > http://www.guilhermesuzuki.com > 11 - 992360535 > 11 - 20990757 > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Hey matthias, nice to meet you, buddy. My problem: sometimes I have to reboot the dom0 (lame) to see VGA passthru work properly. On Mar 4, 2013 1:10 PM, "Matthias" <matthias.kannenberg@googlemail.com> wrote: Hi, ehm, I may be missing something, but what exactly is your problem? Or better phrased: Do you have any functional problems like BSODs or something? Also, what distro and kernel are you using? 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>:> Hi, everyone. I''m Guilherme Suzuki (brazillian, by the way) and really > interested in xen-vga-pas... > _______________________________________________ > 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 kernel version: 3.6-10 and fedora 18 On Mar 4, 2013 1:14 PM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: Hey matthias, nice to meet you, buddy. My problem: sometimes I have to reboot the dom0 (lame) to see VGA passthru work properly.> > On Mar 4, 2013 1:10 PM, "Matthias" <matthias.kannenberg@googlemail.com>wrote:> > Hi, > > ehm,...> > > Hi, everyone. I''m Guilherme Suzuki (brazillian, by the way) and really > interested in xen-vga-pas...> > > _______________________________________________ > > Xen-users mailing list > > Xen-users@list..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi there, I fear you have to be a bit more specific because with only that information, this could be a lot.. But alright, let''s start at the beginning: I assume you installed your dom0, installed your windows domU via the vnc vga, then installed latest catalyst drivers and at this point vga passthrough should work.. So now let''s assume you have a freshly booted dom0 and try to start your domU. Does vga passthrough works every time on a freshly booted dom0? Lets further assume it have worked the first time.. does it always does not work when booting a second time? What in general happens when you say vga passthrough doesn''t work? Do you get a BSOD? or do you get your graphic output on the vnc vga and your main vga has a error 14 or error 43 in device manager? Also, next to distro and kernel information, your domU config would be interesting (especially the acpi, api, pci_whatever parts).. 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>:> Hey matthias, nice to meet you, buddy. > > My problem: sometimes I have to reboot the dom0 (lame) to see VGA passthru > work properly. > > On Mar 4, 2013 1:10 PM, "Matthias" <matthias.kannenberg@googlemail.com> > wrote: > > Hi, > > ehm, I may be missing something, but what exactly is your problem? Or > better phrased: Do you have any functional problems like BSODs or > something? > > Also, what distro and kernel are you using? > > 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>: > >> Hi, everyone. I''m Guilherme Suzuki (brazillian, by the way) and really >> interested in xen-vga-pas... > >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users
Alright! First question: yes, it does work everytime I start the dom0 with my HD 7950 freshly booted as the secondary VGA (it never worked as primary though). Using windows 7 ultimate 64bits, after rebooting due to windows update, the VGA won''t work (only if I reboot dom0 as I said). Reaching the VM with VNC, the cirrus device seems to be okay, the radeon device tells me it co Using Windows XP sp3 I managed to reboot the VM several times and everything worked. On Mar 4, 2013 1:27 PM, "Matthias" <matthias.kannenberg@googlemail.com> wrote: Hi there, I fear you have to be a bit more specific because with only that information, this could be a lot.. But alright, let''s start at the beginning: I assume you installed your dom0, installed your windows domU via the vnc vga, then installed latest catalyst drivers and at this point vga passthrough should work.. So now let''s assume you have a freshly booted dom0 and try to start your domU. Does vga passthrough works every time on a freshly booted dom0? Lets further assume it have worked the first time.. does it always does not work when booting a second time? What in general happens when you say vga passthrough doesn''t work? Do you get a BSOD? or do you get your graphic output on the vnc vga and your main vga has a error 14 or error 43 in device manager? Also, next to distro and kernel information, your domU config would be interesting (especially the acpi, api, pci_whatever parts).. 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>:> Hey matthias, nice to meet you, buddy. > > My problem: sometimes I have to reboot the dom0 (lame) ..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Sorry (hit send). So, the radeon device tells it couldnt start itself (code 10) and cirrus device take over. On Mar 4, 2013 1:37 PM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: Alright! First question: yes, it does work everytime I start the dom0 with my HD 7950 freshly booted as the secondary VGA (it never worked as primary though). Using windows 7 ultimate 64bits, after rebooting due to windows update, the VGA won''t work (only if I reboot dom0 as I said). Reaching the VM with VNC, the cirrus device seems to be okay, the radeon device tells me it co Using Windows XP sp3 I managed to reboot the VM several times and everything worked.> > On Mar 4, 2013 1:27 PM, "Matthias" <matthias.kannenberg@googlemail.com>wrote:> > Hi there, >...> > > Hey matthias, nice to meet you, buddy. > > > My problem: sometimes I have to reboot the dom0 (lame) ..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi, good news, since you said your winxp was able to boot with vga passthrough just fine, your FLR seems to work fine and this might ''only'' be a driver-related problem. What you can do is deinstall your catalyst drivers. After rebooting, Win7 will fallback on a windows-standard driver for the vga but when it correctly says the vga name (like ATI Radeion HD whatever Series), it actually is falling back to an older catalyst version which is shipped per default with windows. I have found this much more stable on reboots then the newest driver. Also, deinstall Catalyst / Vision control center and at best everything the catalyst installer lets you deinstall. If vga passthrough works without all the drivers and you really want the latest and greatest catalyst, i recommend not using the latest 13-1 because it creates a similar behavior you mentioned on my machine. But catalyst 12-10 seems to work fine, so i would advice you trying that one. If it still doesn''t work with deinstalled drivers, we can try a patch i''m currently testing.. But this the patch is somewhat complicated to install, let''s stick with the simple things for the moment. Also, your domU config still would be of help ruling out some misconfiguration there.. 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>:> Sorry (hit send). > > So, the radeon device tells it couldnt start itself (code 10) and cirrus > device take over. > > On Mar 4, 2013 1:37 PM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: > > Alright! > > First question: yes, it does work everytime I start the dom0 with my HD 7950 > freshly booted as the secondary VGA (it never worked as primary though). > > Using windows 7 ultimate 64bits, after rebooting due to windows update, the > VGA won''t work (only if I reboot dom0 as I said). Reaching the VM with VNC, > the cirrus device seems to be okay, the radeon device tells me it co > > Using Windows XP sp3 I managed to reboot the VM several times and everything > worked. > > >> >> On Mar 4, 2013 1:27 PM, "Matthias" <matthias.kannenberg@googlemail.com> >> wrote: >> >> Hi there, >> > ... > >> >> > Hey matthias, nice to meet you, buddy. >> > > >> My problem: sometimes I have to reboot the dom0 (lame) ...
Alright! I''m gonna try catalyst 12-10 (after deinstalling and checking if the passthru works rebooting and so on). I''ll send my domU config as soon as I get home. One more question: does it matter if I use intel onboard graphics with the dom0 and xen-pciback(radeon device pci)? Cause that would be the reason primary VGA passthru did not work... Thx, xen guys are awesome! =D On Mar 4, 2013 2:07 PM, "Matthias" <matthias.kannenberg@googlemail.com> wrote: Hi, good news, since you said your winxp was able to boot with vga passthrough just fine, your FLR seems to work fine and this might ''only'' be a driver-related problem. What you can do is deinstall your catalyst drivers. After rebooting, Win7 will fallback on a windows-standard driver for the vga but when it correctly says the vga name (like ATI Radeion HD whatever Series), it actually is falling back to an older catalyst version which is shipped per default with windows. I have found this much more stable on reboots then the newest driver. Also, deinstall Catalyst / Vision control center and at best everything the catalyst installer lets you deinstall. If vga passthrough works without all the drivers and you really want the latest and greatest catalyst, i recommend not using the latest 13-1 because it creates a similar behavior you mentioned on my machine. But catalyst 12-10 seems to work fine, so i would advice you trying that one. If it still doesn''t work with deinstalled drivers, we can try a patch i''m currently testing.. But this the patch is somewhat complicated to install, let''s stick with the simple things for the moment. Also, your domU config still would be of help ruling out some misconfiguration there.. 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>:> Sorry (hit send). > > So, the radeon device tells it couldnt start itself (code 10) and cirrus > d..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Matthias, hi! I''ve tried Catalyst 12.10 and even 12.1, but xen behavior kept the same on and on (*VGA passthru worked only as secondary device and dom0 freshly rebooted*). As requested, I''m sending you the hvm configuration files from windows-xp and windows-7, my lspci -vv, uname and the kernel configuration file. Do you have any idea how I can make this work? 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>> Alright! > > I''m gonna try catalyst 12-10 (after deinstalling and checking if the > passthru works rebooting and so on). > > I''ll send my domU config as soon as I get home. > > One more question: does it matter if I use intel onboard graphics with the > dom0 and xen-pciback(radeon device pci)? Cause that would be the reason > primary VGA passthru did not work... > > Thx, xen guys are awesome! =D > > On Mar 4, 2013 2:07 PM, "Matthias" <matthias.kannenberg@googlemail.com> > wrote: > > Hi, > > good news, since you said your winxp was able to boot with vga > passthrough just fine, your FLR seems to work fine and this might > ''only'' be a driver-related problem. > > What you can do is deinstall your catalyst drivers. After rebooting, > Win7 will fallback on a windows-standard driver for the vga but when > it correctly says the vga name (like ATI Radeion HD whatever Series), > it actually is falling back to an older catalyst version which is > shipped per default with windows. I have found this much more stable > on reboots then the newest driver. Also, deinstall Catalyst / Vision > control center and at best everything the catalyst installer lets you > deinstall. > > If vga passthrough works without all the drivers and you really want > the latest and greatest catalyst, i recommend not using the latest > 13-1 because it creates a similar behavior you mentioned on my > machine. But catalyst 12-10 seems to work fine, so i would advice you > trying that one. > > > If it still doesn''t work with deinstalled drivers, we can try a patch > i''m currently testing.. But this the patch is somewhat complicated to > install, let''s stick with the simple things for the moment. > > Also, your domU config still would be of help ruling out some > misconfiguration there.. > > > > 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>: > > > Sorry (hit send). > > > > So, the radeon device tells it couldnt start itself (code 10) and cirrus > > d... > >-- Grato, ** <http://www.guilhermesuzuki.com>*Guilherme Suzuki* Consultor em TI para projetos Microsoft *http://www.guilhermesuzuki.com* 11 - 992360535 11 - 20990757 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hello Guilherme, was following your exchange and wanted to see how this turned out. Secondary Passthrough works with AMD, but for primary you need to apply custom patches. There is another email chain circling the mailing list with links to some fresh patches. As Matthias mentioned, passthrough is working, but I am quite certain FLR is interfering which has led to driver related BSoD''s. My understanding is that FLR allows a virtual machine to issue a reset to a piece of hardware, and without it that device''s state cannot be cleared. Consumer cards do not come with FLR, and no patch for this is available. What this means is that when you first boot your virtual machine, the card is initialized and performs just fine. When you shut down Windows 7 or XP and start either one back up you may encounter a BSoD. This is because the card is being initialized a second time. For me and many others rebooting has led to degraded performance instead of a BSoD, which can be fixed by manually ejecting the card with the "safely eject media" tool. However experiences vary. I am using an AMD Radeon HD 6870 with 12.10 catalyst drivers, and it is working just fine. I have had this working in both Windows 7 and Windows 8, but I have no experience with XP. Keeping in mind that your experience may vary, here is my route to success: First, backup your Windows HVM before attempting to pass any PCI devices. Make certain that Dom0 has been freshly booted to ensure that the PCI card only initializes once. The leading cause to trouble from my experience is passing the card more than once at any point during the installation, which leads to a BSoD during the process OR a badly damaged install which can range from BSoD on reboot only to gradual buggy experiences and BSoD''s on first boot. Prior to passing the PCI card to Windows 7 or Windows 8 be sure to turn off all automatic driver installation settings (there are more than one). If using Windows 8 do not add the card to the configuration, instead let it boot and then use `xl pci-attach`, since Windows 8 will attempt to install a driver at boot time and reboot without ever displaying anything on screen. Once the installation has completed it may ask you to reboot, instead shut down Windows and reboot Dom0 then start Windows again. This avoids any post-install processes from attempting to communicate with the card in its buggy (previously initialized) state, which could muck up the installation. I have used the above rules successfully more than a dozen times now, and never once had a BSoD when I followed them. Finally, the reason for the backup at the beginning is that anytime I failed to follow the above rules, I was not able to fix the problem by removing and installing the drivers again. In fact, that never once worked and I wasted a few days trying several times without success. So in short, if you fail don''t bother removing the drivers and trying again, instead restore from an image backup of the machine that has never once seen your PCI device. I hope this information helps. Sincerely, Casey DeLorme On Mon, Mar 4, 2013 at 9:43 PM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> Matthias, hi! > > I''ve tried Catalyst 12.10 and even 12.1, but xen behavior kept the same on > and on (*VGA passthru worked only as secondary device and dom0 freshly > rebooted*). As requested, I''m sending you the hvm configuration files > from windows-xp and windows-7, my lspci -vv, uname and the kernel > configuration file. > > Do you have any idea how I can make this work? > > > > 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com> > >> Alright! >> >> I''m gonna try catalyst 12-10 (after deinstalling and checking if the >> passthru works rebooting and so on). >> >> I''ll send my domU config as soon as I get home. >> >> One more question: does it matter if I use intel onboard graphics with >> the dom0 and xen-pciback(radeon device pci)? Cause that would be the reason >> primary VGA passthru did not work... >> >> Thx, xen guys are awesome! =D >> >> On Mar 4, 2013 2:07 PM, "Matthias" <matthias.kannenberg@googlemail.com> >> wrote: >> >> Hi, >> >> good news, since you said your winxp was able to boot with vga >> passthrough just fine, your FLR seems to work fine and this might >> ''only'' be a driver-related problem. >> >> What you can do is deinstall your catalyst drivers. After rebooting, >> Win7 will fallback on a windows-standard driver for the vga but when >> it correctly says the vga name (like ATI Radeion HD whatever Series), >> it actually is falling back to an older catalyst version which is >> shipped per default with windows. I have found this much more stable >> on reboots then the newest driver. Also, deinstall Catalyst / Vision >> control center and at best everything the catalyst installer lets you >> deinstall. >> >> If vga passthrough works without all the drivers and you really want >> the latest and greatest catalyst, i recommend not using the latest >> 13-1 because it creates a similar behavior you mentioned on my >> machine. But catalyst 12-10 seems to work fine, so i would advice you >> trying that one. >> >> >> If it still doesn''t work with deinstalled drivers, we can try a patch >> i''m currently testing.. But this the patch is somewhat complicated to >> install, let''s stick with the simple things for the moment. >> >> Also, your domU config still would be of help ruling out some >> misconfiguration there.. >> >> >> >> 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com>: >> >> > Sorry (hit send). >> > >> > So, the radeon device tells it couldnt start itself (code 10) and cirrus >> > d... >> >> > > > -- > Grato, > > ** <http://www.guilhermesuzuki.com>*Guilherme Suzuki* > Consultor em TI para projetos Microsoft > *http://www.guilhermesuzuki.com* > 11 - 992360535 > 11 - 20990757 > > > > _______________________________________________ > 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
A few things I can add... My card is a Sapphire Radeon HD 6770. And I''m currently using catalyst version 12-10. I *never* got windows xp to use the passed through gfx card unless I set "stdvga=1" (which means to replace the cirrus logic card (that works in winxp) with another (that doesn''t work in xp), so it then uses the secondary gpu like I wanted. Win7 and 8 work without this. (and FYI xp is the worst performer by far, maybe from a xen bug that only affects AMD cpus, and 4.2.x is unusably slow in xp, definitely a bug affecting just AMD) I very rarely get any problem booting and getting graphics to work, and never on the first boot. Every time there is an error, it is from a "restart" (such as a windows update) instead of a "shutdown" and "start", like Casey described. However, when this happens, I can simply "xm destroy ..." and "xm create ..." again, and it works 100%. I have never needed to reboot dom0 to start a vm, except: 1. to get my USB IRQ to work again in dom0 (without this, my keyboard and mouse are laggy and miss keystrokes). I have passed through a USB controller that lacks FLR, so if the vm dies incorrectly [not a shutdown], dom0 broadcasts that it is disabling an irq. If I start the domu again, the usb works fine in domu, but never dom0 until reboot. (I''ve only caused this with crashing domu''s from kernel oopses from #2, and with gplpv network drivers which never seem to work right for me) 2. testing broken kernels (3.7-rc2, etc. with broken network) (in this case, every domu I try to create after the first problem starts with a blank screen, and vnc usually is blank or just says "parallell0" instead of a console screen) And last, contradictory to what the others said, win7 gfx passthrough never worked for me without installing the catalyst drivers first in winxp or win7. Win8 worked though, one time even in the installer (depends on whether the monitor is plugged in at the right time I think). On 2013-03-05 05:25, Casey DeLorme wrote:> Hello Guilherme, was following your exchange and wanted to see how > this turned out. > > Secondary Passthrough works with AMD, but for primary you need to > apply custom patches. There is another email chain circling the > mailing list with links to some fresh patches. > > As Matthias mentioned, passthrough is working, but I am quite certain > FLR is interfering which has led to driver related BSoD''s. > > My understanding is that FLR allows a virtual machine to issue a reset > to a piece of hardware, and without it that device''s state cannot be > cleared. Consumer cards do not come with FLR, and no patch for this > is available. > > What this means is that when you first boot your virtual machine, the > card is initialized and performs just fine. When you shut down > Windows 7 or XP and start either one back up you may encounter a BSoD. > This is because the card is being initialized a second time. > > For me and many others rebooting has led to degraded performance > instead of a BSoD, which can be fixed by manually ejecting the card > with the "safely eject media" tool. However experiences vary. > > > I am using an AMD Radeon HD 6870 with 12.10 catalyst drivers, and it > is working just fine. I have had this working in both Windows 7 and > Windows 8, but I have no experience with XP. > > Keeping in mind that your experience may vary, here is my route to > success: > > First, backup your Windows HVM before attempting to pass any PCI devices. > > Make certain that Dom0 has been freshly booted to ensure that the PCI > card only initializes once. The leading cause to trouble from my > experience is passing the card more than once at any point during the > installation, which leads to a BSoD during the process OR a badly > damaged install which can range from BSoD on reboot only to gradual > buggy experiences and BSoD''s on first boot. > > Prior to passing the PCI card to Windows 7 or Windows 8 be sure to > turn off all automatic driver installation settings (there are more > than one). If using Windows 8 do not add the card to the > configuration, instead let it boot and then use `xl pci-attach`, since > Windows 8 will attempt to install a driver at boot time and reboot > without ever displaying anything on screen. > > Once the installation has completed it may ask you to reboot, instead > shut down Windows and reboot Dom0 then start Windows again. This > avoids any post-install processes from attempting to communicate with > the card in its buggy (previously initialized) state, which could muck > up the installation. > > I have used the above rules successfully more than a dozen times now, > and never once had a BSoD when I followed them. > > Finally, the reason for the backup at the beginning is that anytime I > failed to follow the above rules, I was not able to fix the problem by > removing and installing the drivers again. In fact, that never once > worked and I wasted a few days trying several times without success. > So in short, if you fail don''t bother removing the drivers and trying > again, instead restore from an image backup of the machine that has > never once seen your PCI device. > > > I hope this information helps. > > Sincerely, > > Casey DeLorme > > > On Mon, Mar 4, 2013 at 9:43 PM, Guilherme Suzuki <suzuki.gui@gmail.com > <mailto:suzuki.gui@gmail.com>> wrote: > > Matthias, hi! > > I''ve tried Catalyst 12.10 and even 12.1, but xen behavior kept the > same on and on (_VGA passthru worked only as secondary device and > dom0 freshly rebooted_). As requested, I''m sending you the hvm > configuration files from windows-xp and windows-7, my lspci -vv, > uname and the kernel configuration file. > > Do you have any idea how I can make this work? > > > > 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com > <mailto:suzuki.gui@gmail.com>> > > Alright! > > I''m gonna try catalyst 12-10 (after deinstalling and checking > if the passthru works rebooting and so on). > > I''ll send my domU config as soon as I get home. > > One more question: does it matter if I use intel onboard > graphics with the dom0 and xen-pciback(radeon device pci)? > Cause that would be the reason primary VGA passthru did not > work... > > Thx, xen guys are awesome! =D > >> On Mar 4, 2013 2:07 PM, "Matthias" >> <matthias.kannenberg@googlemail.com >> <mailto:matthias.kannenberg@googlemail.com>> wrote: >> >> Hi, >> >> good news, since you said your winxp was able to boot with vga >> passthrough just fine, your FLR seems to work fine and this might >> ''only'' be a driver-related problem. >> >> What you can do is deinstall your catalyst drivers. After >> rebooting, >> Win7 will fallback on a windows-standard driver for the vga >> but when >> it correctly says the vga name (like ATI Radeion HD whatever >> Series), >> it actually is falling back to an older catalyst version which is >> shipped per default with windows. I have found this much more >> stable >> on reboots then the newest driver. Also, deinstall Catalyst / >> Vision >> control center and at best everything the catalyst installer >> lets you >> deinstall. >> >> If vga passthrough works without all the drivers and you >> really want >> the latest and greatest catalyst, i recommend not using the >> latest >> 13-1 because it creates a similar behavior you mentioned on my >> machine. But catalyst 12-10 seems to work fine, so i would >> advice you >> trying that one. >> >> >> If it still doesn''t work with deinstalled drivers, we can try >> a patch >> i''m currently testing.. But this the patch is somewhat >> complicated to >> install, let''s stick with the simple things for the moment. >> >> Also, your domU config still would be of help ruling out some >> misconfiguration there.. >> >> >> >> 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com >> <mailto:suzuki.gui@gmail.com>>: >> > Sorry (hit send). >> > >> > So, the radeon device tells it couldnt start itself (code >> 10) and cirrus >> > d... > > > > > -- > Grato, > > *Guilherme Suzuki* > Consultor em TI para projetos Microsoft > *http://www.guilhermesuzuki.com* > 11 - 992360535 > 11 - 20990757 > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org <mailto: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-- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
grr Thunderbird doesn''t cc everyone when I hit "reply list", sorry for the double message if you got 2. On 2013-03-05 09:35, Peter Maloney wrote:> A few things I can add... > > My card is a Sapphire Radeon HD 6770. And I''m currently using catalyst > version 12-10. > > I *never* got windows xp to use the passed through gfx card unless I > set "stdvga=1" (which means to replace the cirrus logic card (that > works in winxp) with another (that doesn''t work in xp), so it then > uses the secondary gpu like I wanted. Win7 and 8 work without this. > (and FYI xp is the worst performer by far, maybe from a xen bug that > only affects AMD cpus, and 4.2.x is unusably slow in xp, definitely a > bug affecting just AMD) > > I very rarely get any problem booting and getting graphics to work, > and never on the first boot. Every time there is an error, it is from > a "restart" (such as a windows update) instead of a "shutdown" and > "start", like Casey described. However, when this happens, I can > simply "xm destroy ..." and "xm create ..." again, and it works 100%. > > I have never needed to reboot dom0 to start a vm, except: > 1. to get my USB IRQ to work again in dom0 (without this, my keyboard > and mouse are laggy and miss keystrokes). I have passed through a USB > controller that lacks FLR, so if the vm dies incorrectly [not a > shutdown], dom0 broadcasts that it is disabling an irq. If I start the > domu again, the usb works fine in domu, but never dom0 until reboot. > (I''ve only caused this with crashing domu''s from kernel oopses from > #2, and with gplpv network drivers which never seem to work right for me) > 2. testing broken kernels (3.7-rc2, etc. with broken network) (in this > case, every domu I try to create after the first problem starts with a > blank screen, and vnc usually is blank or just says "parallell0" > instead of a console screen) > > And last, contradictory to what the others said, win7 gfx passthrough > never worked for me without installing the catalyst drivers first in > winxp or win7. Win8 worked though, one time even in the installer > (depends on whether the monitor is plugged in at the right time I think). > > > > On 2013-03-05 05:25, Casey DeLorme wrote: >> Hello Guilherme, was following your exchange and wanted to see how >> this turned out. >> >> Secondary Passthrough works with AMD, but for primary you need to >> apply custom patches. There is another email chain circling the >> mailing list with links to some fresh patches. >> >> As Matthias mentioned, passthrough is working, but I am quite certain >> FLR is interfering which has led to driver related BSoD''s. >> >> My understanding is that FLR allows a virtual machine to issue a >> reset to a piece of hardware, and without it that device''s state >> cannot be cleared. Consumer cards do not come with FLR, and no patch >> for this is available. >> >> What this means is that when you first boot your virtual machine, the >> card is initialized and performs just fine. When you shut down >> Windows 7 or XP and start either one back up you may encounter a >> BSoD. This is because the card is being initialized a second time. >> >> For me and many others rebooting has led to degraded performance >> instead of a BSoD, which can be fixed by manually ejecting the card >> with the "safely eject media" tool. However experiences vary. >> >> >> I am using an AMD Radeon HD 6870 with 12.10 catalyst drivers, and it >> is working just fine. I have had this working in both Windows 7 and >> Windows 8, but I have no experience with XP. >> >> Keeping in mind that your experience may vary, here is my route to >> success: >> >> First, backup your Windows HVM before attempting to pass any PCI devices. >> >> Make certain that Dom0 has been freshly booted to ensure that the PCI >> card only initializes once. The leading cause to trouble from my >> experience is passing the card more than once at any point during the >> installation, which leads to a BSoD during the process OR a badly >> damaged install which can range from BSoD on reboot only to gradual >> buggy experiences and BSoD''s on first boot. >> >> Prior to passing the PCI card to Windows 7 or Windows 8 be sure to >> turn off all automatic driver installation settings (there are more >> than one). If using Windows 8 do not add the card to the >> configuration, instead let it boot and then use `xl pci-attach`, >> since Windows 8 will attempt to install a driver at boot time and >> reboot without ever displaying anything on screen. >> >> Once the installation has completed it may ask you to reboot, instead >> shut down Windows and reboot Dom0 then start Windows again. This >> avoids any post-install processes from attempting to communicate with >> the card in its buggy (previously initialized) state, which could >> muck up the installation. >> >> I have used the above rules successfully more than a dozen times now, >> and never once had a BSoD when I followed them. >> >> Finally, the reason for the backup at the beginning is that anytime I >> failed to follow the above rules, I was not able to fix the problem >> by removing and installing the drivers again. In fact, that never >> once worked and I wasted a few days trying several times without >> success. So in short, if you fail don''t bother removing the drivers >> and trying again, instead restore from an image backup of the machine >> that has never once seen your PCI device. >> >> >> I hope this information helps. >> >> Sincerely, >> >> Casey DeLorme >> >> >> On Mon, Mar 4, 2013 at 9:43 PM, Guilherme Suzuki >> <suzuki.gui@gmail.com <mailto:suzuki.gui@gmail.com>> wrote: >> >> Matthias, hi! >> >> I''ve tried Catalyst 12.10 and even 12.1, but xen behavior kept >> the same on and on (_VGA passthru worked only as secondary device >> and dom0 freshly rebooted_). As requested, I''m sending you the >> hvm configuration files from windows-xp and windows-7, my lspci >> -vv, uname and the kernel configuration file. >> >> Do you have any idea how I can make this work? >> >> >> >> 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com >> <mailto:suzuki.gui@gmail.com>> >> >> Alright! >> >> I''m gonna try catalyst 12-10 (after deinstalling and checking >> if the passthru works rebooting and so on). >> >> I''ll send my domU config as soon as I get home. >> >> One more question: does it matter if I use intel onboard >> graphics with the dom0 and xen-pciback(radeon device pci)? >> Cause that would be the reason primary VGA passthru did not >> work... >> >> Thx, xen guys are awesome! =D >> >>> On Mar 4, 2013 2:07 PM, "Matthias" >>> <matthias.kannenberg@googlemail.com >>> <mailto:matthias.kannenberg@googlemail.com>> wrote: >>> >>> Hi, >>> >>> good news, since you said your winxp was able to boot with vga >>> passthrough just fine, your FLR seems to work fine and this >>> might >>> ''only'' be a driver-related problem. >>> >>> What you can do is deinstall your catalyst drivers. After >>> rebooting, >>> Win7 will fallback on a windows-standard driver for the vga >>> but when >>> it correctly says the vga name (like ATI Radeion HD whatever >>> Series), >>> it actually is falling back to an older catalyst version >>> which is >>> shipped per default with windows. I have found this much >>> more stable >>> on reboots then the newest driver. Also, deinstall Catalyst >>> / Vision >>> control center and at best everything the catalyst installer >>> lets you >>> deinstall. >>> >>> If vga passthrough works without all the drivers and you >>> really want >>> the latest and greatest catalyst, i recommend not using the >>> latest >>> 13-1 because it creates a similar behavior you mentioned on my >>> machine. But catalyst 12-10 seems to work fine, so i would >>> advice you >>> trying that one. >>> >>> >>> If it still doesn''t work with deinstalled drivers, we can >>> try a patch >>> i''m currently testing.. But this the patch is somewhat >>> complicated to >>> install, let''s stick with the simple things for the moment. >>> >>> Also, your domU config still would be of help ruling out some >>> misconfiguration there.. >>> >>> >>> >>> 2013/3/4 Guilherme Suzuki <suzuki.gui@gmail.com >>> <mailto:suzuki.gui@gmail.com>>: >>> > Sorry (hit send). >>> > >>> > So, the radeon device tells it couldnt start itself (code >>> 10) and cirrus >>> > d... >> >> >> >> >> -- >> Grato, >> >> *Guilherme Suzuki* >> Consultor em TI para projetos Microsoft >> *http://www.guilhermesuzuki.com* >> 11 - 992360535 >> 11 - 20990757 >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org <mailto: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 > > > -- > > -------------------------------------------- > Peter Maloney > Brockmann Consult > Max-Planck-Str. 2 > 21502 Geesthacht > Germany > Tel: +49 4152 889 300 > Fax: +49 4152 889 333 > E-mail: peter.maloney@brockmann-consult.de > Internet: http://www.brockmann-consult.de > ---------------------------------------------- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Casey DeLorme, I noticed what you have said... it works for me only for the first time (dom0 just booted). Peter Maloney, I did not know that xm destroy and xm create could make things work again! But it got me thinking, cause I''m passing thru a USB controller FLR disabled. Let me try this: I''ll prepare another installation with fedora 18, install xen from RPM (since I downloaded the unstable source code, rev 26667), and start over without passingthru everything that I wanted at once (just the VGA) to see what happens. I''m gonna do this, installing from RPM, based on what the wiki says (secondary VGA passthru will work out-of-box). I''ll let you guys know... On Mar 5, 2013 5:39 AM, "Peter Maloney" <peter.maloney@brockmann-consult.de> wrote: grr Thunderbird doesn''t cc everyone when I hit "reply list", sorry for the double message if you got 2. On 2013-03-05 09:35, Peter Maloney wrote: A few things I can add... My card is a Sapphire Radeon HD 6770. And I''m currently using catalyst version 12-10. I *never* got windows xp to use the passed through gfx card unless I set "stdvga=1" (which means to replace the cirrus logic card (that works in winxp) with another (that doesn''t work in xp), so it then uses the secondary gpu like I wanted. Win7 and 8 work without this. (and FYI xp is the worst performer by far, maybe from a xen bug that only affects AMD cpus, and 4.2.x is unusably slow in xp, definitely a bug affecting just AMD) I very rarely get any problem booting and getting graphics to work, and never on the first boot. Every time there is an error, it is from a "restart" (such as a windows update) instead of a "shutdown" and "start", like Casey described. However, when this happens, I can simply "xm destroy ..." and "xm create ..." again, and it works 100%. I have never needed to reboot dom0 to start a vm, except: 1. to get my USB IRQ to work again in dom0 (without this, my keyboard and mouse are laggy and miss keystrokes). I have passed through a USB controller that lacks FLR, so if the vm dies incorrectly [not a shutdown], dom0 broadcasts that it is disabling an irq. If I start the domu again, the usb works fine in domu, but never dom0 until reboot. (I''ve only caused this with crashing domu''s from kernel oopses from #2, and with gplpv network drivers which never seem to work right for me) 2. testing broken kernels (3.7-rc2, etc. with broken network) (in this case, every domu I try to create after the first problem starts with a blank screen, and vnc usually is blank or just says "parallell0" instead of a console screen) And last, contradictory to what the others said, win7 gfx passthrough never worked for me without installing the catalyst drivers first in winxp or win7. Win8 worked though, one time even in the installer (depends on whether the monitor is plugged in at the right time I think).> > > > On 2013-03-05 05:25, Casey DeLorme wrote:>> >> Hello Guilherme, was following your exchange and wanted to see how thisturned out.>> >> Seco...-- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Ow, by the way, thanks guys for the support! Who tells that linux guys can''t get help? Have a good day... :) On Mar 5, 2013 8:39 AM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: Casey DeLorme, I noticed what you have said... it works for me only for the first time (dom0 just booted). Peter Maloney, I did not know that xm destroy and xm create could make things work again! But it got me thinking, cause I''m passing thru a USB controller FLR disabled. Let me try this: I''ll prepare another installation with fedora 18, install xen from RPM (since I downloaded the unstable source code, rev 26667), and start over without passingthru everything that I wanted at once (just the VGA) to see what happens. I''m gonna do this, installing from RPM, based on what the wiki says (secondary VGA passthru will work out-of-box). I''ll let you guys know... On Mar 5, 2013 5:39 AM, "Peter Maloney" <peter.maloney@brockmann-consult.de> wrote: grr Thunderbird doesn''t cc everyone when I hit "reply list", sorry for the double message if you got...> > A few things I can add... > > My card is a Sapphire Radeon HD 6770. And I''m currently using cata...> > >> > >> Hello Guilherme, was following your exchange and wanted to see howthis turned out.> >... >> Seco...> > -- > > -------------------------------------------- > Peter Maloney > Brockmann Consult > Max-...-- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I reinstall Fedora 18, kernel 3.6-10 with embedded xen (not as kernel modules) and brought Xen from RPM source (version 4.21) I had the same results everyone''s has achieved with consumer cards (it only works with dom0 freshly booted) This time, though, I tried primary VGA passthru from the intel onboard, which does have FLR. And it worked smoothly! Doing a little research, FLR is not the unique way of refreshing a device (theres d3d0, bus and a few others). I''ll send an email to AMD and see if they can help us resetting theirs VGAs without rebooting the computer everytime. Have a nice day On Mar 5, 2013 8:45 AM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: Ow, by the way, thanks guys for the support! Who tells that linux guys can''t get help? Have a good day... :) On Mar 5, 2013 8:39 AM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: Casey DeLorme, I noticed... On Mar 5, 2013 5:39 AM, "Peter Maloney" <peter.maloney@brockmann-consult.de> wrote: grr Thunderbird doesn''t cc everyone when I hit "reply list", sorry for the double message if you got...> > > > > A few things I can add... > > > My card is a Sapphire Radeon HD 6770. And I''m currently using cata...> > > > > > >> > > >> Hello Guilherme, was following your exchange and wanted to see howthis turne...> >... >> Seco...> > > > > > -- > > > > -------------------------------------------- > > Peter Maloney > > Brockman... > Max-...-- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I haven''t read every message in this string, so forgive me if I''m missing something. But just a comment with regard to what was previously stated by another: "I recommend not using the latest 13-1 because it creates a similar behavior you mentioned on my machine. But catalyst 12-10 seems to work fine, so i would advice you trying that one." Although I''ve read that others have had success with Catalyst 12.10, in my case, that driver was not stable for GPU passthrough with an AMD Radeon HD 6670 and a Windows 7 guest. However, *Catalyst 12.3* on a clean install of Windows 7 (on which no other version of Catalyst has ever been installed) works well for me. (I''ve read that removal process for Catalyst isn''t complete, so a clean install is better.) Hope the above helps. GizmoChicken On Wed, Mar 6, 2013 at 6:22 AM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> I reinstall Fedora 18, kernel 3.6-10 with embedded xen (not as kernel > modules) and brought Xen from RPM source (version 4.21) > > I had the same results everyone''s has achieved with consumer cards (it > only works with dom0 freshly booted) > > This time, though, I tried primary VGA passthru from the intel onboard, > which does have FLR. And it worked smoothly! > > Doing a little research, FLR is not the unique way of refreshing a device > (theres d3d0, bus and a few others). I''ll send an email to AMD and see if > they can help us resetting theirs VGAs without rebooting the computer > everytime. > > Have a nice day > > On Mar 5, 2013 8:45 AM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: > > Ow, by the way, thanks guys for the support! > > Who tells that linux guys can''t get help? Have a good day... :) > > > > On Mar 5, 2013 8:39 AM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: > > Casey DeLorme, I noticed... > > > > > > On Mar 5, 2013 5:39 AM, "Peter Maloney" < > peter.maloney@brockmann-consult.de> wrote: > > grr Thunderbird doesn''t cc everyone when I hit "reply list", sorry for the > double message if you got... > > > > > > > > > > A few things I can add... > > > > > My card is a Sapphire Radeon HD 6770. And I''m currently using cata... > > > > > > > > > > > > >> > > > >> Hello Guilherme, was following your exchange and wanted to see how > this turne... > > >... > > >> Seco... > > > > > > > > > > > > -- > > > > > > -------------------------------------------- > > > Peter Maloney > > > Brockman... > > Max-... > > > > > > > > -- > > -------------------------------------------- > Peter Maloney > Brockmann Consult > Max-Planck-Str... > > > _______________________________________________ > 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
Gizmo, hi! Have you been able to reboot your VM and get everything working fine? On Mar 6, 2013 10:15 AM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: I haven''t read every message in this string, so forgive me if I''m missing something. But just a comment with regard to what was previously stated by another: "I recommend not using the latest 13-1 because it creates a similar behavior you mentioned on my m... Although I''ve read that others have had success with Catalyst 12.10, in my case, that driver was not stable for GPU passthrough with an AMD Radeon HD 6670 and a Windows 7 guest. However, *Catalyst 12.3* on a clean install of Windows 7 (on which no other version of Catalyst has ever been installed) works well for me. (I''ve read that removal process for Catalyst isn''t complete, so a clean install is better.) Hope the above helps. GizmoChicken On Wed, Mar 6, 2013 at 6:22 AM, Guilherme Suzuki <suzuki.gui@gmail.com> wrote:> > > > I reinstall Fedora 18, kernel 3.6-10 with embedded xen (not as kernel > modules) and brought Xen f... > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org... >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Guilherme, It was a while back when I installed Catalyst 12.03, and I had lots of problems with other Catalyst drivers (including Catalyst 12.10), so maybe I''m forgetting some of the details. But yes, if I remember correctly, Windows 7 Ultimate 64-bit booted up just fine after installing Catalyst 12.03 on a clean system. GizmoChicken On Wed, Mar 6, 2013 at 8:28 AM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> Gizmo, hi! > > Have you been able to reboot your VM and get everything working fine? > > On Mar 6, 2013 10:15 AM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: > > I haven''t read every message in this string, so forgive me if I''m missing > something. But just a comment with regard to what was previously stated by > another: > > > > "I recommend not using the latest 13-1 because it creates a similar > behavior you mentioned on my m... > Although I''ve read that others have had success with Catalyst 12.10, in my > case, that driver was not stable for GPU passthrough with an AMD Radeon HD > 6670 and a Windows 7 guest. > > However, *Catalyst 12.3* on a clean install of Windows 7 (on which no > other version of Catalyst has ever been installed) works well for me. > (I''ve read that removal process for Catalyst isn''t complete, so a clean > install is better.) > > Hope the above helps. > > GizmoChicken > > > > On Wed, Mar 6, 2013 at 6:22 AM, Guilherme Suzuki <suzuki.gui@gmail.com> > wrote: > >> > >> > I reinstall Fedora 18, kernel 3.6-10 with embedded xen (not as kernel >> modules) and brought Xen f... >> >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xen.org... >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hmm I see... cause my major problem right now is rebooting domU with secondary VGA adapter passedthrough. Windows 7 ultimate 64bits N says to me: the device cannot start (code 43). It will only come back alive again if I reboot dom0 as well. Which version of windows are you using? On Mar 6, 2013 1:34 PM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: Guilherme, It was a while back when I installed Catalyst 12.03, and I had lots of problems with other Catalyst drivers (including Catalyst 12.10), so maybe I''m forgetting some of the details. But yes, if I remember correctly, Windows 7 Ultimate 64-bit booted up just fine after installing Catalyst 12.03 on a clean system. GizmoChicken On Wed, Mar 6, 2013 at 8:28 AM, Guilherme Suzuki <suzuki.gui@gmail.com> wrote:> > Gizmo, hi! >... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I used Windows 7 Ultimate 64-bit. Also, here''s a link to one of the tutorials that I followed in part, though I think the tutorial recommends a different driver: http://forums.linuxmint.com/viewtopic.php?f=42&t=112013 But as I said, it has been some time since created that VM. And in fact, I don''t currently use it. Rather, I''m now currently experimenting with GPU passthrough using Windows 7 Ultimate 64-bit VM on an XCP 1.6 host, which offers an easier means for getting everything configured. In that VM, Catalyst 12.3 also works great. If interested in trying XCP 1.6 as a host, here''s a link to its download page: http://xen.org/download/xcp/index_1.6.0.html Note that, if you want to try XCP, you''ll also need to download XenCenter to manage XCP. You can learn more about how to get a free version of XenCenter here: http://citrixxperience.com/2012/02/24/download-and-install-citrix-xencenter-6-0/ GizmoChicken On Wed, Mar 6, 2013 at 11:46 AM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> Hmm I see... cause my major problem right now is rebooting domU with > secondary VGA adapter passedthrough. > > Windows 7 ultimate 64bits N says to me: the device cannot start (code 43). > It will only come back alive again if I reboot dom0 as well. > > Which version of windows are you using? > > On Mar 6, 2013 1:34 PM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: > > Guilherme, > > It was a while back when I installed Catalyst 12.03, and I had lots of > problems with other Catalyst drivers (including Catalyst 12.10), so maybe > I''m forgetting some of the details. But yes, if I remember correctly, > Windows 7 Ultimate 64-bit booted up just fine after installing Catalyst > 12.03 on a clean system. > > GizmoChicken > > > > > > On Wed, Mar 6, 2013 at 8:28 AM, Guilherme Suzuki <suzuki.gui@gmail.com> > wrote: > > > > Gizmo, hi! > > > ... > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Nice to know that! I''ll uninstall Xen easily with yum and try XCP. I''ll let you know how things turned out. On Mar 6, 2013 2:17 PM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: I used Windows 7 Ultimate 64-bit. Also, here''s a link to one of the tutorials that I followed in part, though I think the tutorial recommends a different driver: http://forums.linuxmint.com/viewtopic.php?f=42&t=112013 But as I said, it has been some time since created that VM. And in fact, I don''t currently use it. Rather, I''m now currently experimenting with GPU passthrough using Windows 7 Ultimate 64-bit VM on an XCP 1.6 host, which offers an easier means for getting everything configured. In that VM, Catalyst 12.3 also works great. If interested in trying XCP 1.6 as a host, here''s a link to its download page: http://xen.org/download/xcp/index_1.6.0.html Note that, if you want to try XCP, you''ll also need to download XenCenter to manage XCP. You can learn more about how to get a free version of XenCenter here: http://citrixxperience.com/2012/02/24/download-and-install-citrix-xencenter-6-0/ GizmoChicken On Wed, Mar 6, 2013 at 11:46 AM, Guilherme Suzuki <suzuki.gui@gmail.com> wrote:> > Hmm I see... ..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Can you tell me what kernel version your distro''s running with? On Mar 6, 2013 4:39 PM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: Nice to know that! I''ll uninstall Xen easily with yum and try XCP. I''ll let you know how things turned out.> > On Mar 6, 2013 2:17 PM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: > > I used Windows 7 Ul...> > > > > On Wed, Mar 6, 2013 at 11:46 AM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> > > Hmm I see... ..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Guilherme, Before moving further, let''s verify: You do have IOMMU enabled in your BIOS, correct? If not, you need to enable it to get GPU passthrough to work. Now, back to XCP 1.6... XCP 1.6 is kind of a "black box" approach, in that you won''t be able to simply install it over your current dom0, but instead you must *replace*your current dom0. That said, XCP 1.6 is based on CentOS 5.7 (Linux kernel v2.6.32.43). But be aware that XCP 1.6 won''t give you a graphical desktop on dom0. So if you need a graphical desktop on dom0, XCP 1.6 won''t be a long term solution for you. But given the ease of setting up GPU passthrough with XCP, it could be relatively easy way for you to verify that your system is capable of passthrough. Also, be aware that, although GPU passthrough is pretty simple with XPC 1.6, strangely, *you''ll have to do some digging on how to set up PCI-passthrough so that your mouse/keyboard/device is accessible from a guest VM.* It can be done, but the procedure isn''t well-documented. When (and if) you get XPC 1.6 installed and GPU passthrough working, write back to me, and I''ll try to help with the PCI passthrough. (One thing at a time.) If you must have graphical desktop on dom0, then you have another option, namely installing the *XCP-XAPI toolstack* (which is the toolstack used by XCP 1.6) on a desktop version of Ubuntu. In my case, I have successfully installed the XCP-XAPI toolstack on Ubuntu 12.10 desktop. If you want to try XCP-XAPI toolstack on Ubuntu (I recommend Ubuntu 12.10 desktop if you do), here are two reasonably complete tutorials: http://www.chimos.de/stuff/xen-xcp-ubuntu-manual/xen-xcp-ubuntu-manual.txt http://blog.scottlowe.org/2012/06/28/installing-xcp-xapi-on-ubuntu-server-12-04-lts/ Be aware that installing the XCP-XAPI toolstack on Ubuntu requires lots of hacks and may be a bumpy process. So before you even try, I recommend that you *first* experiment with XCP 1.6 (the "black box" approach) to see if it works with your hardware and if XenCenter fits your needs. Hope the above help. GizmoChicken On Wed, Mar 6, 2013 at 3:06 PM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> Can you tell me what kernel version your distro''s running with? > > On Mar 6, 2013 4:39 PM, "Guilherme Suzuki" <suzuki.gui@gmail.com> wrote: > > Nice to know that! I''ll uninstall Xen easily with yum and try XCP. > > I''ll let you know how things turned out. > > > > > > On Mar 6, 2013 2:17 PM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: > > > > I used Windows 7 Ul... > > > > > > > > > > > > On Wed, Mar 6, 2013 at 11:46 AM, Guilherme Suzuki <suzuki.gui@gmail.com> > wrote: > > > > > Hmm I see... ... > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Gizmo, I''ve gone a little bit further than that. I managed to make things (vga passthru) working, but that only works with freshly booted dom0. On Mar 7, 2013 6:57 AM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: Guilherme, Before moving further, let''s verify: You do have IOMMU enabled in your BIOS, correct? If not, you need to enable it to get GPU passthrough to work. Now, back to XCP 1.6... XCP 1.6 is kind of a "black box" approach, in that you won''t be able to simply install it over your current dom0, but instead you must *replace*your current dom0. That said, XCP 1.6 is based on CentOS 5.7 (Linux kernel v2.6.32.43). But be aware that XCP 1.6 won''t give you a graphical desktop on dom0. So if you need a graphical desktop on dom0, XCP 1.6 won''t be a long term solution for you. But given the ease of setting up GPU passthrough with XCP, it could be relatively easy way for you to verify that your system is capable of passthrough. Also, be aware that, although GPU passthrough is pretty simple with XPC 1.6, strangely, *you''ll have to do some digging on how to set up PCI-passthrough so that your mouse/keyboard/device is accessible from a guest VM.* It can be done, but the procedure isn''t well-documented. When (and if) you get XPC 1.6 installed and GPU passthrough working, write back to me, and I''ll try to help with the PCI passthrough. (One thing at a time.) If you must have graphical desktop on dom0, then you have another option, namely installing the *XCP-XAPI toolstack* (which is the toolstack used by XCP 1.6) on a desktop version of Ubuntu. In my case, I have successfully installed the XCP-XAPI toolstack on Ubuntu 12.10 desktop. If you want to try XCP-XAPI toolstack on Ubuntu (I recommend Ubuntu 12.10 desktop if you do), here are two reasonably complete tutorials: http://www.chimos.de/stuff/xen-xcp-ubuntu-manual/xen-xcp-ubuntu-manual.txt http://blog.scottlowe.org/2012/06/28/installing-xcp-xapi-on-ubuntu-server-12-04-lts/ Be aware that installing the XCP-XAPI toolstack on Ubuntu requires lots of hacks and may be a bumpy process. So before you even try, I recommend that you *first* experiment with XCP 1.6 (the "black box" approach) to see if it works with your hardware and if XenCenter fits your needs. Hope the above help. GizmoChicken On Wed, Mar 6, 2013 at 3:06 PM, Guilherme Suzuki <suzuki.gui@gmail.com> wrote:> > Can you tell ..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Guilherme, Okay. Good to know you are certain that IOMMU is activated. Like I wrote before, GPU passthrough is pretty easy to set up in XCP 1.6 when used in conjunction with XenCenter. And by "pretty easy to set up in XCP 1.6 when used in conjunction with XenCenter," I mean select your GPU from a drop-down menu kind of easy. So you might want to back up your current system (or swap out your hard drive) and install XCP 1.6, in conjunction with XenCenter, as a test. If GPU passthrough doesn''t work for you in XCP 1.6 (which relies on Xen 4.1), then you probably have some other hardware problems that you need to straighten out. One note: My system has UEFI, but I have found that things work much better when I force to boot into "comparability mode" at all times. So if you have UEFI, you might want to try that, regardless what dom0 you select. Best of luck! GizmoChicken On Thu, Mar 7, 2013 at 6:19 AM, Guilherme Suzuki <suzuki.gui@gmail.com>wrote:> Gizmo, I''ve gone a little bit further than that. I managed to make things > (vga passthru) working, but that only works with freshly booted dom0. > > On Mar 7, 2013 6:57 AM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: > > Guilherme, > > Before moving further, let''s verify: You do have IOMMU enabled in your > BIOS, correct? If not, you need to enable it to get GPU passthrough to > work. > > Now, back to XCP 1.6... > > XCP 1.6 is kind of a "black box" approach, in that you won''t be able to > simply install it over your current dom0, but instead you must *replace*your current dom0. That said, XCP 1.6 is based on CentOS 5.7 (Linux > kernel v2.6.32.43). But be aware that XCP 1.6 won''t give you a graphical > desktop on dom0. So if you need a graphical desktop on dom0, XCP 1.6 won''t > be a long term solution for you. But given the ease of setting up GPU > passthrough with XCP, it could be relatively easy way for you to verify > that your system is capable of passthrough. > > Also, be aware that, although GPU passthrough is pretty simple with XPC > 1.6, strangely, *you''ll have to do some digging on how to set up > PCI-passthrough so that your mouse/keyboard/device is accessible from a > guest VM.* It can be done, but the procedure isn''t well-documented. > When (and if) you get XPC 1.6 installed and GPU passthrough working, write > back to me, and I''ll try to help with the PCI passthrough. (One thing at a > time.) > > If you must have graphical desktop on dom0, then you have another option, > namely installing the *XCP-XAPI toolstack* (which is the toolstack used > by XCP 1.6) on a desktop version of Ubuntu. In my case, I have > successfully installed the XCP-XAPI toolstack on Ubuntu 12.10 desktop. > > If you want to try XCP-XAPI toolstack on Ubuntu (I recommend Ubuntu 12.10 > desktop if you do), here are two reasonably complete tutorials: > > http://www.chimos.de/stuff/xen-xcp-ubuntu-manual/xen-xcp-ubuntu-manual.txt > > http://blog.scottlowe.org/2012/06/28/installing-xcp-xapi-on-ubuntu-server-12-04-lts/ > > Be aware that installing the XCP-XAPI toolstack on Ubuntu requires lots of > hacks and may be a bumpy process. So before you even try, I recommend that > you *first* experiment with XCP 1.6 (the "black box" approach) to see if > it works with your hardware and if XenCenter fits your needs. > > Hope the above help. > > GizmoChicken > > > > > > On Wed, Mar 6, 2013 at 3:06 PM, Guilherme Suzuki <suzuki.gui@gmail.com> > wrote: > > > > Can you tell ... > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Unfortuntely, XCP is not so easy to install on Fedora. One thing I noticed: kernel 3.8.1 has some improvements regarding Power Management and Reset functions as well. I''ll head this way (downloading kernel, set it and installing). Current version my dom0 is running: 3.6-10. Thx for the help On Mar 7, 2013 10:53 AM, "Gizmo Chicken" <gizmochicken@gmail.com> wrote: Guilherme, Okay. Good to know you are certain that IOMMU is activated. Like I wrote before, GPU passthrough is pretty easy to set up in XCP 1.6 when used in conjunction with XenCenter. And by "pretty easy to set up in XCP 1.6 when used in conjunction with XenCenter," I mean select your GPU from a drop-down menu kind of easy. So you might want to back up your current system (or swap out your hard drive) and install XCP 1.6, in conjunction with XenCenter, as a test. If GPU passthrough doesn''t work for you in XCP 1.6 (which relies on Xen 4.1), then you probably have some other hardware problems that you need to straighten out. One note: My system has UEFI, but I have found that things work much better when I force to boot into "comparability mode" at all times. So if you have UEFI, you might want to try that, regardless what dom0 you select. Best of luck! GizmoChicken On Thu, Mar 7, 2013 at 6:19 AM, Guilherme Suzuki <suzuki.gui@gmail.com> wrote:> > Gizmo, I''ve g..._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi, after reading the thread I don''t think it will help you cause you got other issues, but since i promised the patch and wrote it for another thread a minute ago anyway, here is the reference to it: http://lists.xen.org/archives/html/xen-users/2013-03/msg00127.html :)
Matthias, I think you can help! I applied a similar patch to my xen (unstable, by the way) and all that I get is "parallel0 console" through VNC and the display seems dead (black screen). This time I''m trying to "primary VGA passthru" it. But I noticed something: my VMs have been running with 8gb ram. I''ll try to decrease that... I sort of gave up using my radeon 7950 as secondary, it will only work properly if I reboot dom0 as well. On Mar 12, 2013 4:48 PM, "Matthias" <matthias.kannenberg@googlemail.com> wrote: Hi, after reading the thread I don''t think it will help you cause you got other issues, but since i promised the patch and wrote it for another thread a minute ago anyway, here is the reference to it: http://lists.xen.org/archives/html/xen-users/2013-03/msg00127.html :) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Dude, please forget my previous message! I followed that post from *xen-devel* string, applied the patch and everything seems to be working just fine! That''s really my case (newest kernel, old amd patch). I hope those problems become part of the past from now on. You''re are awesome! Thx a lot. 2013/3/12 Guilherme Suzuki <suzuki.gui@gmail.com>> Matthias, I think you can help! > > I applied a similar patch to my xen (unstable, by the way) and all that I > get is "parallel0 console" through VNC and the display seems dead (black > screen). This time I''m trying to "primary VGA passthru" it. > > But I noticed something: my VMs have been running with 8gb ram. I''ll try > to decrease that... > > I sort of gave up using my radeon 7950 as secondary, it will only work > properly if I reboot dom0 as well. > > On Mar 12, 2013 4:48 PM, "Matthias" <matthias.kannenberg@googlemail.com> > wrote: > > Hi, > > after reading the thread I don''t think it will help you cause you got > other issues, but since i promised the patch and wrote it for another > thread a minute ago anyway, here is the reference to it: > > http://lists.xen.org/archives/html/xen-users/2013-03/msg00127.html > > :) > >-- Grato, ** <http://www.guilhermesuzuki.com>*Guilherme Suzuki* Consultor em TI para projetos Microsoft *http://www.guilhermesuzuki.com* 11 - 992360535 11 - 20990757 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi, good to hear it worked for you! Can you be more specific in what you now did and what xen-devel-thread you followed? 2013/3/12 Guilherme Suzuki <suzuki.gui@gmail.com>:> Dude, please forget my previous message! > > I followed that post from xen-devel string, applied the patch and everything > seems to be working just fine! > > That''s really my case (newest kernel, old amd patch). I hope those problems > become part of the past from now on. > > You''re are awesome! Thx a lot. > > > 2013/3/12 Guilherme Suzuki <suzuki.gui@gmail.com> >> >> Matthias, I think you can help! >> >> I applied a similar patch to my xen (unstable, by the way) and all that I >> get is "parallel0 console" through VNC and the display seems dead (black >> screen). This time I''m trying to "primary VGA passthru" it. >> >> But I noticed something: my VMs have been running with 8gb ram. I''ll try >> to decrease that... >> >> I sort of gave up using my radeon 7950 as secondary, it will only work >> properly if I reboot dom0 as well. >> >> On Mar 12, 2013 4:48 PM, "Matthias" <matthias.kannenberg@googlemail.com> >> wrote: >> >> Hi, >> >> after reading the thread I don''t think it will help you cause you got >> other issues, but since i promised the patch and wrote it for another >> thread a minute ago anyway, here is the reference to it: >> >> http://lists.xen.org/archives/html/xen-users/2013-03/msg00127.html >> >> :) > > > > > -- > Grato, > > Guilherme Suzuki > Consultor em TI para projetos Microsoft > http://www.guilhermesuzuki.com > 11 - 992360535 > 11 - 20990757 > >
Alright, I really thought that things would work now just fine. It does, BUT I''m getting the famous *BSOD* now (after rebooting the *domU*). Now I can use my radeon as primary device or secondary as well (since dom0 is freshly booted) I followed this link straight: http://lists.xen.org/archives/html/xen-users/2013-03/msg00127.html I gitted xen-unstable-staging, applied xen-unstable-atipassthough.patch (the one attached to the link above) and then tried to passthru the VGA device. My kernel version is 3.8.1-201 (I had compiled xen modules into the kernel to use kernel parameters). 2013/3/12 Matthias <matthias.kannenberg@googlemail.com>> Hi, > > good to hear it worked for you! > > Can you be more specific in what you now did and what xen-devel-thread > you followed? > > 2013/3/12 Guilherme Suzuki <suzuki.gui@gmail.com>: > > Dude, please forget my previous message! > > > > I followed that post from xen-devel string, applied the patch and > everything > > seems to be working just fine! > > > > That''s really my case (newest kernel, old amd patch). I hope those > problems > > become part of the past from now on. > > > > You''re are awesome! Thx a lot. > > > > > > 2013/3/12 Guilherme Suzuki <suzuki.gui@gmail.com> > >> > >> Matthias, I think you can help! > >> > >> I applied a similar patch to my xen (unstable, by the way) and all that > I > >> get is "parallel0 console" through VNC and the display seems dead (black > >> screen). This time I''m trying to "primary VGA passthru" it. > >> > >> But I noticed something: my VMs have been running with 8gb ram. I''ll try > >> to decrease that... > >> > >> I sort of gave up using my radeon 7950 as secondary, it will only work > >> properly if I reboot dom0 as well. > >> > >> On Mar 12, 2013 4:48 PM, "Matthias" <matthias.kannenberg@googlemail.com > > > >> wrote: > >> > >> Hi, > >> > >> after reading the thread I don''t think it will help you cause you got > >> other issues, but since i promised the patch and wrote it for another > >> thread a minute ago anyway, here is the reference to it: > >> > >> http://lists.xen.org/archives/html/xen-users/2013-03/msg00127.html > >> > >> :) > > > > > > > > > > -- > > Grato, > > > > Guilherme Suzuki > > Consultor em TI para projetos Microsoft > > http://www.guilhermesuzuki.com > > 11 - 992360535 > > 11 - 20990757 > > > > >-- Grato, ** <http://www.guilhermesuzuki.com>*Guilherme Suzuki* Consultor em TI para projetos Microsoft *http://www.guilhermesuzuki.com* 11 - 992360535 11 - 20990757 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I''m not sure if this is related, but everytime I shutdown a domU (win7 64bits), the display device goes to some sort of a stanby state (like my radeon went to sleep). And then, if I try to passthru again, my linux pc crashes (I can''t even execute commands through ssh). On Mar 13, 2013 1:25 PM, "David TECHER" <davidtecher@yahoo.fr> wrote: Got the same behavior for windows. But I can reboot VM only when it is a Linux-VM. ________________________________ De : Guilherme Suzuki <suzuki.gui@gmail.com> *À :* David TECHER <davidtecher@yahoo.fr> *Cc :* Matthias <matthias.kannenberg@googlemail.com>; " xen-users@lists.xen.org" <xen-users@lists.xen.org> *Envoyé le :* Mercredi 13 mars 2013 16h03 Objet : Re: [Xen-users] VGA Passthru - FLR? David, hi! Are you able to reboot domU? Cause in my case, after rebooting domU, xen just crashes t... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users