Re: to enable nvme
| Newsgroups | gmane.linux.debian.ports.hurd |
|---|---|
| Message-ID | <[email protected]> |
On 8/7/26 11:48, Samuel Thibault wrote: > Hello, > > [email protected], le ven. 07 août 2026 15:35:41 +0000, a ecrit: >> On 8/6/26 18:13, Samuel Thibault wrote: >>>> Is it appropriate to send screenshot attachments in this list? >>> Sure! >>> >> I tried to send a e-mail that did not seem to get through. > The snapshot went through. It indeed shows that the nvme PCI device is > unconfigured. You'd want to check with lspci from a linux live image how > the device looks exactly and how the rump drivers should be able to > detect it. > > Samuel What made it more difficult for me was that I had VT-D enabled in the bios. Disabling that, enabled AHCI which made RAID go away that I could bind the device easily. I was able to boot to the login screen with from the disk using qemu command: qemu-system-x86_64 -drive file=nvme://0000:01:00.0/1 -m 8G -accel kvm -net user,hostfwd=tcp:127.0.0.1:2222-:22 -display spice-app I didn't change the name from wd0. cfdisk reports that the disk /dev/wd0 has 917.6 GB of free space on the device which I believe is accurate. For some reason I am unable to connect to ssh. Is there something else that I should test from this disk that would help us to know if works? Is rumpdisk managing the memory too? I see that it does 8G of memory without a problem. It was crashing above 3G on my virtual machine before.