>Number:         35069
>Category:       misc
>Synopsis:       NetBSD/xen-Howto: physdev_dom0_hide potenial confusion.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Nov 18 06:15:00 +0000 2006
>Originator:     Jason White
>Release:        NetBSD 3.0
>Organization:
Jason White <jdwhite@menelos.com>       Jabber: jdwhite(jabber.org)
http://jdwhite.menelos.com/                     jason.d.white(gmail.com)
PGP KeyID: 0x5290E477
>Environment:
System: NetBSD bender.menelos.com 3.0 NetBSD 3.0 (BENDER) #0: Thu Feb 2 17:13:01 CST 2006 jdwhite@smeghead:/usr/obj/i386/BENDER i386
Architecture: i386
Machine: i386
>Description:
In the xen Howto (http://www.netbsd.org/Ports/xen/howto.html) under the 
section "Using PCI devices in guest domains" points out that the numeric 
values used in the physdev_dom0_hide option are hexadecimal.  However, 
NetBSD outputs this information at boot in decimal.  If one uses dmesg output 
to determine which PCI device to hide, they may not realize that these values 
are in decimal.

Unfortunately, the example dmesg output in the xen-Howto uses values less 
then 10, so this subtle point is not reinforced.
>How-To-Repeat:
>Fix:
Use an example with a device value greater than 10 so the conversion from 
decimal to hexadecimal is shown.  I suggest the following change:

[...]
  For example, to hide devices PCI bus 0, device 10, function 2 and PCI bus 0, 
  device 6, function 0 and PCI bus 1, device 17, function 0 I use (note that 
  NetBSD kernel messages show these values in decimal, but the values
  passed to physdev_dom0_hide are interpreted in hex):

      physdev_dom0_hide='(00:0A.2)(01:11.0)(00:06.0)'
[...]