Re: [Qemu-discuss] kvm instance hangs at boot while starting with iSCSI

[Josef Johansson]

----- Original Message -----
From: "Charles Chou" <address@hidden>
To: "Josef Johansson" <address@hidden>
Cc: address@hidden
Sent: Wednesday, June 13, 2012 11:47:10 PM
Subject: Re: [Qemu-discuss] kvm instance hangs at boot while starting with iSCSI

On 6/13/2012 11:37 AM, Josef Johansson wrote:
>
> ----- Original Message -----
> From: "Charles Chou"<address@hidden>
> To: "Josef"<address@hidden>
> Cc: address@hidden
> Sent: Wednesday, June 13, 2012 9:56:23 PM
> Subject: Re: [Qemu-discuss] kvm instance hangs at boot while starting with 
> iSCSI
>
> On 6/13/2012 7:43 AM, Josef wrote:
>> Hi,
>>
>> Ok, I will try that later tonight, thanks.
>>
>> I have it working with open-iscsi already so that should not be a problem.
>>
>> /Josef
>>
>> ------------------------------------------------------------------------
>> *From:* Charles Chou
>> *Sent:* Wed, 13/06/2012 19:39
>> *To:* address@hidden
>> *Subject:* Re: [Qemu-discuss] kvm instance hangs at boot while
>> starting with iSCSI
>>
> Hi,
>       After reading the source some more I think iscsi is a top level
> option so you may want to try:
>
> -iscsi initiator-name=some_name -drive
> file=iscsi://[xxxx:xxxx:xxxx::3]:3260/iqn.2010-08.xx.xxx.xxxxxxx.pool10-images/10,....
>
>       Also I am curious as to whether it performs better than using
> virtio on a block device that is created by the open-iscsi initiator.
>
> Charles Chou
>
>
> --
>
> Where do you see -iscsi initiator-name? Maybe we're looking at different 
> sources. I see this:
>
>      /* Should really append the KVM name after the ':' here */
>      iscsi = iscsi_create_context("iqn.2008-11.org.linux-kvm:");
>      if (iscsi == NULL) {
>          error_report("iSCSI: Failed to create iSCSI context.");
>          ret = -ENOMEM;
>          goto failed;
>      }
>
> And it isn't possible to define the parameter initiator-name anywhere. I'll 
> see if it works with qemu-kvm 1.1.
>
> Regards,
> Josef
I am reading vl.c and qemu-config.c off the 1.1.0 tree and it seems 
QEMU_OPTION_iscsi is at the same level as QEMU_OPTION_net
and in qemu-config.c you see the options for iscsi in qemu_iscsi_opts().


--

OK, so I tried QEMU-KVM 1.1 with -iscsi initiator_name=iqn.... -drive 
file=iscsi://..., still 100% CPU.

So, I have another vector to try, and that is another iSCSI-implementation at 
the server end.

Running against 'SCSI Target Mode Framework (STMF) framework' seems like 
trouble, and running against 'iSCSI Enterprise Target' works.

So maybe libiscsi isn't sending enough data, I'm guessing a wiretap will reveal 
that!

Regards,
Josef