From: Paolo Bonzini <pbonzini@redhat.com>
To: Timon Wang <timonwst@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Don Koch <dkoch@verizon.com>,
libvirt-users <libvirt-users@redhat.com>,
kvm@vger.kernel.org
Subject: Re: Oracle RAC in libvirt+KVM environment
Date: Wed, 21 Aug 2013 11:09:37 +0200 [thread overview]
Message-ID: <521483D1.7040803@redhat.com> (raw)
In-Reply-To: <CAH+8FsxeCPJHe-HgJVGs3vz3NtQjiUp+u6rijW0+QkZh+g7ADg@mail.gmail.com>
Il 21/08/2013 04:11, Timon Wang ha scritto:
> From the fedora 19 host:
> [root@fedora ~]# sg_inq /dev/sdc
> standard INQUIRY:
> PQual=0 Device_type=0 RMB=0 version=0x05 [SPC-3]
> [AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=0
> SCCS=1 ACC=0 TPGS=1 3PC=0 Protect=0 [BQue=0]
> EncServ=0 MultiP=0 [MChngr=0] [ACKREQQ=0] Addr16=0
> [RelAdr=0] WBus16=1 Sync=1 Linked=0 [TranDis=0] CmdQue=1
> length=36 (0x24) Peripheral device type: disk
> Vendor identification: MacroSAN
> Product identification: LU
> Product revision level: 1.0
> Unit serial number: fd01ece6-8540-f4c7-0000-fe170142b300
>
> From the fedora 19 vm:
> [root@fedoravm ~]# sg_inq /dev/sdb
> standard INQUIRY:
> PQual=0 Device_type=0 RMB=0 version=0x05 [SPC-3]
> [AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=0
> SCCS=1 ACC=0 TPGS=1 3PC=0 Protect=0 [BQue=0]
> EncServ=0 MultiP=0 [MChngr=0] [ACKREQQ=0] Addr16=0
> [RelAdr=0] WBus16=1 Sync=1 Linked=0 [TranDis=0] CmdQue=1
> length=36 (0x24) Peripheral device type: disk
> Vendor identification: MacroSAN
> Product identification: LU
> Product revision level: 1.0
> Unit serial number: fd01ece6-8540-f4c7-0000-fe170142b300
>
> The result from fedora 19 host and fedora 19 vm are the same. It's
> that means I got a wrong windows vm scsi pass-through driver?
> Or is there any tool like sg_inq in windows 2008?
Yeah, there's something weird in the Windows VM.
sg_inq should be available for Windows too, but I don't know where to
get a precompiled binary from.
Paolo
next prev parent reply other threads:[~2013-08-21 9:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 5:58 Oracle RAC in libvirt+KVM environment Timon Wang
2013-08-08 7:54 ` Timon Wang
[not found] ` <CAH+8Fsxhgkd2ScivXcPc7WzXyie4AHUsuNvLEUgo2rvTBtzdNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-08 14:04 ` Don Koch
2013-08-10 3:14 ` Timon Wang
2013-08-12 9:53 ` Stefan Hajnoczi
[not found] ` <20130812095304.GE29880-lxVrvc10SDTaErKTczak/Dh473NlOPsLVpNB7YpNyf8@public.gmane.org>
2013-08-12 10:17 ` Timon Wang
2013-08-13 9:18 ` Stefan Hajnoczi
2013-08-14 6:33 ` Timon Wang
2013-08-14 8:40 ` Timon Wang
2013-08-14 14:02 ` Stefan Hajnoczi
2013-08-15 10:01 ` Timon Wang
2013-08-19 11:10 ` Paolo Bonzini
2013-08-20 6:00 ` Timon Wang
2013-08-20 6:05 ` Timon Wang
2013-08-20 8:33 ` Paolo Bonzini
2013-08-20 9:59 ` Timon Wang
2013-08-20 10:16 ` Paolo Bonzini
2013-08-20 10:42 ` Timon Wang
2013-08-20 10:49 ` Paolo Bonzini
2013-08-20 11:43 ` Timon Wang
2013-08-20 11:57 ` Timon Wang
2013-08-20 12:09 ` Paolo Bonzini
2013-08-21 2:11 ` Timon Wang
2013-08-21 9:09 ` Paolo Bonzini [this message]
2013-08-21 9:40 ` Nicholas A. Bellinger
2013-08-22 7:46 ` Timon Wang
2013-08-22 9:02 ` Paolo Bonzini
2013-08-23 2:44 ` Timon Wang
2013-08-27 10:29 ` Masaki Kimura
2013-08-27 11:07 ` Paolo Bonzini
2013-08-27 12:09 ` Timon Wang
2013-08-12 9:49 ` Stefan Hajnoczi
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=521483D1.7040803@redhat.com \
--to=pbonzini@redhat.com \
--cc=dkoch@verizon.com \
--cc=kvm@vger.kernel.org \
--cc=libvirt-users@redhat.com \
--cc=stefanha@gmail.com \
--cc=timonwst@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).