* Dedicate PCI Devices to DomU?
@ 2006-08-04 18:26 Ahamed K, Rafiq (STSD)
2006-08-07 22:24 ` Jon Mason
0 siblings, 1 reply; 3+ messages in thread
From: Ahamed K, Rafiq (STSD) @ 2006-08-04 18:26 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]
I am trying to dedicate a number of PCI ports to DomU and no success!
The PCI devices I am trying to dedicate are QLogic 23xx cards!
I am using SUSE 10.1 with latest xen-unstable!
I have followed all the instructions given in latest xen 3.0 manual.
Like building the backend support in Dom0
Building the frontend support in DomU
Using the pciback.hide=(xx:xx.x) in Dom0 command line (and it
successfully hides the devices!)
Later while I try to load the driver in Dom1 it doesn't load and seems
to miss some of pci libraries..I am guessing this is due to stripped
down version of DomU build by xen-unstable. This is what it throws!
qla2xxx: Unknown symbol fc_attach_transport
qla2xxx: Unknown symbol pci_set_consistent_dma_mask
qla2xxx: Unknown symbol pci_enable_device
qla2xxx: Unknown symbol fc_remote_port_add
qla2xxx: Unknown symbol fc_remove_host
qla2xxx: Unknown symbol pci_request_regions
qla2xxx: Unknown symbol pci_bus_write_config_byte
qla2xxx: Unknown symbol fc_remote_port_delete
qla2xxx: Unknown symbol pci_bus_read_config_dword
qla2xxx: Unknown symbol pci_bus_read_config_word
qla2xxx: Unknown symbol fc_release_transport
qla2xxx: Unknown symbol pci_set_mwi
qla2xxx: Unknown symbol pci_find_capability
qla2xxx: Unknown symbol fc_remote_port_rolechg
qla2xxx: Unknown symbol pci_bus_write_config_dword
qla2xxx: Unknown symbol pci_set_master
qla2xxx: Unknown symbol pci_bus_write_config_word
qla2xxx: Unknown symbol pci_release_regions
qla2xxx: Unknown symbol scsi_is_fc_rport
qla2xxx: Unknown symbol pci_disable_device
I have attached the logs of Dom1 and Dom0. Can anyone please tell me if
anything is missing?
Note: with xen 2.0 I was able to load at least partially the Qlogic
driver on Dom1. It used to crash after a while!
Thanks,
Rafiq
[-- Attachment #1.2: Type: text/html, Size: 5465 bytes --]
[-- Attachment #2: dom1log --]
[-- Type: application/octet-stream, Size: 4009 bytes --]
Linux version 2.6.16.13-xenU (root@xentop) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Thu Aug 3 21:01:48 MDT 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000020800000 (usable)
0MB HIGHMEM available.
520MB LOWMEM available.
On node 0 totalpages: 133120
DMA zone: 133120 pages, LIFO batch:31
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 0 pages, LIFO batch:0
HighMem zone: 0 pages, LIFO batch:0
Built 1 zonelists
Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sde1 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Xen reported: 2666.852 MHz processor.
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB disabled
vmalloc area: e1000000-fb7fe000, maxmem 33ffe000
Memory: 514816k/532480k available (1797k kernel code, 9044k reserved, 527k data, 144k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5338.00 BogoMIPS (lpj=26690006)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebc3f1 20100000 00000000 00000000 000064bd 00000000 00000001
CPU: After vendor identify, caps: bfebc3f1 20100000 00000000 00000000 000064bd 00000000 00000001
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: After all inits, caps: bfebc3f1 20100000 00000000 00000180 000064bd 00000000 00000001
Checking 'hlt' instruction... OK.
Brought up 1 CPUs
migration_cost=0
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
xen_mem: Initialising balloon driver.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
i8042.c: No controller found.
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
Registering block device major 8
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/pci/0
IP-Config: Incomplete network configuration information.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 144k freed
EXT3 (no)acl options not supported
EXT3 (no)acl options not supported
EXT3 FS on sde1, internal journal
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
qla2xxx: Unknown symbol fc_attach_transport
qla2xxx: Unknown symbol pci_set_consistent_dma_mask
qla2xxx: Unknown symbol pci_enable_device
qla2xxx: Unknown symbol fc_remote_port_add
qla2xxx: Unknown symbol fc_remove_host
qla2xxx: Unknown symbol pci_request_regions
qla2xxx: Unknown symbol pci_bus_write_config_byte
qla2xxx: Unknown symbol fc_remote_port_delete
qla2xxx: Unknown symbol pci_bus_read_config_dword
qla2xxx: Unknown symbol pci_bus_read_config_word
qla2xxx: Unknown symbol fc_release_transport
qla2xxx: Unknown symbol pci_set_mwi
qla2xxx: Unknown symbol pci_find_capability
qla2xxx: Unknown symbol fc_remote_port_rolechg
qla2xxx: Unknown symbol pci_bus_write_config_dword
qla2xxx: Unknown symbol pci_set_master
qla2xxx: Unknown symbol pci_bus_write_config_word
qla2xxx: Unknown symbol pci_release_regions
qla2xxx: Unknown symbol scsi_is_fc_rport
qla2xxx: Unknown symbol pci_disable_device
[-- Attachment #3: dmesg_Dom0 --]
[-- Type: application/octet-stream, Size: 15355 bytes --]
PI: PCI Interrupt Link [LNKG] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKH] (IRQs *5 7 10 11)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: ACPI device : hid PNP0A03
pnp: ACPI device : hid PNP0C02
pnp: ACPI device : hid PNP0200
pnp: ACPI device : hid PNP0800
pnp: ACPI device : hid PNP0303
pnp: ACPI device : hid PNP0F13
pnp: ACPI device : hid PNP0A06
pnp: ACPI device : hid PNP0400
pnp: ACPI device : hid PNP0501
pnp: ACPI device : hid PNP0700
pnp: PnP ACPI: found 10 devices
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: the driver 'system' has been registered
pnp: match found with the PnP device '00:01' and the driver 'system'
pnp: 00:01: ioport range 0x408-0x40f has been reserved
pnp: 00:01: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:01: ioport range 0x700-0x71f has been reserved
pciback 0000:08:04.0: seizing device
pciback 0000:08:04.1: seizing device
pciback 0000:08:06.0: seizing device
pciback 0000:08:06.1: seizing device
PCI: Bridge: 0000:02:00.0
IO window: disabled.
MEM window: fd000000-fd0fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:07:01.0
IO window: 5000-5fff
MEM window: fd200000-fd2fffff
PREFETCH window: e2000000-e20fffff
PCI: Bridge: 0000:02:00.2
IO window: 4000-5fff
MEM window: fd100000-fd2fffff
PREFETCH window: e2000000-e22fffff
PCI: Bridge: 0000:00:01.0
IO window: 4000-5fff
MEM window: fd000000-fd2fffff
PREFETCH window: e2000000-e22fffff
PCI: Bridge: 0000:00:02.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:03.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:04.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:17:00.0
IO window: 6000-7fff
MEM window: fd400000-fd9fffff
PREFETCH window: fa200000-fa7fffff
PCI: Bridge: 0000:17:00.2
IO window: 8000-9fff
MEM window: fda00000-fdffffff
PREFETCH window: fa800000-fadfffff
PCI: Bridge: 0000:00:06.0
IO window: 6000-9fff
MEM window: fd300000-fdffffff
PREFETCH window: fa200000-fadfffff
PCI: Bridge: 0000:00:07.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: 2000-3fff
MEM window: faf00000-fcffffff
PREFETCH window: e2300000-e23fffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Setting latency timer of device 0000:02:00.0 to 64
PCI: Setting latency timer of device 0000:02:00.2 to 64
PCI: Setting latency timer of device 0000:00:02.0 to 64
PCI: Setting latency timer of device 0000:00:03.0 to 64
PCI: Setting latency timer of device 0000:00:04.0 to 64
PCI: Setting latency timer of device 0000:00:05.0 to 64
PCI: Setting latency timer of device 0000:00:06.0 to 64
ACPI: PCI Interrupt 0000:17:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:17:00.0 to 64
ACPI: PCI Interrupt 0000:17:00.2[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:17:00.2 to 64
PCI: Setting latency timer of device 0000:00:07.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
highmem bounce pool size: 64 pages
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
pnp: the driver 'i8042 kbd' has been registered
pnp: match found with the PnP device '00:04' and the driver 'i8042 kbd'
pnp: the driver 'i8042 aux' has been registered
pnp: match found with the PnP device '00:05' and the driver 'i8042 aux'
PNP: PS/2 Controller [PNP0303:KBD,PNP0f0e:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 2.6.10)
Intel(R) PRO/1000 Network Driver - version 6.3.9-k4
Copyright (c) 1999-2005 Intel Corporation.
pcnet32.c:v1.31c 01.Nov.2005 tsbogend@alpha.franken.de
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
tg3.c:v3.49 (Feb 2, 2006)
ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 33 (level, low) -> IRQ 18
eth0: Tigon3 [partno(N/A) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:13:21:65:8f:cb
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth0: dma_rwctrl[769f4000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:03:03.1[B] -> GSI 34 (level, low) -> IRQ 19
eth1: Tigon3 [partno(N/A) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:13:21:65:8f:ca
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[769f4000] dma_mask[64-bit]
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
blkif_init: reqs=64, pages=704, mmap_vstart=0xf3800000
ACPI: PCI Interrupt 0000:08:06.1[B] -> GSI 50 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:08:06.0[A] -> GSI 49 (level, low) -> IRQ 21
ACPI: PCI Interrupt 0000:08:04.1[B] -> GSI 50 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:08:04.0[A] -> GSI 49 (level, low) -> IRQ 21
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt 0000:00:1f.1[A]: no GSI
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0500-0x0507, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x0508-0x050f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: DV-28E-N, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Adaptec aacraid driver (1.1-4 Aug 3 2006 20:51:35)
3ware Storage Controller device driver for Linux v1.26.02.001.
libata version 1.20 loaded.
Fusion MPT base driver 3.03.07
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.03.07
ACPI: PCI Interrupt 0000:07:03.0[A] -> GSI 51 (level, low) -> IRQ 22
mptbase: Initiating ioc0 bringup
ioc0: 53C1030: Capabilities={Initiator,Target}
scsi0 : ioc0: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=22
Vendor: COMPAQ Model: BD03663622 Rev: BDC4
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 71132000 512-byte hdwr sectors (36420 MB)
sda: Write Protect is off
sda: Mode Sense: f1 00 10 08
SCSI device sda: drive cache: write through w/ FUA
SCSI device sda: 71132000 512-byte hdwr sectors (36420 MB)
sda: Write Protect is off
sda: Mode Sense: f1 00 10 08
SCSI device sda: drive cache: write through w/ FUA
sda: sda1 sda2 sda3
sd 0:0:1:0: Attached scsi disk sda
Vendor: COMPAQ Model: BD0366349C Rev: 3B06
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 71132000 512-byte hdwr sectors (36420 MB)
sdb: Write Protect is off
sdb: Mode Sense: f7 00 10 08
SCSI device sdb: drive cache: write through w/ FUA
SCSI device sdb: 71132000 512-byte hdwr sectors (36420 MB)
sdb: Write Protect is off
sdb: Mode Sense: f7 00 10 08
SCSI device sdb: drive cache: write through w/ FUA
sdb: sdb1 sdb2 sdb3 sdb4
sd 0:0:4:0: Attached scsi disk sdb
Vendor: COMPAQ Model: BD03663622 Rev: BDC4
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdc: 71132000 512-byte hdwr sectors (36420 MB)
sdc: Write Protect is off
sdc: Mode Sense: f1 00 10 08
SCSI device sdc: drive cache: write through w/ FUA
SCSI device sdc: 71132000 512-byte hdwr sectors (36420 MB)
sdc: Write Protect is off
sdc: Mode Sense: f1 00 10 08
SCSI device sdc: drive cache: write through w/ FUA
sdc: sdc1 sdc2
sd 0:0:5:0: Attached scsi disk sdc
Vendor: COMPAQ Model: BD0366349C Rev: 3B02
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdd: 71132000 512-byte hdwr sectors (36420 MB)
sdd: Write Protect is off
sdd: Mode Sense: f7 00 10 08
SCSI device sdd: drive cache: write through w/ FUA
SCSI device sdd: 71132000 512-byte hdwr sectors (36420 MB)
sdd: Write Protect is off
sdd: Mode Sense: f7 00 10 08
SCSI device sdd: drive cache: write through w/ FUA
sdd: sdd1
sd 0:0:9:0: Attached scsi disk sdd
Vendor: COMPAQ Model: PROLIANT 4L8I Rev: N188
Type: Processor ANSI SCSI revision: 02
ACPI: PCI Interrupt 0000:07:03.1[B] -> GSI 55 (level, low) -> IRQ 23
mptbase: Initiating ioc1 bringup
ioc1: 53C1030: Capabilities={Initiator,Target}
scsi1 : ioc1: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=23
Vendor: COMPAQ Model: BD03663622 Rev: BDC4
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sde: 71132000 512-byte hdwr sectors (36420 MB)
sde: Write Protect is off
sde: Mode Sense: f1 00 10 08
SCSI device sde: drive cache: write through w/ FUA
SCSI device sde: 71132000 512-byte hdwr sectors (36420 MB)
sde: Write Protect is off
sde: Mode Sense: f1 00 10 08
SCSI device sde: drive cache: write through w/ FUA
sde: sde1
sd 1:0:1:0: Attached scsi disk sde
Vendor: COMPAQ Model: PROLIANT 4L2I Rev: N188
Type: Processor ANSI SCSI revision: 02
usbmon: debugfs is not available
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 24
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 24, io base 0x00001020
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 25
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 25, io base 0x00001040
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001060
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 1421.600 MB/sec
raid5: using function: pIII_sse (1421.600 MB/sec)
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
input: AT Translated Set 2 keyboard as /class/input/input0
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
logips2pp: Detected unknown logitech mouse model 1
Bridge firewalling registered
Using IPI Shortcut mode
input: ImExPS/2 Logitech Explorer Mouse as /class/input/input1
Freeing unused kernel memory: 352k freed
ACPI: Thermal Zone [THM0] (8 C)
ReiserFS: sda2: found reiserfs format "3.6" with standard journal
ReiserFS: sda2: using ordered data mode
ReiserFS: sda2: journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda2: checking transaction log (sda2)
ReiserFS: sda2: Using r5 hash to sort names
ReiserFS: sda2: warning: acl not supported.
ReiserFS: sda2: warning: user_xattr not supported.
ReiserFS: sda2: warning: acl not supported.
ReiserFS: sda2: warning: user_xattr not supported.
ReiserFS: sda3: warning: acl not supported.
ReiserFS: sda3: warning: user_xattr not supported.
ReiserFS: sda3: found reiserfs format "3.6" with standard journal
ReiserFS: sda3: using ordered data mode
ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda3: checking transaction log (sda3)
ReiserFS: sda3: Using r5 hash to sort names
Adding 2104472k swap on /dev/sda1. Priority:-1 extents:1 across:2104472k
ACPI: Power Button (FF) [PWRF]
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
device vif0.0 entered promiscuous mode
xenbr0: port 1(vif0.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
tg3: peth0: Link is up at 100 Mbps, full duplex.
tg3: peth0: Flow control is on for TX and on for RX.
device peth0 entered promiscuous mode
xenbr0: port 2(peth0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 2(peth0) entering forwarding state
device vif1.0 entered promiscuous mode
xenbr0: port 3(vif1.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 3(vif1.0) entering forwarding state
kjournald starting. Commit interval 5 seconds
EXT3 FS on sde1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
xenbr0: port 3(vif1.0) entering disabled state
device vif1.0 left promiscuous mode
xenbr0: port 3(vif1.0) entering disabled state
device vif2.0 entered promiscuous mode
xenbr0: port 3(vif2.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 3(vif2.0) entering forwarding state
xenbr0: port 3(vif2.0) entering disabled state
device vif2.0 left promiscuous mode
xenbr0: port 3(vif2.0) entering disabled state
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Dedicate PCI Devices to DomU?
2006-08-04 18:26 Dedicate PCI Devices to DomU? Ahamed K, Rafiq (STSD)
@ 2006-08-07 22:24 ` Jon Mason
2006-08-07 22:42 ` Ahamed K, Rafiq (STSD)
0 siblings, 1 reply; 3+ messages in thread
From: Jon Mason @ 2006-08-07 22:24 UTC (permalink / raw)
To: Ahamed K, Rafiq (STSD); +Cc: xen-devel
On Fri, Aug 04, 2006 at 02:26:41PM -0400, Ahamed K, Rafiq (STSD) wrote:
> I am trying to dedicate a number of PCI ports to DomU and no success!
>
>
>
> The PCI devices I am trying to dedicate are QLogic 23xx cards!
>
>
>
> I am using SUSE 10.1 with latest xen-unstable!
>
>
>
> I have followed all the instructions given in latest xen 3.0 manual.
>
>
>
> Like building the backend support in Dom0
>
> Building the frontend support in DomU
>
> Using the pciback.hide=(xx:xx.x) in Dom0 command line (and it
> successfully hides the devices!)
>
>
>
> Later while I try to load the driver in Dom1 it doesn't load and seems
> to miss some of pci libraries..I am guessing this is due to stripped
> down version of DomU build by xen-unstable. This is what it throws!
>
>
>
> qla2xxx: Unknown symbol fc_attach_transport
>
> qla2xxx: Unknown symbol pci_set_consistent_dma_mask
>
> qla2xxx: Unknown symbol pci_enable_device
>
> qla2xxx: Unknown symbol fc_remote_port_add
>
> qla2xxx: Unknown symbol fc_remove_host
>
> qla2xxx: Unknown symbol pci_request_regions
>
> qla2xxx: Unknown symbol pci_bus_write_config_byte
>
> qla2xxx: Unknown symbol fc_remote_port_delete
>
> qla2xxx: Unknown symbol pci_bus_read_config_dword
>
> qla2xxx: Unknown symbol pci_bus_read_config_word
>
> qla2xxx: Unknown symbol fc_release_transport
>
> qla2xxx: Unknown symbol pci_set_mwi
>
> qla2xxx: Unknown symbol pci_find_capability
>
> qla2xxx: Unknown symbol fc_remote_port_rolechg
>
> qla2xxx: Unknown symbol pci_bus_write_config_dword
>
> qla2xxx: Unknown symbol pci_set_master
>
> qla2xxx: Unknown symbol pci_bus_write_config_word
>
> qla2xxx: Unknown symbol pci_release_regions
>
> qla2xxx: Unknown symbol scsi_is_fc_rport
>
> qla2xxx: Unknown symbol pci_disable_device
>
>
>
> I have attached the logs of Dom1 and Dom0. Can anyone please tell me if
> anything is missing?
This looks to me like you setup everything to be a module and didn't
copy them over to your domU. Can you send your domU .config to confirm
this?
Thanks,
Jon
>
>
>
> Note: with xen 2.0 I was able to load at least partially the Qlogic
> driver on Dom1. It used to crash after a while!
>
>
>
> Thanks,
>
> Rafiq
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Dedicate PCI Devices to DomU?
2006-08-07 22:24 ` Jon Mason
@ 2006-08-07 22:42 ` Ahamed K, Rafiq (STSD)
0 siblings, 0 replies; 3+ messages in thread
From: Ahamed K, Rafiq (STSD) @ 2006-08-07 22:42 UTC (permalink / raw)
To: Jon Mason; +Cc: xen-devel
Thanks for the help jon,
I am able to load now! My para-virtualized guest systems fstab and
modprobe.conf weren't updated properly....
Rafiq
-----Original Message-----
From: Jon Mason [mailto:jdmason@us.ibm.com]
Sent: Monday, August 07, 2006 4:25 PM
To: Ahamed K, Rafiq (STSD)
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Dedicate PCI Devices to DomU?
On Fri, Aug 04, 2006 at 02:26:41PM -0400, Ahamed K, Rafiq (STSD) wrote:
> I am trying to dedicate a number of PCI ports to DomU and no success!
>
>
>
> The PCI devices I am trying to dedicate are QLogic 23xx cards!
>
>
>
> I am using SUSE 10.1 with latest xen-unstable!
>
>
>
> I have followed all the instructions given in latest xen 3.0 manual.
>
>
>
> Like building the backend support in Dom0
>
> Building the frontend support in DomU
>
> Using the pciback.hide=(xx:xx.x) in Dom0 command line (and it
> successfully hides the devices!)
>
>
>
> Later while I try to load the driver in Dom1 it doesn't load and seems
> to miss some of pci libraries..I am guessing this is due to stripped
> down version of DomU build by xen-unstable. This is what it throws!
>
>
>
> qla2xxx: Unknown symbol fc_attach_transport
>
> qla2xxx: Unknown symbol pci_set_consistent_dma_mask
>
> qla2xxx: Unknown symbol pci_enable_device
>
> qla2xxx: Unknown symbol fc_remote_port_add
>
> qla2xxx: Unknown symbol fc_remove_host
>
> qla2xxx: Unknown symbol pci_request_regions
>
> qla2xxx: Unknown symbol pci_bus_write_config_byte
>
> qla2xxx: Unknown symbol fc_remote_port_delete
>
> qla2xxx: Unknown symbol pci_bus_read_config_dword
>
> qla2xxx: Unknown symbol pci_bus_read_config_word
>
> qla2xxx: Unknown symbol fc_release_transport
>
> qla2xxx: Unknown symbol pci_set_mwi
>
> qla2xxx: Unknown symbol pci_find_capability
>
> qla2xxx: Unknown symbol fc_remote_port_rolechg
>
> qla2xxx: Unknown symbol pci_bus_write_config_dword
>
> qla2xxx: Unknown symbol pci_set_master
>
> qla2xxx: Unknown symbol pci_bus_write_config_word
>
> qla2xxx: Unknown symbol pci_release_regions
>
> qla2xxx: Unknown symbol scsi_is_fc_rport
>
> qla2xxx: Unknown symbol pci_disable_device
>
>
>
> I have attached the logs of Dom1 and Dom0. Can anyone please tell me
> if anything is missing?
This looks to me like you setup everything to be a module and didn't
copy them over to your domU. Can you send your domU .config to confirm
this?
Thanks,
Jon
>
>
>
> Note: with xen 2.0 I was able to load at least partially the Qlogic
> driver on Dom1. It used to crash after a while!
>
>
>
> Thanks,
>
> Rafiq
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-08-07 22:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-04 18:26 Dedicate PCI Devices to DomU? Ahamed K, Rafiq (STSD)
2006-08-07 22:24 ` Jon Mason
2006-08-07 22:42 ` Ahamed K, Rafiq (STSD)
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.