Hi all!
Recently I've found myself adding my first VM on a FreeNAS 12 bare metal.
It is a Windows 2019, where I would run the software "roon".
I am not happy with the disk performance, and trying to use the VirtIO drivers does not make the system boot anymore.
So, following the "roon" hardware guidelines, I want to dedicate an SSD to this VM. In this case my NVME.
Running
So I added the following tunables (type loader):
vmm_load =true
pptdevs2 = 0/4/0
vmm_after = kldload if_re
if_re_load = NO
Then I rebooted and, if I understood correctly, the device should be not showed in dmesg.
So I run...
The NVMe is also still visible and could be used to create a new pool, so it seems it has not been reserved for bhyve.
On the VM section of TrueNAS I don't see the nvme device
I tried then the following commands, curious that the same input generated different outputs...
Any advice? I would really like to avoid implementing ESXi just for a single VM (an additional system to manage, keep updated, etc).
After rebooting the system, I run the following command
Recently I've found myself adding my first VM on a FreeNAS 12 bare metal.
It is a Windows 2019, where I would run the software "roon".
I am not happy with the disk performance, and trying to use the VirtIO drivers does not make the system boot anymore.
So, following the "roon" hardware guidelines, I want to dedicate an SSD to this VM. In this case my NVME.
Running
pciconf -v -l
allows me to identify the device: "nvme0@pci0:4:0:0: class=0x010802 card=0xa801144d chip=0xa808144d rev=0x00 hdr=0x00"
So I added the following tunables (type loader):
vmm_load =true
pptdevs2 = 0/4/0
vmm_after = kldload if_re
if_re_load = NO
Then I rebooted and, if I understood correctly, the device should be not showed in dmesg.
So I run...
dmesg | grep nvme
nvme0: <Generic NVMe Device> mem 0xdf400000-0xdf403fff irq 16 at device 0.0 on pci4
nvme0: <Generic NVMe Device> mem 0xdf400000-0xdf403fff irq 16 at device 0.0 on pci4
The NVMe is also still visible and could be used to create a new pool, so it seems it has not been reserved for bhyve.
On the VM section of TrueNAS I don't see the nvme device
I tried then the following commands, curious that the same input generated different outputs...
root@freenas:~ # bhyve -S -s 7,passthru,0/4/0 WinServer
virtual machine cannot be booted
root@freenas:~ # bhyve -S -s 7,passthru,0/4/0 WinServer
bhyve: PCI device at 0/4/0 is not using the ppt(4) driver
device emulation initialization error: No such file or directory
root@freenas:~ # bhyve -S -s 7,passthru,0/4/0 WinServer
Unable to setup memory (17)
root@freenas:~ # bhyve -S -s 7,passthru,0/4/0 WinServer
Unable to setup memory (17)
root@freenas:~ # bhyve -S -s 7,passthru,0/4/0 WinServer
Unable to setup memory (17)
Any advice? I would really like to avoid implementing ESXi just for a single VM (an additional system to manage, keep updated, etc).
After rebooting the system, I run the following command
bhyve -S -s 7,passthru,0/4/0 WinServer
Unable to setup memory (17)