Xen users - Apr 2012 - xen-pciback cause my system hang

Hi,

I have successfully start my Win7 x86 domU on my x64 Xen dom0 system. Now I
want to give my Win7 full access to my Nvidia card.

lspci

01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 140M]
(rev a1)


and I added these to my /etc/modprobe.d/xen-pciback.conf

options xen-pciback hide=(0000:01:00.0)


then I ran modprobe xen-pciback

nothing happens on the screen, and my system becomes unresponsive. But
interestingly, I can use Ctrl+Alt+Del to reboot my system. I guess the
system is not all hanged, it is only the screen not responsive.


-- 
Regards，
David Shen

http://about.me/davidshen
https://twitter.com/#!/davidshen84


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hi,

On Mon, Apr 09, Xi Shen wrote:
> 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 140M]
> (rev a1)
> 
> 
> and I added these to my /etc/modprobe.d/xen-pciback.conf
> 
> options xen-pciback hide=(0000:01:00.0)
when you put the grafic card to a domU, then dom0 can''t display any
new stuff on it.
Maybe you want insert a second card for dom0, or use a serial cable
to get access to your dom0 from a second computer.


-- 
Best regards

  Dieter

--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won''t use my address in
the
From field.

I kind of guessed that. But I do not have another card, or computer...I
will try to use a script to start my domU.


On Tuesday, April 10, 2012, Dieter Bloms wrote:
> Hi,
>
> On Mon, Apr 09, Xi Shen wrote:
>
> > 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS
> 140M]
> > (rev a1)
> >
> >
> > and I added these to my /etc/modprobe.d/xen-pciback.conf
> >
> > options xen-pciback hide=(0000:01:00.0)
>
> when you put the grafic card to a domU, then dom0 can''t display
any
> new stuff on it.
> Maybe you want insert a second card for dom0, or use a serial cable
> to get access to your dom0 from a second computer.
>
>
> --
> Best regards
>
>  Dieter
>
> --
> I do not get viruses because I do not use MS software.
> If you use Outlook then please do not put my email address in your
> address-book so that WHEN you get a virus it won''t use my address
in the
> From field.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org <javascript:;>
> http://lists.xen.org/xen-users
>

-- 
Regards，
David Shen

http://about.me/davidshen
https://twitter.com/#!/davidshen84


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hi,
I tried running debian wheezy amd64 with the debian stock kernel 3.2 and
xen 4.2 rc3. Compiling ran through without any errors and xen boots up
without problems.

But xen-pciback always produces the same error message:

# lsmod | grep pci
pci_stub               12429  0
# modprobe xen-pciback
ERROR: could not insert ''xen_pciback'': Unknown symbol in
module, or
unknown parameter (see dmesg)
# dmesg | tail -n 1
[ 3687.470124] xen_pciback: Unknown parameter `1)''


This message always appears when I try to load xen-pciback, whenever I
give a "hide=(0000:01.00.0)" parameter or not, or in general whatever
I do.

Since I couldn''t find any help on this topic so far, I hope for some
idea for a solution here!


Best Regards,
Tilo

If you are using the stock kernel and pciback as a module, then you have to
use live binding, not grub.

Alternatively, rebuild the kernel with pciback built-in (not as a module)
and that will allow you to use grub.

Supposedly you can rebuild the initrd image without recompiling the whole
kernel, if live binding isn''t appealing then I would investigate that.

On Mon, Sep 10, 2012 at 1:03 PM, Tilo Peter <phenix@web.de> wrote:
> Hi,
> I tried running debian wheezy amd64 with the debian stock kernel 3.2 and
> xen 4.2 rc3. Compiling ran through without any errors and xen boots up
> without problems.
>
> But xen-pciback always produces the same error message:
>
> # lsmod | grep pci
> pci_stub               12429  0
> # modprobe xen-pciback
> ERROR: could not insert ''xen_pciback'': Unknown symbol in
module, or
> unknown parameter (see dmesg)
> # dmesg | tail -n 1
> [ 3687.470124] xen_pciback: Unknown parameter `1)''
>
>
> This message always appears when I try to load xen-pciback, whenever I
> give a "hide=(0000:01.00.0)" parameter or not, or in general
whatever I do.
>
> Since I couldn''t find any help on this topic so far, I hope for
some
> idea for a solution here!
>
>
> Best Regards,
> Tilo
>
>
> _______________________________________________
> 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

Thanks for your reply,
what exactly do you mean by "live binding"? As I showed in the code 
example, I tried to do this in the running system using modprobe.

I will look into recompiling the kernel, but I still wonder if there is 
a bug that prevents xen-pciback to run probably in this configuration.


On 10.9.12 21:13, Casey DeLorme wrote:
> If you are using the stock kernel and pciback as a module, then you have
> to use live binding, not grub.
>
> Alternatively, rebuild the kernel with pciback built-in (not as a
> module) and that will allow you to use grub.
>
> Supposedly you can rebuild the initrd image without recompiling the
> whole kernel, if live binding isn''t appealing then I would
investigate that.
>
> On Mon, Sep 10, 2012 at 1:03 PM, Tilo Peter <phenix@web.de
> <mailto:phenix@web.de>> wrote:
>
>     Hi,
>     I tried running debian wheezy amd64 with the debian stock kernel 3.2
and
>     xen 4.2 rc3. Compiling ran through without any errors and xen boots up
>     without problems.
>
>     But xen-pciback always produces the same error message:
>
>     # lsmod | grep pci
>     pci_stub               12429  0
>     # modprobe xen-pciback
>     ERROR: could not insert ''xen_pciback'': Unknown symbol
in module, or
>     unknown parameter (see dmesg)
>     # dmesg | tail -n 1
>     [ 3687.470124] xen_pciback: Unknown parameter `1)''
>
>
>     This message always appears when I try to load xen-pciback, whenever I
>     give a "hide=(0000:01.00.0)" parameter or not, or in general
>     whatever I do.
>
>     Since I couldn''t find any help on this topic so far, I hope
for some
>     idea for a solution here!
>
>
>     Best Regards,
>     Tilo
>

Quoting Tilo Peter''s message from 10 sep 2012:
>Hi,
>I tried running debian wheezy amd64 with the debian stock kernel 3.2
>and xen 4.2 rc3. Compiling ran through without any errors and xen
>boots up without problems.
>
>But xen-pciback always produces the same error message:
>
># lsmod | grep pci
>pci_stub               12429  0
># modprobe xen-pciback
>ERROR: could not insert ''xen_pciback'': Unknown symbol in
module, or
>unknown parameter (see dmesg)
># dmesg | tail -n 1
>[ 3687.470124] xen_pciback: Unknown parameter `1)''
>
>
>This message always appears when I try to load xen-pciback, whenever I
>give a "hide=(0000:01.00.0)" parameter or not, or in general
whatever
>I do.
>
>Since I couldn''t find any help on this topic so far, I hope for
some
>idea for a solution here!
If you load the module on the kernel command line, try to put the whole
string inside quotes. For example, in my extlinux.conf I have:
"xen-pciback.hide=(01:00.0)" and I can imagine that you could also try
this with grub.

I noticed you have 0000:01.00.0. I see two periods. Are you sure that
this is right? Usually it should be similar to 01:00.0, 02:00.0,
06:04.0 et cetera. Be sure to double check that.

If you would rather not have the xen-pciback line in grub but instead
have the module be loaded during boot or via a manual modprobe, then be
sure to have something in /etc/modules.conf or /etc/module.d/custom.conf
(or another name of your own preference) like the following:

options xen-pciback hide=(01:00.0)(02:00.0)(06:04.0)

After that, run update-initramfs. Usually I just do either
"update-initramfs -k all -c" or instead of -c (create new initramfs)
I use -u (update existing initramfs).

If that does not work, try to put the full string of the last element
in quotes and retry again.


-- 
HTH,
Mark van Dijk.                ,---------------------------------
-----------------------------''         Mon Sep 10 20:34 UTC 2012
Today is Pungenday, the 34th day of Bureaucracy in the YOLD 3178

On 10/09/12 22:34, Mark van Dijk wrote:
> Quoting Tilo Peter''s message from 10 sep 2012:
>> Hi,
>> I tried running debian wheezy amd64 with the debian stock kernel 3.2
>> and xen 4.2 rc3. Compiling ran through without any errors and xen
>> boots up without problems.
>>
>> But xen-pciback always produces the same error message:
>>
>> # lsmod | grep pci
>> pci_stub               12429  0
>> # modprobe xen-pciback
>> ERROR: could not insert ''xen_pciback'': Unknown symbol
in module, or
>> unknown parameter (see dmesg)
>> # dmesg | tail -n 1
>> [ 3687.470124] xen_pciback: Unknown parameter `1)''
>>
>>
>> This message always appears when I try to load xen-pciback, whenever I
>> give a "hide=(0000:01.00.0)" parameter or not, or in general
whatever
>> I do.
>>
>> Since I couldn''t find any help on this topic so far, I hope
for some
>> idea for a solution here!
> 
> If you load the module on the kernel command line, try to put the whole
> string inside quotes. For example, in my extlinux.conf I have:
> "xen-pciback.hide=(01:00.0)" and I can imagine that you could
also try
> this with grub.
I tried this, but it didn''t work, just didn''t give any effect
I could
see. I only checked with "xm pci-list-assignable-devices", or is there
any other way?
> I noticed you have 0000:01.00.0. I see two periods. Are you sure that
> this is right? Usually it should be similar to 01:00.0, 02:00.0,
> 06:04.0 et cetera. Be sure to double check that.
Just a typo, because in the shell it doesnt matter if try "modprobe
xen-pciback", "modprobe xen-pciback
''hide=(01.00.0)''" or "modprobe
xen-pciback foobar" the error message will always be the same.
> If you would rather not have the xen-pciback line in grub but instead
> have the module be loaded during boot or via a manual modprobe, then be
> sure to have something in /etc/modules.conf or /etc/module.d/custom.conf
> (or another name of your own preference) like the following:
> 
> options xen-pciback hide=(01:00.0)(02:00.0)(06:04.0)
OK, this actually worked. Thanks!
> After that, run update-initramfs. Usually I just do either
> "update-initramfs -k all -c" or instead of -c (create new
initramfs)
> I use -u (update existing initramfs).
> 
> If that does not work, try to put the full string of the last element
> in quotes and retry again.