qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 6/9] vhost-scsi: new device supporting the tcm_v


From: Libaiqing
Subject: Re: [Qemu-devel] [PATCH 6/9] vhost-scsi: new device supporting the tcm_vhost Linux kernel module
Date: Thu, 20 Jun 2013 08:49:50 +0000

Hi Asias,
    Thanks for your config.
    According to you config,I test booting from vhost device with upstream 
kernel and qemu,but failed.
    
    1 installing guest from cdrom,ok.
    2 booting vhost-scsi,guest fs error occurs. 
    3 using fileio backstores,the error is same..
    4 rebooting guest,a log printed:
     (qemu) hw/scsi/virtio-scsi.c:533:virtio_scsi_handle_event: Object 
0x7fccae7f2c88 is not an instance of type virtio-scsi-device
    5 using upstream seabios,core dumped.
 
    Could you give me some advise to debug this problem ? I can provide more 
information if need.

The qemu cmd:
address@hidden x86_64-softmmu]# ./qemu-system-x86_64 -enable-kvm -name fedora   
-M pc -m 1024 -smp 2   -drive file=/home/fedora18.iso,if=ide,media=cdrom 
-device vhost-scsi-pci,wwpn=naa.50014057133e25dc  -monitor stdio   -vga qxl  
-vnc :1

The vnc output:
Dracut-initqueue[189]:/dev/mapper/fedora-root:UNEXPECTED INCONSISTENCY;RUN FSCK 
MANUALLY.
Dracut-initqueue[189]: Warning: e2fsck returned with 4
Dracut-initqueue[189]: Warning: ***An error occurred during the file system 
check.

The guest kernel log:
Kernel: virtio-pci 0000:00:04.0: irq 40 for MSI/MSI-X
Kernel: virtio-pci 0000:00:04.0: irq 41 for MSI/MSI-X
Kernel: virtio-pci 0000:00:04.0: irq 42 for MSI/MSI-X
Kernel: virtio-pci 0000:00:04.0: irq 43 for MSI/MSI-X
Kernel: scsi2 : Virtio SCSI HBA
Kernel: scsi 2:0:1:0: Direct-Access LIO-ORG r0
Kernel: sd 2:0:1:0: Attached scsi generic sg1 type 0
Kernel: sd 2:0:1:0: [sda]1258912 512-byte logical .....
Kernel: sd 2:0:1:0: [sda]write protect is off
Kernel: sd 2:0:1:0: [sda]Mode sense :43 00 00 08
Kernel: sd 2:0:1:0: [sda]write cache: disabled, read .....
Kernel: sda sda1 sda2
Kernel: sd 2:0:1:0: [sda] Attached SCSI disk
Dracut-initqueue[189]: Scanning devices sda2 for LVM
Dracut-initqueue[189]: inactive '/dev/fedora/swap'...
Dracut-initqueue[189]: inactive '/dev/fedora/root'...

The info of host:
address@hidden x86_64-softmmu]# uname -a
Linux fedora121 3.10.0-rc6 #1 SMP Wed Jun 19 19:34:24 CST 2013 x86_64 x86_64 
x86_64 GNU/Linux
address@hidden x86_64-softmmu]# lsmod |grep vhost_scsi
vhost_scsi             49456  5
target_core_mod       282163  14 
target_core_iblock,target_core_pscsi,iscsi_target_mod,target_core_file,vhost_scsi
address@hidden x86_64-softmmu]# targetcli
targetcli shell version v2.1.fb26
Copyright 2011 by RisingTide Systems LLC and others.
For help on commands, type 'help'.

/> ls
o- / 
.........................................................................................................................
 [...]
  o- backstores 
..............................................................................................................
 [...]
  | o- block 
..................................................................................................
 [Storage Objects: 0]
  | o- fileio 
.................................................................................................
 [Storage Objects: 0]
  | o- pscsi 
..................................................................................................
 [Storage Objects: 0]
  | o- ramdisk 
................................................................................................
 [Storage Objects: 1]
  |   o- r0 
...................................................................................................
 [(6.0GiB) activated]
  o- iscsi 
............................................................................................................
 [Targets: 0]
  o- loopback 
.........................................................................................................
 [Targets: 0]
  o- vhost 
............................................................................................................
 [Targets: 1]
    o- naa.50014057133e25dc 
..............................................................................................
 [TPGs: 1]
      o- tpg1 
...............................................................................................
 [naa.5001405a70ac3421]
        o- acls 
..........................................................................................................
 [ACLs: 0]
        o- luns 
..........................................................................................................
 [LUNs: 1]
          o- lun0 
.....................................................................................................
 [ramdisk/r0]

Regards,
baiqing
> -----Original Message-----
> From: Asias He [mailto:address@hidden
> Sent: Thursday, June 20, 2013 9:34 AM
> To: Libaiqing
> Cc: Paolo Bonzini; Wenchao Xia; address@hidden;
> address@hidden; Michael S. Tsirkin; Haofeng
> Subject: Re: [Qemu-devel] [PATCH 6/9] vhost-scsi: new device supporting the
> tcm_vhost Linux kernel module
> 
> On Wed, Jun 19, 2013 at 12:55:10PM +0000, Libaiqing wrote:
> > Hi paolo,
> >   The vhost-scsi device can be used as boot device?
> >   I tested with your config + 3.10 rc6 + seabios 1.7.2.2,but failed.
> >   Could you give me some advise to debug this problem ? I can provide
> more information if need.
> 
> Boot from vhost-scsi is supposed to work. The seabios you used should be
> fine which contains the fixes for vhost-scsi.
> 
> Instead of playing with the /sys/kernel/config/target directly, I really
> recommend using targetcli utils.
> 
> Nab, I think we really should write some docs for people to use
> vhost-scsi.
> 
> This is how I install and use targetcli in RHEL6. Note you need upstream
> kernel and qemu bits for vhost-scsi.
> 
> # yum groupinstall  'Development tools'
> # yum install python-devel epydoc python-simpleparse
> 
> # git clone git://github.com/agrover/rtslib-fb.git
> # git clone git://github.com/agrover/targetcli-fb.git
> # git clone git://github.com/agrover/configshell-fb.git
> # for i in rtslib-fb configshell-fb targetcli-fb; do
>       make -C $i rpm
>       yum localinstall $i/dist/*.noarch.rpm
>   done
> 
> In targetcli, create a backstore and vhost wwpn, e.g.
> # targetcli
> /> /backstores/ramdisk create r0 1g
> /> /vhost create
> /> cd /vhost/naa.500140527cb6616b/tpg1/luns
> /> create /backstores/ramdisk/r0
> 
> # qemu -device vhost-scsi-pci,wwpn=naa.500140527cb6616b ...
> 
> Hope this helps.
> 
> > Regards,
> > baiqing
> >
> > > -----Original Message-----
> > > From: address@hidden
> > > [mailto:address@hidden On
> > > Behalf Of Paolo Bonzini
> > > Sent: Tuesday, May 28, 2013 4:01 PM
> > > To: Wenchao Xia
> > > Cc: address@hidden; address@hidden; address@hidden;
> > > Michael S. Tsirkin
> > > Subject: Re: [Qemu-devel] [PATCH 6/9] vhost-scsi: new device supporting
> the
> > > tcm_vhost Linux kernel module
> > >
> > > Il 28/05/2013 09:13, Wenchao Xia ha scritto:
> > > >> > From: Nicholas Bellinger <address@hidden>
> > > >> >
> > > >> > The WWPN specified in configfs is passed to "-device
> vhost-scsi-pci".
> > > >> > The tgpt field of the SET_ENDPOINT ioctl is obsolete now, so it is 
> > > >> > not
> > > >> > available from the QEMU command-line.  Instead, I hardcode it to
> > > zero.
> > > >> >
> > > > Hi, Paolo
> > > >   Any document about how to config it correctly in configfs, before
> > > > invoking qemu with the WWPN number?
> > >
> > > Unfortunately no, but vhost-scsi doesn't have many knobs (unlike
> > > iSCSI for example) so it's quite simple.  Here is an example:
> > >
> > > cd /sys/kernel/config/target
> > > mkdir -p core/fileio_0/fileio
> > > echo
> 'fd_dev_name=/home/pbonzini/test.img,fd_dev_size=5905580032' >
> > > core/fileio_0/fileio/control
> > > echo 1 > core/fileio_0/fileio/enable
> > > mkdir -p vhost/naa.600140554cf3a18e/tpgt_0/lun/lun_0
> > > cd vhost/naa.600140554cf3a18e/tpgt_0
> > > ln -sf ../../../../../core/fileio_0/fileio/ lun/lun_0/virtual_scsi_port
> > > echo naa.60014053226f0388 > nexus
> > >
> > > The "nexus" value is the initiator WWN.  naa.600140554cf3a18e is the
> > > target WWN that you have to pass to "-device vhost-scsi-pci".
> > >
> > > Paolo
> >
> 
> --
> Asias



reply via email to

[Prev in Thread] Current Thread [Next in Thread]