From: Fam Zheng <famz@redhat.com>
To: Holger Schranz <holger@fam-schranz.de>
Cc: John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, mueller-ralf@t-online.de
Subject: Re: [Qemu-devel] Strange/wrong behavior with iSCSI Tape devices in QEMU 2.8.0-rc4
Date: Wed, 21 Dec 2016 07:47:38 +0800 [thread overview]
Message-ID: <20161220234738.GB2994@lemon> (raw)
In-Reply-To: <89d9fe09-3bdc-3c84-3ddf-f9462adb2068@fam-schranz.de>
On Tue, 12/20 17:53, Holger Schranz wrote:
> Hi John,
>
> sorry or late. I will reproduce it and send you the QEMU command line
> instruction.
>
> About the guest system: LINUX SuSE SLES11 SP4.
>
> About 2.7.0 Release: it doesn't run without the patches for the issue:
> [Qemu-devel] [PATCH] iscsi: Fix divide-by-zero regression on raw SG devices
>
> (I can't find the issue number).
Are there any related message showing up in guest dmesg?
Is it possible to do a git bisect?
Also, does it work if you login with host side iscsi client (iscsiadm) and pass
the /dev/sgX to QEMU?
Fam
>
> Best regards
>
> Holger
>
> Am 19.12.2016 um 18:30 schrieb John Snow:
> >
> > On 12/19/2016 04:05 AM, Holger Schranz wrote:
> > > # Strange/wrong behavior in QEMU 2.8.0-rc4
> > >
> > > After update from QEMU 2.6.2 to 2.8.0-rc4 the tape devices
> > > and the corresponding medium changer are no longer available
> > > in the VM quest system.
> > >
> > > The tape devices and the media changer are declared in the
> > > xml-file for libvirt. Both, tape drives and medium changer
> > > are avalilable via iSCSI.
> > >
> > > In a first rough investigation the login in iSCSI runs well
> > > but in QEMU, it seems the devices doesn't reported to the VM-Quest.
> > >
> > > ------------------
> > >
> > > Best regards
> > >
> > > Holger
> > >
> > Hi, thanks for the report; do you have a QEMU command line that we can
> > use to help reproduce the problem? It's easiest if we can cut libvirt
> > out of the loop.
> >
> > What is the architecture and version of the guest?
> >
> > Lastly, it looks like this worked in our 2.7 release if I'm reading you
> > correctly, so this is a change for the 2.8 release as far as you can
> > tell, right?
> >
> > --js
> >
> > > =====================================================================
> > >
> > > XML-Declration:
> > >
> > > .
> > > .
> > > .
> > >
> > > <!-- SCSI 2 -->
> > > <controller type='scsi' model='virtio-scsi' index='1'>
> > > <alias name='scsi1'/>
> > > </controller>
> > >
> > > <!-- 2 x LTO5 -->
> > > <hostdev mode='subsystem' type='scsi' managed='no' rawio='yes'>
> > > <source protocol='iscsi'
> > > name='iqn.2008-09.net.fsc:server.LT260_61003/4'>
> > > <host name='etcsvms2.abg.fsc.net' port='3260'/>
> > > </source>
> > > <address type='drive' controller='1' bus='0' target='2' unit='1'/>
> > > </hostdev>
> > >
> > > <hostdev mode='subsystem' type='scsi' managed='no' rawio='yes'>
> > > <source protocol='iscsi'
> > > name='iqn.2008-09.net.fsc:server.LT260_61003/5'>
> > > <host name='etcsvms2.abg.fsc.net' port='3260'/>
> > > </source>
> > > <address type='drive' controller='1' bus='0' target='2' unit='2'/>
> > > </hostdev>
> > >
> > > <!-- Virtual media changer Fujitsu LT260 -->
> > > <hostdev mode='subsystem' type='scsi' managed='no' rawio='yes'>
> > > <source protocol='iscsi'
> > > name='iqn.2008-09.net.fsc:server.LT260_61003/6'>
> > > <host name='etcsvms2.abg.fsc.net' port='3260'/>
> > > </source>
> > > <address type='drive' controller='1' bus='0' target='2' unit='3'/>
> > > </hostdev>
> > >
> > > <!-- 2 x LTO6 (via PLP(LAN-attached library)) -->
> > > <hostdev mode='subsystem' type='scsi' managed='no' rawio='yes'>
> > > <source protocol='iscsi'
> > > name='iqn.2008-09.net.fsc:server.LT60_61005/3'>
> > > <host name='etcsvms2.abg.fsc.net' port='3260'/>
> > > </source>
> > > <address type='drive' controller='1' bus='0' target='2' unit='4'/>
> > > </hostdev>
> > >
> > > <hostdev mode='subsystem' type='scsi' managed='no' rawio='yes'>
> > > <source protocol='iscsi'
> > > name='iqn.2008-09.net.fsc:server.LT60_61005/4'>
> > > <host name='etcsvms2.abg.fsc.net' port='3260'/>
> > > </source>
> > > <address type='drive' controller='1' bus='0' target='2' unit='5'/>
> > > </hostdev>
> > > .
> > > .
> > > .
> > >
> > > ===============================================================================
> > >
> > >
> > > correct behavior/Result inside the VM-Quest together with QEMU/KVM 2.6.2
> > > / 2.7.0
> > > --
> > > (VCSTCS82:A)IUP1:~ # lsscsi -g
> > > [0:2:0:0] disk FTS PRAID EP420i 4.25 /dev/sda /dev/sg0
> > > [3:0:0:0] cd/dvd QEMU QEMU DVD-ROM 2.5+ /dev/sr0 /dev/sg1
> > > [8:0:2:1] tape HP Ultrium 5-SCSI 0001 /dev/st3 /dev/sg6
> > > [8:0:2:2] tape HP Ultrium 5-SCSI 0001 /dev/st2 /dev/sg5
> > > [8:0:2:3] mediumx FUJITSU ETERNUS LT260 6.20 - /dev/sg4
> > > [8:0:2:4] tape HP Ultrium 6-SCSI 23AB /dev/st1 /dev/sg3
> > > [8:0:2:5] tape HP Ultrium 6-SCSI 23AB /dev/st0 /dev/sg2
> > > [11:0:0:0] disk FUJITSU ETERNUS_DXL 0000 /dev/sdb /dev/sg7
> > > [11:0:0:2] disk FUJITSU ETERNUS_DXL 0000 /dev/sdh /dev/sg13
> > > [11:0:0:3] disk FUJITSU ETERNUS_DXL 0000 /dev/sdg /dev/sg12
> > > [11:0:0:4] disk FUJITSU ETERNUS_DXL 0000 /dev/sdf /dev/sg11
> > > [11:0:0:5] disk FUJITSU ETERNUS_DXL 0000 /dev/sde /dev/sg10
> > > [11:0:0:6] disk FUJITSU ETERNUS_DXL 0000 /dev/sdd /dev/sg9
> > > [11:0:0:7] disk FUJITSU ETERNUS_DXL 0000 /dev/sdc /dev/sg8
> > > [11:0:0:15] disk FUJITSU ETERNUS_DXL 0000 /dev/sdi /dev/sg14
> > > (VCSTCS82:A)IUP1:~ #
> > >
> > >
> > >
> > > Wrong behavior/Result inside the VM-Quest together with QEMU/KVM 2.8.0-RC4
> > > --
> > > (VCSTCS82:A)IUP1:~ # lsscsi -g
> > > [0:2:0:0] disk FTS PRAID EP420i 4.25 /dev/sda /dev/sg0
> > > [3:0:0:0] cd/dvd QEMU QEMU DVD-ROM 2.5+ /dev/sr0 /dev/sg1
> > > [11:0:1:0] disk FUJITSU ETERNUS_DXL 0000 /dev/sdj /dev/sg10
> > > [11:0:1:2] disk FUJITSU ETERNUS_DXL 0000 /dev/sdp /dev/sg16
> > > [11:0:1:3] disk FUJITSU ETERNUS_DXL 0000 /dev/sdo /dev/sg15
> > > [11:0:1:4] disk FUJITSU ETERNUS_DXL 0000 /dev/sdn /dev/sg14
> > > [11:0:1:5] disk FUJITSU ETERNUS_DXL 0000 /dev/sdm /dev/sg13
> > > [11:0:1:6] disk FUJITSU ETERNUS_DXL 0000 /dev/sdl /dev/sg12
> > > [11:0:1:7] disk FUJITSU ETERNUS_DXL 0000 /dev/sdk /dev/sg11
> > > [11:0:1:15] disk FUJITSU ETERNUS_DXL 0000 /dev/sdq /dev/sg17
> > > (VCSTCS82:A)IUP1:~ #
> > >
>
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
>
>
next prev parent reply other threads:[~2016-12-20 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 9:05 [Qemu-devel] Strange/wrong behavior with iSCSI Tape devices in QEMU 2.8.0-rc4 Holger Schranz
2016-12-19 17:30 ` John Snow
2016-12-20 16:53 ` Holger Schranz
2016-12-20 23:47 ` Fam Zheng [this message]
2016-12-21 4:44 ` Holger Schranz
2016-12-21 11:51 ` Holger Schranz
2016-12-21 12:39 ` Holger Schranz
2016-12-22 6:22 ` Fam Zheng
2016-12-22 12:33 ` Holger Schranz
2016-12-22 13:06 ` Fam Zheng
2016-12-22 16:47 ` Paolo Bonzini
2016-12-22 18:21 ` Holger Schranz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161220234738.GB2994@lemon \
--to=famz@redhat.com \
--cc=holger@fam-schranz.de \
--cc=jsnow@redhat.com \
--cc=mueller-ralf@t-online.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.