frodr Posted September 22, 2019 Share Posted September 22, 2019 (edited) I am running a MacOS kvm with a primary vdisk and a nvme ssd passed thru (the controller). I have cloned the nvme drive with Carbon Copy Cloner. How do I make the nvme ssd the startup drive? Very happy for any help. Supermicro X11DAI-N, version 1.02 | AMI 3.1 | dual Xeon Silver 4116 | 64 MB RAM | 4 x WD SSD in RAID 10 Cache l Unraid 6.72 l Quadro RTX4000 for Plex docker l GTX 1070 for MacOS kvm l Samsung 970 Pro nvme for MacOS kvm Edited September 22, 2019 by frodr Quote Link to comment
david279 Posted September 22, 2019 Share Posted September 22, 2019 Add this too where you have the nvme device <boot order='1'/> Quote Link to comment
frodr Posted September 22, 2019 Author Share Posted September 22, 2019 15 minutes ago, david279 said: Add this too where you have the nvme device <boot order='1'/> Thanks. This is the only text added to the xml with reference to the nvme controller: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x1a' slot='0x00' function='0x0'/> </source> </hostdev> Can you tell me where it should be added, please? Quote Link to comment
david279 Posted September 22, 2019 Share Posted September 22, 2019 You can put it in before the address line. Quote Link to comment
frodr Posted September 22, 2019 Author Share Posted September 22, 2019 5 minutes ago, david279 said: You can put it in before the address line. Like this? <hostdev mode='subsystem' type='pci' managed='yes'> <source> <boot order='1'/> <address domain='0x0000' bus='0x1a' slot='0x00' function='0x0'/> </source> </hostdev> Quote Link to comment
david279 Posted September 22, 2019 Share Posted September 22, 2019 That should work Quote Link to comment
frodr Posted September 22, 2019 Author Share Posted September 22, 2019 6 minutes ago, david279 said: That should work I got this message. High up in the xml it says: <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b6d807ac-76fd-78a5-3710-fe431bb5832b_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> With a reference to current/old bott drive. Quote Link to comment
david279 Posted September 22, 2019 Share Posted September 22, 2019 Yeah you will have to remove the other boot line. I had a nvme passed throughto a VM before so I went thru this. Quote Link to comment
frodr Posted September 22, 2019 Author Share Posted September 22, 2019 5 minutes ago, david279 said: Yeah you will have to remove the other boot line. I had a nvme passed throughto a VM before so I went thru this. Removed: <boot dev='hd'/> Still the same error message: internal error........... Quote Link to comment
david279 Posted September 22, 2019 Share Posted September 22, 2019 Try it under the address line Quote Link to comment
frodr Posted September 23, 2019 Author Share Posted September 23, 2019 3 hours ago, david279 said: Try it under the address line Removing the boot line in the OS section, I can same the xml file and start up the kvm. But I cannot connect, assuming that the nvme id not starting. I have set the <boot order='1'/> over, under, in between, etc. What does the 1 refer to? Quote Link to comment
david279 Posted September 23, 2019 Share Posted September 23, 2019 It sets the nvme drive as the boot drive for the VM. Without it you will just boot to the UEFI Shell. Quote Link to comment
frodr Posted September 23, 2019 Author Share Posted September 23, 2019 Strange things happened. Setting <boot order='1'/> just above the address domain line, and the xml would not update. Trying again with <boot order='1'/> above source and the xml was able to update. Then checking the xml, and the <boot order='1'/> was under the <source> line. <hostdev mode='subsystem' type='pci' managed='yes'> <source> <boot order='1'/> <address domain='0x0000' bus='0x1a' slot='0x00' function='0x0'/> </source> </hostdev> The <boot order='1'/> line also moved when introduced vdisk again. And did not go away changing the xml in Form View. I was not able to save the kvm after this. I will have to make a new kvm from scratch. Thanks for the help so far, I will be back in a day or three. Cheers, Quote Link to comment
frodr Posted September 25, 2019 Author Share Posted September 25, 2019 (edited) Hi, New MacOS kvm is up and running, Nvidia GPU and nvme ssd are passthrough, and works fine. I would like to passthrough usb and boot from the nvme ssd as well. In the xml form view a USB Aten International is selectable, but I can not connect to the kvm (it starts) when enabled. Disabling it, and I can again connect to the kvm. It is no pci usb in the server, only the onboard ones. System Devices show different usb devices, how can I pass some of them through? The other topic is how to boot from the nvme ssd. A MacOS spesific setup of SIO`s Windows solution would be nice. Appreciate any help. Edited September 25, 2019 by frodr Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.