similar to: Is there any plan to support SPDK disks?

I have been following the patches on nvme support on the list and was wondering: If I wanted to build a vm host to be on the bleeding edge for nvme and spdk fun in libvirt, which linux distro -- fedora/ubuntu/centos/etc -- should I pick?

On Thu, Dec 12, 2019 at 5:40 AM Michal Privoznik <mprivozn@redhat.com> wrote: > > On 11/27/19 4:12 PM, Mauricio Tavares wrote: > > I have been following the patches on nvme support on the list and was > > wondering: If I wanted to build a vm host to be on the bleeding edge > > for nvme and spdk fun in libvirt, which linux distro -- > > fedora/ubuntu/centos/etc

Hi All - I use qemu on my centOS 7.7 box that has software raid of 2- SSD disks. I installed an nVME drive in the computer also. I tried to insall CentOS8 on it (the physical /dev/nvme0n1 with the -hda /dev/nvme0n1 as the disk. The process started installing but is really "slow" - I was expecting with the nvme device it would be much quicker. Is there something I am missing how to

On 11/27/19 4:12 PM, Mauricio Tavares wrote: > I have been following the patches on nvme support on the list and was > wondering: If I wanted to build a vm host to be on the bleeding edge > for nvme and spdk fun in libvirt, which linux distro -- > fedora/ubuntu/centos/etc -- should I pick? > For NVMe itself it probably doesn't matter as it doesn't require any special

>6 hours are too much. First of all you need to check your nvme >performace (dd can help? dd if=/dev/zero of=/test bs=1M count=10000 andd >see results. If you want results more benchmark oriented you could try >bonnie++ as suggested by Jerry). >Other this, have you got kvm module loaded and enabled cpu >virtualization option in the BIOS? >If yes, have you got created the VM

On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <g.hooton at ucc.ie> wrote: > > Hi All, > I am having problems with a kickstart install of CentOS 8 > When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. > Then I see the following message > "kickstart install Started cancel waiting for multipath

Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1" This is what I have in the kickstart file # Clear the Master Boot Record zerombr #

Hello all, and hope all is well Has anyone installed / on an nvme ssd for Cent 7? Would anyone know if that is supported? I have installed using Arch Linux, but at the time, mid last year, had to patch grub to recognize nvme. Arch is obviously running a much more recent kernel. Not afraid todo some empirical leg work. Just asking if anyone had tried already thanks all for any/all help regards

On Wed, Jul 18, 2018 at 12:10:30PM +0800, Bob Chen wrote: > Considering that the technic of SPDK + QEMU is making progress toward > maturity. > > Personally I'd like to do the integration work. Not sure somebody would > mind to give me some clue on that? Because I'm not familiar with libguestfs > code structures. If qemu supports SPDK then we should get it "for

On 11/27/19 10:12 AM, Mauricio Tavares wrote: > I have been following the patches on nvme support on the list and was > wondering: If I wanted to build a vm host to be on the bleeding edge > for nvme and spdk fun in libvirt, which linux distro -- > fedora/ubuntu/centos/etc -- should I pick? IMO Fedora, most of libvirt is developed by @redhat people so there's plenty of Fedora

Forwarded to centos mailing list -----Original Messages----- From: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> Sent Time: 2018-10-30 14:06:00 (Tuesday) To: "storage performance development kit" <spdk at lists.01.org> Cc: centos at centos.org, qemu-discuss at nongnu.org Subject: Re: [SPDK] VM boot failed sometimes if using vhost-user-blk with spdk I enable debug of

Hi guys, During the last few weeks, I've been looking at how to use SPDK as QEMU's bootable rootfs disk. I managed to boot up a SPDK rootfs disk by using OVMF UEFI boot-loader. And in order to deploy the guest OS before start-up(which has a unrecognizable filesystem to the host), I have written a small patch for the libguestfs. It was based on Redhat's CentOS libguestfs-1.36.10 RPM,

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

Hi Rob & Mihai, I wrote vhost-nvme patches on top of Christoph's NVMe target. vhost-nvme still uses mmio. So the guest OS can run unmodified NVMe driver. But the tests I have done didn't show competitive performance compared to virtio-blk/virtio-scsi. The bottleneck is in mmio. Your nvme vendor extension patches reduces greatly the number of MMIO writes. So I'd like to push it

Hi Rob & Mihai, I wrote vhost-nvme patches on top of Christoph's NVMe target. vhost-nvme still uses mmio. So the guest OS can run unmodified NVMe driver. But the tests I have done didn't show competitive performance compared to virtio-blk/virtio-scsi. The bottleneck is in mmio. Your nvme vendor extension patches reduces greatly the number of MMIO writes. So I'd like to push it

hi guys, I thought I should ask before I start fiddling and break something - can we tell grub2 to add nvme device as an option to boot from? And if yes then what do tell grub? many thanks, L.

Hi Cole & Michal, I'm sorry for my late response, I just end my journey today. Thank your response, your suggestion is very helpful to me. I have added Michal in this mail, Michal helps me review my initial patchset. (https://www.spinics.net/linux/fedora/libvir/msg191339.html) All concern about this feature is the XML design. My original XML design exposes more details of Qemu.

On Fri, 2015-09-18 at 14:09 -0700, Nicholas A. Bellinger wrote: > On Fri, 2015-09-18 at 11:12 -0700, Ming Lin wrote: > > On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > > > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > > > Hi Ming & Co, > >

On Fri, 2015-09-18 at 14:09 -0700, Nicholas A. Bellinger wrote: > On Fri, 2015-09-18 at 11:12 -0700, Ming Lin wrote: > > On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > > > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > > > Hi Ming & Co, > >