All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lin Ma" <lma@suse.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
	Zhiqiang Zhou <ZZhou@suse.com>,
	hare@suse.de
Subject: [Qemu-devel] [RFC] virtio-fc: draft idea of virtual fibre channel HBA
Date: Wed, 15 Feb 2017 00:15:02 -0700	[thread overview]
Message-ID: <58A4707602000062000D0393@prv-mh.provo.novell.com> (raw)

Hi all,
 
We know that libvirt can create fibre channels vHBA on host
based on npiv, and present the LUNs to guest.
 
I'd like to implement a virtual fibre channel HBA for qemu,
I havn't investigate it deeply yet. The idea presents a fc
vHBA in guest, interact with remote fc switch through npiv,
The LUNs will be recognized inside guest. I sent this email
here to see if you are in agreement with this approach and
hope to get some ideas/suggestions.
 
The frontend is based on virtio, say virtio-fc-pci; the backend
is based on npiv of physical fc hba on host.
The implementation of this virtual fc hba doesn't support Fc-al,
only supports Fabric. It wrappers scsi data info fc frames, then
forwards them to backend, sounds like scsi over fc.
(maybe I can re-use some of virtio-scsi code/idea to deal with scsi data)
 
The minimum invocation may look like:
qemu-system-x86_64 \
...... \
-object fibrechannel-backend,id=fcdev0,host=0000:81:00.0 \
-device virtio-fc-pci,id=vfc0,fc_backend=fcdev0,wwpn=1000000000000001,wwnn=1100000000000001 \
......
 
BTW, I have no idea how to make migration works:
How to deal with the BDF during migration?
How to deal with the Fabric ID during migration?
 
It's a draft idea, There are lots of related code I need to
investigate, Currently this is all thoughts I have.
 
Hello Paolo and Stefan, You are the authors of virtio-scsi,
and had some in-depth discuss about virtio-scsi in 2011
with Hannes, May I have your ideas/thoughts?
 
Thanks,
Lin

             reply	other threads:[~2017-02-15  7:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  7:15 Lin Ma [this message]
2017-02-15 15:33 ` [Qemu-devel] [RFC] virtio-fc: draft idea of virtual fibre channel HBA Stefan Hajnoczi
2017-02-16  7:16   ` [Qemu-devel] 答复： " Lin Ma
2017-02-16  8:39     ` Paolo Bonzini
2017-02-16  9:02       ` Lin Ma
2017-02-16  9:56       ` Hannes Reinecke
2017-02-22  8:19         ` Lin Ma
2017-02-22  9:20           ` Hannes Reinecke
2017-05-15 17:21             ` Paolo Bonzini
2017-05-16  6:34               ` Hannes Reinecke
2017-05-16  8:19                 ` Paolo Bonzini
2017-05-16 15:22                   ` Hannes Reinecke
2017-05-16 16:22                     ` Paolo Bonzini
2017-05-17  6:01                       ` Hannes Reinecke
2017-05-17  7:33                         ` Paolo Bonzini

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=58A4707602000062000D0393@prv-mh.provo.novell.com \
    --to=lma@suse.com \
    --cc=ZZhou@suse.com \
    --cc=hare@suse.de \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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.