search for: nvme0n1

Hi all. In recent hardware the first disk has device name nvme0n1 rather then sda How do you tell kickstart to use the first available disk? No matter if it is called sda or nvme0n1? e.g. part /boot --fstype="xfs" --ondisk=sda --size=1000 Regards ....Volker

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 get a faster disk access ? Thanks, Jerry

...e partition under C7.7 and ran the nvme test. Pretty much came back in seconds for 10G test. dd if=/dev/zero of=test bs=1M count=10000 10000+0 records in 10000+0 records out 10485760000 bytes (10 GB) copied, 5.45451 s, 1.9 GB/s Yes kvm_intel is loaded as a module. I am using the "-hda /dev/nvme0n1" when I run qemu.... I'm thinking this works find for my other "img" files - but does not work for "well" for my physical NVME. What is the correct argument perhaps to use for running a physical NVME disk as a qemu guest ?? Thanks, Jerry

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 # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================ When I install from a USB drive it works OK and I have the following in /dev/disk/by-id...

...ving 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" > The above says that the system thinks your box is multipath but the other drives are not showing up correctly. You will need to provide a lot more information for anyone to be able to help diagnosis this for you: 1. What is the build system 2. What kind of drives/drive controller is 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

On Mon, Feb 5, 2018 at 8:27 AM, Kay Diederichs <kay.diederichs at uni-konstanz.de> wrote: > grub-install /dev/nvme0n1 Running this on computers with UEFI firmware is not good advice, it's an obsolete command. People should use the prebaked grubx64.efi binary that comes in the grub2-efi package, and is a signed binary so it can support UEFI Secure Boot. If you run grub2-install, a new unsigned grub binary is...

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 has s...

hi list, i am trying to change the input and output scheduler on my disks, and it does not allow me , I have several virtualized vm over kvm, and when I try to make the change it shows me this message: echo "noop" > /sys/block/vda/queue/scheduler -bash: echo: write error: Invalid argument kernel version: 3.10.0-1127.13.1.el7.x86_64 any idea? -- rickygm

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

...ls, and leads to the loss of the grub menu, and restoration of the (non-grub) "Windows boot manager" (or whatever it's called). After being bit by it once, I disabled it. HTH, Kay P.S. I recovered my Ubuntu grub menu by booting from the Ubuntu live USB, and then sudo su mount /dev/nvme0n1p7 /mnt cd /mnt mount /dev/nvme0n1p1 boot/efi mount --bind /proc proc mount --bind /sys sys mount --bind /dev dev chroot /mnt grub-install /dev/nvme0n1 update-grub On CentOS, the last two lines would be grub2-install /dev/nvme0n1 grub2-mkconfig -o etc/grub2.cfg > > By booting from a USB...

...re any > special library. However, I'm not so sure about SPDK, esp. whether my > NVMe patches is what you really need? My patches enable the only missing > combination: > > host kernel storage stack + qemu storage stack = <disk type='block> > <source dev='/dev/nvme0n1'/> </disk> > This has disadvantage of latency added by both stacks, but allows > migration. > > neither host kernel nor qemu storage stack = <hostdev/> (aka PCI assignment) > This offers near bare metal latencies, but prohibits migration. > > qemu stora...

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

...unsigned size, bool match_data, uint64_t data, EventNotifier *e) Could you help to explain what "match_data" and "data" mean? I use a real NVMe device as backend. -drive file=/dev/nvme0n1,format=raw,if=none,id=D22 \ -device nvme,drive=D22,serial=1234 Here is the test results: local NVMe: 860MB/s qemu-nvme: 108MB/s qemu-nvme+google-ext: 140MB/s qemu-nvme-google-ext+eventfd: 190MB/s root at wheezy:~# cat test.job [global] bs=4k ioengine=libaio iodepth=64 direct=1 runtime=60 time_b...

...problem with thinly provisioned logical volumes and I wondered if anyone can explain why it happens and if and how can be fixed. The behavior is the same on Centos 6.8 and Centos 7.2. I have a NVME card (Intel DC P3600 -2 TB) on which I create a thinly provisioned logical volume: pvcreate /dev/nvme0n1 vgcreate vgg /dev/nvme0n1 lvcreate -l100%FREE -T vgg/thinpool lvcreate -V40000M -T vgg/thinpool -n brick1 mkfs.xfs /dev/vgg/brick1 If I run a write test ( dd if=/dev/zero of=./zero.img bs=4k count=100000 oflag=dsync ) I see in iotop that the actual disk write is 30 times the amount of data tha...

...v (LBA, length) | .----------------------------------------------------------------------. | LIO backend driver | | - fileio (/mnt/xxx.file) | | - iblock (/dev/sda1, /dev/nvme0n1, ...) | '----------------------------------------------------------------------' | ^ | submit_bio() | v | .----...

...v (LBA, length) | .----------------------------------------------------------------------. | LIO backend driver | | - fileio (/mnt/xxx.file) | | - iblock (/dev/sda1, /dev/nvme0n1, ...) | '----------------------------------------------------------------------' | ^ | submit_bio() | v | .----...

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;