ossicle

Members
  • Posts

    3
  • Joined

Everything posted by ossicle

  1. The <hostdev> block goes towards the end of the XML, inside the <devices> block, between the <video> and <memballoon> blocks. Here are the last lines of my XML: [...] <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host6'/> <address bus='0' target='0' unit='0'/> </source> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>
  2. Harmani, that sounds frustrating.... First thing to check, did you change the XML code to match the SCSI device number? In my system the drive address is [6:0:0:0], so I used <adapter name='scsi_host6'/> in the XML. Your system is likely different. If you can post the system info and XML that would help us troubleshoot your issue.
  3. I've been trying to do this on Unraid 6.8.1 this week... I finally got it to work and thought I'd share my results. I'm able to pass through a SATA BluRay drive to Ubuntu and Windows 10 VMs, and I can read CD/DVD/BluRay. I haven't tested burning yet. First I had to connect the drive directly to a SATA port on my motherboard rather than through my SAS HBA. It might be possible to pass it through the HBA but it wasn't working, and seemed like that might be adding an additional hurdle. Here is the drive's SCSI address from Tools/System Devices: SCSI Devices ... [6:0:0:0] cd/dvd HL-DT-ST BD-RE WH14NS40 1.03 /dev/sr0 - This addition to the Windows 10 VM XML works for me: <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host6'/> <address bus='0' target='0' unit='0'/> </source> <readonly/> <alias name='hostdev0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> And this VM XML addition works for me on Ubuntu 18.04.03 VM: <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host6'/> <address bus='0' target='0' unit='0'/> </source> <readonly/> <address type='drive' controller='2' bus='0' target='0' unit='0'/> </hostdev> Note that controller='2' here for the Ubuntu VM.... other users suggested using 0 or 1, which for me gave UEFI errors on VM boot. Controller 2 seems to work for me. (Not sure why there's a difference between the Windows 10 and Ubuntu VMs on this.)