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: Tue, 20 Aug 2013 12:49:20 +0200 [thread overview]
Message-ID: <521349B0.60103@redhat.com> (raw)
In-Reply-To: <CAH+8FswZd_VNr5QCOMssUtTc+=apWWgxUyfxxO8U6akJduXVBA@mail.gmail.com>
Il 20/08/2013 12:42, Timon Wang ha scritto:
> [root@localhost /]# ls -l /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk
> lrwxrwxrwx. 1 root root 8 8月 20 17:38
> /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk -> ../dm-13
> [root@localhost /]# sg_inq /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk
> 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: 0d9281ae-aea4-6da0-0000-02180142b300
>
> This lun is from a vg build based on iscsi target.
If it is a logical volume, you cannot pass it as a LUN to the guest.
Only the whole iSCSI LUN can be passed as a LUN.
Paolo
> [root@localhost /]# libvirtd --version
> libvirtd (libvirt) 1.0.5
> [root@localhost /]# qemu-kvm --version
> QEMU emulator version 1.4.1, Copyright (c) 2003-2008 Fabrice Bellard
> [root@localhost /]# uname -a
> Linux localhost.localdomain 3.9.2-301.fc19.x86_64 #1 SMP Mon May 13
> 12:36:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>
> On Tue, Aug 20, 2013 at 6:16 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 20/08/2013 11:59, Timon Wang ha scritto:
>>> On Tue, Aug 20, 2013 at 4:33 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>> Il 20/08/2013 08:00, Timon Wang ha scritto:
>>>>> <disk type='file' device='disk'>
>>>>> <driver name='qemu' type='raw' cache='none'/>
>>>>> <source file='/home/images/win2008_2_sys'/>
>>>>> <target dev='hda' bus='ide'/>
>>>>> <boot order='3'/>
>>>>> <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>>>>> </disk>
>>>>> <disk type='file' device='cdrom'>
>>>>> <driver name='qemu' type='raw'/>
>>>>> <source file='/home/isos/windows2008_64r2.iso'/>
>>>>> <target dev='sdc' bus='ide'/>
>>>>> <readonly/>
>>>>> <boot order='1'/>
>>>>> <address type='drive' controller='0' bus='1' target='0' unit='0'/>
>>>>> </disk>
>>>>> <disk type='block' device='disk'>
>>>>
>>>> I'm not sure this will be enough, but if you want passthrough to the
>>>> host device you should use device='lun' here. However, you still would
>>>> not be able to issue SCSI reservations unless you run QEMU with the
>>>> CAP_SYS_RAWIO capability (using "<disk ... rawio='yes'>").
>>>>
>>>
>>> After change the libvirt xml like this:
>>> <disk type='block' device='lun' rawio='yes'>
>>> <driver name='qemu' type='raw' cache='none'/>
>>> <source dev='/dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk'/>
>>> <target dev='sda' bus='scsi'/>
>>> <shareable/>
>>> <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>>> </disk>
>>> I got these errors:
>>> char device redirected to /dev/pts/1 (label charserial0)
>>> qemu-system-x86_64: -device
>>> scsi-block,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0:
>>> scsi-block: INQUIRY failed
>>> qemu-system-x86_64: -device
>>> scsi-block,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0:
>>> Device 'scsi-block' could not be initialized
>>
>> Can you do
>>
>> # ls -l /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk
>> # sg_inq /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk
>>
>> ?
>>
>> Paolo
>>
>
>
>
next prev parent reply other threads:[~2013-08-20 10:50 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 [this message]
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
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=521349B0.60103@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).