Is PCI pass-through available in the "standard" CentOS 5.1 kernel? From the "xm info" command, I see the major.minor version of Xen is 3.1, so I''m assuming it is and that I''m missing something basic. I''ve tried using "pciback.hide=(...)" in grub.conf, but after getting an error message about it not being valid, I realized that pciback is a module, so it''s not available. So, I tried it in /etc/modprobe.conf, but that apparently didn''t work either. I also tried this ( http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module?highlight=%28pci%29) and it seemed to work -- I at least got a message about the pciback grabbing the device. I do, however, still see the device when I do a "lspci", but I''m not certain if that is normal or not. I added the "pci = [ ... ]" in my Xen domU config file but am not seeing the device in lspci (which is totally empty), and am not sure what is up. Since I don''t have the "xm" commands in the domU, I''m not sure what to do. I''d like to pass in my video capture devices into a domU and get Myth or Sage running in one of my domU''s. Base OS is CentOS 5.1 x86_64 for sheer stability and patchability; that way the domU can be tweaked/upgraded/rebuilt without impacting anything else. Any suggestions would be appreciated! -Rob _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Rob, On Sun, Apr 20, 2008 at 11:33 PM, Rob Greene <robgreene@gmail.com> wrote:> Is PCI pass-through available in the "standard" CentOS 5.1 kernel? From > the "xm info" command, I see the major.minor version of Xen is 3.1, so I''m > assuming it is and that I''m missing something basic. > > I''ve tried using "pciback.hide=(...)" in grub.conf, but after getting an > error message about it not being valid, I realized that pciback is a module, > so it''s not available. > > So, I tried it in /etc/modprobe.conf, but that apparently didn''t work > either. I also tried this ( > http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module?highlight=%28pci%29) > and it seemed to work -- I at least got a message about the pciback grabbing > the device. I do, however, still see the device when I do a "lspci", but > I''m not certain if that is normal or not. >This is normal, at least in my experience I have always seen the device in lspci. The seizing device line is one of the best ways to know that it worked.> > I added the "pci = [ ... ]" in my Xen domU config file but am not seeing > the device in lspci (which is totally empty), and am not sure what is up. > Since I don''t have the "xm" commands in the domU, I''m not sure what to do. >Usually if you pass the pci device in the domU config file it will give an error if it isn''t able to give it. Are you seeing any errors in any of the xen log files when you start that guest? Cheers, Todd> > I''d like to pass in my video capture devices into a domU and get Myth or > Sage running in one of my domU''s. Base OS is CentOS 5.1 x86_64 for sheer > stability and patchability; that way the domU can be > tweaked/upgraded/rebuilt without impacting anything else. > > Any suggestions would be appreciated! > -Rob > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
----- Original Message -----
From: Todd Deshane
To: Rob Greene
Cc: xen-users@lists.xensource.com
Sent: Monday, April 21, 2008 6:34 PM
Subject: Re: [Xen-users] CentOS/Xen PCI pass-through
Hi Rob,
On Sun, Apr 20, 2008 at 11:33 PM, Rob Greene <robgreene@gmail.com>
wrote:
Is PCI pass-through available in the "standard" CentOS 5.1 kernel?
>From the "xm info" command, I see the major.minor version of Xen
is 3.1, so I''m assuming it is and that I''m missing something
basic.
I''ve tried using "pciback.hide=(...)" in grub.conf, but
after getting an error message about it not being valid, I realized that pciback
is a module, so it''s not available.
So, I tried it in /etc/modprobe.conf, but that apparently didn''t
work either. I also tried this
(http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module?highlight=%28pci%29)
and it seemed to work -- I at least got a message about the pciback grabbing the
device. I do, however, still see the device when I do a "lspci", but
I''m not certain if that is normal or not.
This is normal, at least in my experience I have always seen the device in
lspci. The seizing device line is one of the best ways to know that it worked.
I added the "pci = [ ... ]" in my Xen domU config file but am not
seeing the device in lspci (which is totally empty), and am not sure what is up.
Since I don''t have the "xm" commands in the domU,
I''m not sure what to do.
Usually if you pass the pci device in the domU config file it will give an
error if it isn''t able to give it. Are you seeing any errors in any of
the xen log files when you start that guest?
Cheers,
Todd
I''d like to pass in my video capture devices into a domU and get
Myth or Sage running in one of my domU''s. Base OS is CentOS 5.1 x86_64
for sheer stability and patchability; that way the domU can be
tweaked/upgraded/rebuilt without impacting anything else.
Any suggestions would be appreciated!
-Rob
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
------------------------------------------------------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Guys, I have been trying to get PCI Passthrough working for *MONTHS* now. Finally, when I stopped trying, I came across the following page. http://www.novell.com/coolsolutions/feature/17605.html In the bottom half are the best instructions I''ve seen so far for getting PCI Passthrough to work yet. It not only explains it better than most places, but it allows you to see and understand what is actually going on during the process. I now have successfully passed through a network card and a video card to a DomU machine. (I''ve yet to get the video card to actually work, but it''s in the PCI list now) Hope this helps, Phil. ----- Original Message ----- From: Rob Greene To: xen-users@lists.xensource.com Sent: Monday, April 21, 2008 4:33 AM Subject: [Xen-users] CentOS/Xen PCI pass-through Is PCI pass-through available in the "standard" CentOS 5.1 kernel? >From the "xm info" command, I see the major.minor version of Xen is 3.1, so I''m assuming it is and that I''m missing something basic. I''ve tried using "pciback.hide=(...)" in grub.conf, but after getting an error message about it not being valid, I realized that pciback is a module, so it''s not available. So, I tried it in /etc/modprobe.conf, but that apparently didn''t work either. I also tried this (http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module?highlight=%28pci%29) and it seemed to work -- I at least got a message about the pciback grabbing the device. I do, however, still see the device when I do a "lspci", but I''m not certain if that is normal or not. I added the "pci = [ ... ]" in my Xen domU config file but am not seeing the device in lspci (which is totally empty), and am not sure what is up. Since I don''t have the "xm" commands in the domU, I''m not sure what to do. I''d like to pass in my video capture devices into a domU and get Myth or Sage running in one of my domU''s. Base OS is CentOS 5.1 x86_64 for sheer stability and patchability; that way the domU can be tweaked/upgraded/rebuilt without impacting anything else. Any suggestions would be appreciated! -Rob ------------------------------------------------------------------------------ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Well, I got to the point that I''m receiving errors when starting the domU -- something about requiring 4 arguments but only got three. I tried the patches and they didn''t work. I think this is my fault, however, as I tried to upgrade to Xen 3.2, thinking I needed it, and then "downgraded" to the default CentOS libraries. I don''t remember the error message from before that adventure. So, since I haven''t built the machine out, I''m going to reinstall CentOS (hopefully) tonight and start again. I do have a question, however. CentOS 5.1 comes with what appears to be Xen 3.1 (major=3 and minor=1 in "xm info") but the capabilities are all listed as "3.0" something-or-another. Do I need to install something different or should I be fine with the base CentOS 5.1 + Xen install? Thanks for the help! Hopefully I''ll be closer in a day or two... -Rob _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>I do have a question, however. CentOS 5.1 comes with what appears to be Xen 3.1 (major=3 and minor=1 >in "xm info") but the capabilities are all listed as "3.0" something-or-another. Do I need to install something >different or should I be fine with the base CentOS 5.1 + Xen install? > >Thanks for the help! Hopefully I''ll be closer in a day or two... >-RobThe version in of xen in CentOS has been back ported. It should work fine. jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Just to keep the conversation going, here''s my status: It works! My configuration from before apparently was fine -- I''m not certain where the error messages went, but did disappear (and I didn''t have to reinstall CentOS after all). I do have an anomaly, and this might help others: If I start from the Virtual Machine Manager, the PCI pass-through *does not work*. If I start with "xm create ______", PCI pass-through *does work*. I''m not certain of what the actual difference is between these, but that''s good to know. Now I''m off to mess around with those silly IVTV drivers! -Rob _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Rob, On Wed, Apr 23, 2008 at 11:08 PM, Rob Greene <robgreene@gmail.com> wrote:> Just to keep the conversation going, here''s my status: > > It works! My configuration from before apparently was fine -- I''m not > certain where the error messages went, but did disappear (and I didn''t have > to reinstall CentOS after all). > > I do have an anomaly, and this might help others: If I start from the > Virtual Machine Manager, the PCI pass-through *does not work*. If I start > with "xm create ______", PCI pass-through *does work*. I''m not certain of > what the actual difference is between these, but that''s good to know. >Thanks for reporting that. There must be some sort of bug or config problem somewhere. I wonder if virt-manager is using a different config file than you expect? If not then some bug or problem somewhere else. Todd> > Now I''m off to mess around with those silly IVTV drivers! > -Rob > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Oops, I wasn''t paying attention... this message was meant for the list! -Rob On Thu, Apr 24, 2008 at 9:28 AM, Rob Greene <robgreene@gmail.com> wrote:> I wonder if virt-manager is using a different config file than you expect? >> If not then some bug or problem somewhere else. >> > > I''m not certain where that other config file might live? I''ve been putting > them in /etc/xen and nowhere else. When I manually create the file, at some > point it shows up in virt-manager (not sure if it just shows up or if it is > after the first "xm create ____"). > -Rob >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday 24 April 2008 11:16:35 Todd Deshane wrote:> Hi Rob, > > On Wed, Apr 23, 2008 at 11:08 PM, Rob Greene <robgreene@gmail.com>wrote:> > Just to keep the conversation going, here''s my status: > > > > It works! My configuration from before apparently was fine -- I''m > > not certain where the error messages went, but did disappear (and I > > didn''t have to reinstall CentOS after all). > > > > I do have an anomaly, and this might help others: If I start from > > the Virtual Machine Manager, the PCI pass-through *does not work*. > > If I start with "xm create ______", PCI pass-through *does work*. > > I''m not certain of what the actual difference is between these, but > > that''s good to know. > > Thanks for reporting that. There must be some sort of bug or config > problem somewhere. > > I wonder if virt-manager is using a different config file than you > expect? If not then some bug or problem somewhere else.[Sorry - not sent to the list originally...] Typically - yes. I''ve not looked at RHEL/CentOS lately, but I suspect the implementation of virt-manager is the same as that in SUSE, whereby the VMs configurations are stored rather than read from their config files. You can probably ''fix'' the datastore dy doing xm delete <VM name> and then xm new <config file name>. This will re-add the VM to the datastore using the updated config file. e.g if xm list shows I have a DomU called fedora, and I have a config file called /etc/xen/vm/fedora (default location in SUSE) I would run xm delete fedora to remove the entry from the datastore, and then run xm new fedora to recreate it from the config file in /etc/xen/vm Hope this helps, Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users