thr3ads.net - Xen users - [Xen-users] passthrough PCI SCSI device [Apr 2010]

If this information is useful, please help other people find it:
Share via:

James Pifer

2010-Apr-26 14:18 UTC

[Xen-users] passthrough PCI SCSI device

I have a sles10sp3 vm that I''m trying to passthrough a scsi card, which
has a DLT tape drive attached. Anyone doing anything similar? 

When I passthrough the scsi card (forced to do both ports), the vm dies
when it loads, I think during udev. I''m viewing the vm through
virt-manager, so I can''t scroll up and see what everything says. 

Is there a way to get the text xm console loaded on a start command so I
can see everything?

Anyone using a DLT tape drive or something similar through a passed
through scsi card? 

Thanks,
James


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

Matej Zary

2010-Apr-26 15:18 UTC

head link

RE: [Xen-users] passthrough PCI SCSI device

If i got the question right

xm start nameofvm -c


Regards 

Matej

-----Original Message-----
From: xen [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of James
Pifer
Sent: Monday, April 26, 2010 4:19 PM
To: Xen List
Subject: [Xen-users] passthrough PCI SCSI device

I have a sles10sp3 vm that I''m trying to passthrough a scsi card, which
has a DLT tape drive attached. Anyone doing anything similar? 

When I passthrough the scsi card (forced to do both ports), the vm dies
when it loads, I think during udev. I''m viewing the vm through
virt-manager, so I can''t scroll up and see what everything says. 

Is there a way to get the text xm console loaded on a start command so I
can see everything?

Anyone using a DLT tape drive or something similar through a passed
through scsi card? 

Thanks,
James


_______________________________________________
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

Simon Hobson

2010-Apr-26 15:36 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

James Pifer wrote:
>Is there a way to get the text xm console loaded on a start command so I
>can see everything?
xm create -c <domain>

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

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

James Pifer

2010-Apr-26 16:13 UTC

head link

RE: [Xen-users] passthrough PCI SCSI device

On Mon, 2010-04-26 at 17:18 +0200, Matej Zary wrote:> If i got the question right
> 
> xm start nameofvm -c
> 
> 
> Regards 
> 
> Matej
Thanks, that helped a lot. Now, anyone have any suggestions for this?
Where would I use swiotlb=force?

SCSI subsystem initialized
Fusion MPT base driver 3.04.07_suse
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.07_suse
PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 C0: Capabilities={Initiator,Target}
scsi0 : ioc0: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=30
Fatal DMA error! Please use ''swiotlb=force''
------------[ cut here ]------------
kernel BUG at arch/i386/kernel/pci-dma-xen.c:106!
invalid opcode: 0000 [#1]
SMP 
last sysfs file: /class/net/eth2/type
Modules linked in: mptspi mptscsih mptbase scsi_transport_spi joydev scsi_mod
ext3 jbd xennet dm_mirror dm_snapshot dm_mod processor xenblk
CPU:    0
EIP:    0061:[<c010c197>]    Not tainted VLI
EFLAGS: 00210092   (2.6.16.60-0.54.5-xenpae #1) 
EIP is at dma_map_sg+0x207/0x230
eax: 0000002f   ebx: ffffffff   ecx: 00000000   edx: 00000001
esi: 89a623c0   edi: 00000003   ebp: ed232600   esp: ecee9a58
ds: 007b   es: 007b   ss: 0069
Process modprobe (pid: 1239, threadinfo=ecee8000 task=c1aca330)
Stack: <0>c0330f04 ee3a2aa6 ed232600 ed30046c 00000001 ed232600 ed639848
00000000
       00000000 00000002 ed639848 ed509000 ecf0cd00 ee394728 00000002 ed5d79a4 
       ecdae01c 00000010 ed5de980 00000000 00000001 00000001 00000001 00000006 
Call Trace:
 [<ee3a2aa6>] mpt_get_msg_frame+0xc6/0x100 [mptbase]
 [<ee394728>] mptscsih_qcmd+0x278/0x8d0 [mptscsih]
 [<ee2baf5f>] scsi_prep_fn+0x20f/0x4b0 [scsi_mod]
 [<c012ed90>] lock_timer_base+0x20/0x50
 [<c012ed90>] lock_timer_base+0x20/0x50
 [<c012eed9>] __mod_timer+0x99/0xc0
 [<ee2b4aba>] scsi_dispatch_cmd+0x16a/0x2b0 [scsi_mod]
 [<ee2bab42>] scsi_request_fn+0x222/0x430 [scsi_mod]
 [<c01f0cc6>] __generic_unplug_device+0x26/0x30
 [<c01f0ee5>] generic_unplug_device+0x15/0x50
 [<c01f0ffa>] blk_execute_rq+0x7a/0xf0
 [<c01f0200>] blk_end_sync_rq+0x0/0x20
 [<c01848ee>] bio_add_pc_page+0x2e/0x40
 [<c01849bb>] bio_map_kern+0xbb/0x100
 [<ee2ba3a2>] scsi_execute+0xd2/0x100 [scsi_mod]
 [<ee2ba44e>] scsi_execute_req+0x7e/0x100 [scsi_mod]
 [<ee2bbbe0>] scsi_probe_and_add_lun+0x230/0xb90 [scsi_mod]
 [<ee2bcb4e>] __scsi_scan_target+0xde/0x6d0 [scsi_mod]
 [<c01feb31>] idr_get_new_above_int+0xe1/0x280
 [<c01fecda>] idr_get_new+0xa/0x30
 [<ee2bd1b7>] scsi_scan_channel+0x77/0x90 [scsi_mod]
 [<ee2bd24d>] scsi_scan_host_selected+0x7d/0x130 [scsi_mod]
 [<ee2b577c>] scsi_add_host+0x19c/0x1c0 [scsi_mod]
 [<ee2bd321>] scsi_scan_host+0x21/0x30 [scsi_mod]
 [<ee3851ba>] mptspi_probe+0x39a/0x460 [mptspi]
 [<c020e56b>] pci_device_probe+0x5b/0x80
 [<c026f2a2>] driver_probe_device+0x52/0xc0
 [<c026f41e>] __driver_attach+0x8e/0x90
 [<c026ec1a>] bus_for_each_dev+0x3a/0x60
 [<c026f1c6>] driver_attach+0x16/0x20
 [<c026f390>] __driver_attach+0x0/0x90
 [<c026e8bc>] bus_add_driver+0x8c/0x140
 [<c020e726>] __pci_register_driver+0x66/0xa0
 [<ee2550a5>] mptspi_init+0xa5/0xc3 [mptspi]
 [<c0142270>] sys_init_module+0x110/0x1c48
 [<c03186d8>] mutex_lock+0x8/0x20
 [<c0105aad>] syscall_call+0x7/0xb
Code: e8 8f 8f 01 00 0f 0b 6d 00 e4 0e 33 c0 e9 d6 fe ff ff 0f 0b 65 00 e4 0e 33
c0 e9 f4 fe ff ff c7 04 24 04 0f 33 c0 e8 69 8f 01 00 <0f> 0b 6a 00 e4 0e
33 c0 e9 82 fe ff ff 0f 0b 22 00 4c 07 33 c0

Thanks,
James


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

listmail

2010-Apr-26 16:58 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

If I got this right, on the extra line if direct booting or on the pv''s
grub menu.lst kernel line.
You may also need iommu=soft ahead of that.

James Pifer wrote:> On Mon, 2010-04-26 at 17:18 +0200, Matej Zary wrote:
>   
>> If i got the question right
>>
>> xm start nameofvm -c
>>
>>
>> Regards 
>>
>> Matej
>>     
>
> Thanks, that helped a lot. Now, anyone have any suggestions for this?
> Where would I use swiotlb=force?
>
> SCSI subsystem initialized
> Fusion MPT base driver 3.04.07_suse
> Copyright (c) 1999-2008 LSI Corporation
> Fusion MPT SPI Host driver 3.04.07_suse
> PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
> mptbase: ioc0: Initiating bringup
> ioc0: LSI53C1030 C0: Capabilities={Initiator,Target}
> scsi0 : ioc0: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=30
> Fatal DMA error! Please use ''swiotlb=force''
> ------------[ cut here ]------------
> kernel BUG at arch/i386/kernel/pci-dma-xen.c:106!
> invalid opcode: 0000 [#1]
> SMP 
> last sysfs file: /class/net/eth2/type
> Modules linked in: mptspi mptscsih mptbase scsi_transport_spi joydev
scsi_mod ext3 jbd xennet dm_mirror dm_snapshot dm_mod processor xenblk
> CPU:    0
> EIP:    0061:[<c010c197>]    Not tainted VLI
> EFLAGS: 00210092   (2.6.16.60-0.54.5-xenpae #1) 
> EIP is at dma_map_sg+0x207/0x230
> eax: 0000002f   ebx: ffffffff   ecx: 00000000   edx: 00000001
> esi: 89a623c0   edi: 00000003   ebp: ed232600   esp: ecee9a58
> ds: 007b   es: 007b   ss: 0069
> Process modprobe (pid: 1239, threadinfo=ecee8000 task=c1aca330)
> Stack: <0>c0330f04 ee3a2aa6 ed232600 ed30046c 00000001 ed232600
ed639848 00000000
>        00000000 00000002 ed639848 ed509000 ecf0cd00 ee394728 00000002
ed5d79a4
>        ecdae01c 00000010 ed5de980 00000000 00000001 00000001 00000001
00000006
> Call Trace:
>  [<ee3a2aa6>] mpt_get_msg_frame+0xc6/0x100 [mptbase]
>  [<ee394728>] mptscsih_qcmd+0x278/0x8d0 [mptscsih]
>  [<ee2baf5f>] scsi_prep_fn+0x20f/0x4b0 [scsi_mod]
>  [<c012ed90>] lock_timer_base+0x20/0x50
>  [<c012ed90>] lock_timer_base+0x20/0x50
>  [<c012eed9>] __mod_timer+0x99/0xc0
>  [<ee2b4aba>] scsi_dispatch_cmd+0x16a/0x2b0 [scsi_mod]
>  [<ee2bab42>] scsi_request_fn+0x222/0x430 [scsi_mod]
>  [<c01f0cc6>] __generic_unplug_device+0x26/0x30
>  [<c01f0ee5>] generic_unplug_device+0x15/0x50
>  [<c01f0ffa>] blk_execute_rq+0x7a/0xf0
>  [<c01f0200>] blk_end_sync_rq+0x0/0x20
>  [<c01848ee>] bio_add_pc_page+0x2e/0x40
>  [<c01849bb>] bio_map_kern+0xbb/0x100
>  [<ee2ba3a2>] scsi_execute+0xd2/0x100 [scsi_mod]
>  [<ee2ba44e>] scsi_execute_req+0x7e/0x100 [scsi_mod]
>  [<ee2bbbe0>] scsi_probe_and_add_lun+0x230/0xb90 [scsi_mod]
>  [<ee2bcb4e>] __scsi_scan_target+0xde/0x6d0 [scsi_mod]
>  [<c01feb31>] idr_get_new_above_int+0xe1/0x280
>  [<c01fecda>] idr_get_new+0xa/0x30
>  [<ee2bd1b7>] scsi_scan_channel+0x77/0x90 [scsi_mod]
>  [<ee2bd24d>] scsi_scan_host_selected+0x7d/0x130 [scsi_mod]
>  [<ee2b577c>] scsi_add_host+0x19c/0x1c0 [scsi_mod]
>  [<ee2bd321>] scsi_scan_host+0x21/0x30 [scsi_mod]
>  [<ee3851ba>] mptspi_probe+0x39a/0x460 [mptspi]
>  [<c020e56b>] pci_device_probe+0x5b/0x80
>  [<c026f2a2>] driver_probe_device+0x52/0xc0
>  [<c026f41e>] __driver_attach+0x8e/0x90
>  [<c026ec1a>] bus_for_each_dev+0x3a/0x60
>  [<c026f1c6>] driver_attach+0x16/0x20
>  [<c026f390>] __driver_attach+0x0/0x90
>  [<c026e8bc>] bus_add_driver+0x8c/0x140
>  [<c020e726>] __pci_register_driver+0x66/0xa0
>  [<ee2550a5>] mptspi_init+0xa5/0xc3 [mptspi]
>  [<c0142270>] sys_init_module+0x110/0x1c48
>  [<c03186d8>] mutex_lock+0x8/0x20
>  [<c0105aad>] syscall_call+0x7/0xb
> Code: e8 8f 8f 01 00 0f 0b 6d 00 e4 0e 33 c0 e9 d6 fe ff ff 0f 0b 65 00 e4
0e 33 c0 e9 f4 fe ff ff c7 04 24 04 0f 33 c0 e8 69 8f 01 00 <0f> 0b 6a 00
e4 0e 33 c0 e9 82 fe ff ff 0f 0b 22 00 4c 07 33 c0
>
> Thanks,
> James
>
>
> _______________________________________________
> 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

James Pifer

2010-Apr-26 17:04 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

On Mon, 2010-04-26 at 12:58 -0400, listmail wrote:> If I got this right, on the extra line if direct booting or on the
pv''s
> grub menu.lst kernel line.
> You may also need iommu=soft ahead of that.

Thanks. Tried that and got:
# xm start vmtest03 -c
Linux version 2.6.16.60-0.54.5-xenpae (geeko@buildhost) (gcc version 4.1.2
20070115 (SUSE Linux)) #1 SMP Fri Sep 4 01:28:03 UTC 2009
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000040800000 (usable)
304MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Allocating PCI resources starting at 50000000 (gap: 40800000:bf800000)
Built 1 zonelists
Kernel command line: iommu=soft swiotlb=force 
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: 2399.316 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Kernel panic - not syncing: No suitable physical memory available for SWIOTLB
buffer!
Use dom0_mem Xen boot parameter to reserve
some DMA memory (e.g., dom0_mem=-128M).

Thanks,
James

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

listmail

2010-Apr-26 17:27 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

That seems weird to suggest dom0_mem=-128M.  I think you can specify 
swiotlb=XXX to allocate some memory, but i''m not sure if its bytes or 
kbytes by default.

James Pifer wrote:> On Mon, 2010-04-26 at 12:58 -0400, listmail wrote:
>   
>> If I got this right, on the extra line if direct booting or on the
pv''s
>> grub menu.lst kernel line.
>> You may also need iommu=soft ahead of that.
>>     
>
>
> Thanks. Tried that and got:
> # xm start vmtest03 -c
> Linux version 2.6.16.60-0.54.5-xenpae (geeko@buildhost) (gcc version 4.1.2
20070115 (SUSE Linux)) #1 SMP Fri Sep 4 01:28:03 UTC 2009
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000040800000 (usable)
> 304MB HIGHMEM available.
> 727MB LOWMEM available.
> NX (Execute Disable) protection: active
> ACPI in unprivileged domain disabled
> Allocating PCI resources starting at 50000000 (gap: 40800000:bf800000)
> Built 1 zonelists
> Kernel command line: iommu=soft swiotlb=force 
> 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: 2399.316 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Kernel panic - not syncing: No suitable physical memory available for
SWIOTLB buffer!
> Use dom0_mem Xen boot parameter to reserve
> some DMA memory (e.g., dom0_mem=-128M).
>
> Thanks,
> James
>
>
> _______________________________________________
> 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

James Pifer

2010-Apr-26 18:54 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

On Mon, 2010-04-26 at 13:27 -0400, listmail wrote:> That seems weird to suggest dom0_mem=-128M.  I think you can specify 
> swiotlb=XXX to allocate some memory, but i''m not sure if its bytes
or
> kbytes by default.
I was going to create a ticket with Novell since I still couldn''t get
it
working. I reapplied the swiotlb=force command so I could capture the
error. Instead of bombing out it worked! Now the domU sees the DLT
drive. We''ll have to do some testing and see if everything actually
works once we install software. 

I assume I had something a little off the first few times I tried it,
but the only thing I changed was swiotlb=128 back to swiotlb=force.

Thanks for the help!

James


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

listmail

2010-Apr-26 19:11 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

This is just speculation here but if the domU booted w/ swiotlb=128 just 
prior to a consecutive
boot with swiotlb=force it could be that the respective memory was still 
available for use.
Something to keep in mind I suppose.  I am still curious if the 
specification is in bytes or not.

James Pifer wrote:> On Mon, 2010-04-26 at 13:27 -0400, listmail wrote:
>   
>> That seems weird to suggest dom0_mem=-128M.  I think you can specify 
>> swiotlb=XXX to allocate some memory, but i''m not sure if its
bytes or
>> kbytes by default.
>>     
>
> I was going to create a ticket with Novell since I still couldn''t
get it
> working. I reapplied the swiotlb=force command so I could capture the
> error. Instead of bombing out it worked! Now the domU sees the DLT
> drive. We''ll have to do some testing and see if everything
actually
> works once we install software. 
>
> I assume I had something a little off the first few times I tried it,
> but the only thing I changed was swiotlb=128 back to swiotlb=force.
>
> Thanks for the help!
>
> James
>
>
> _______________________________________________
> 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

James Pifer

2010-Apr-26 19:36 UTC

head link

Re: [Xen-users] passthrough PCI SCSI device

On Mon, 2010-04-26 at 15:11 -0400, listmail wrote:> This is just speculation here but if the domU booted w/ swiotlb=128 just 
> prior to a consecutive
> boot with swiotlb=force it could be that the respective memory was still 
> available for use.
> Something to keep in mind I suppose.  I am still curious if the 
> specification is in bytes or not.
I was wondering about that. So if I reboot the host machine, is the domU
going to come up correctly?

James


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

Seemingly Similar Threads

Search for more seemingly similar threads

Xen users - Apr 2010 - passthrough PCI SCSI device

[Xen-users] passthrough PCI SCSI device

RE: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

RE: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

Re: [Xen-users] passthrough PCI SCSI device

Seemingly Similar Threads