similar to: qeum on centos 8 with nvme disk

>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

I have CentOS 8 install solely on one nvme drive and it works fine and relatively quickly. /dev/nvme0n1p4????????? 218G?? 50G? 168G? 23% / /dev/nvme0n1p2????????? 2.0G? 235M? 1.6G? 13% /boot /dev/nvme0n1p1????????? 200M? 6.8M? 194M?? 4% /boot/efi You might want to partition the device (p3 is swap) Alan On 13/10/2019 10:38, Jerry Geis wrote: > Hi All - I use qemu on my centOS 7.7 box that

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 #

Hi Alan, Yes I have partitioned similar - with a swap. but as I mentioned slow! What command line do you use ? Device Boot Start End Blocks Id System /dev/nvme0n1p1 2048 102402047 51200000 83 Linux /dev/nvme0n1p2 102402048 110594047 4096000 82 Linux swap / Solaris /dev/nvme0n1p3 110594048 112642047 1024000 6 FAT16

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.

> so you can try like: virt-install -n NAME -r mem --vcpus=N --accelerate >--os-type=X --os-variant=X --disk path=/dev/nvme0n1[pN] ...and so on. Is there a command for virt-manager stuff that is just like qemu? Just command line - I dont want the GUI popping up and all that stuff. I dont need it creating all other files - just a simple command line ? I have not found that yet with my

> How do you measure the slowness? Use fio or bonnie++ to share some number. By it taking more than 6 hours to "install" CentOS 8 in the guest :) Jerry

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?

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 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

>virt-install can be run with no GUI. You can set it up to >automatically start a serial console in case you need to interact with >the install. You can also use 'virsh' to edit VM configs from the >command line. Sure - I saw those - but I was looking for something just like the old qemu command line. Just boot up and run - Nothing added to a GUI interface. Nothing that I

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;

Hello there, Dell XPS-15-9560 laptop (SSD drive, UEFI, secure boot off).. Windows 10 pre-installed, CentOS7 installed in a separate partition and running for months w/o issue. Don't know what happened but at reboot yesterday (not even booted in Windows, just rebooted), grub has disappeared, booted in Windows by default, which apparently has taken over the UEFI boot. By booting from a USB

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, > >

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

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. Thanks, Bob