January 20, 20206 yr 37 minutes ago, rmp5s said: No matter what I do, the only options available are raw and qcow2...whatever that is... You can edit the xml to change it - switch from form view to xml view with the toggle at the top of the page.
January 20, 20206 yr Author 7 minutes ago, John_M said: You can edit the xml to change it - switch from form view to xml view with the toggle at the top of the page. Ooo...that's right. Lemme give that a shot. Thanks.
January 20, 20206 yr 53 minutes ago, rmp5s said: No matter what I do, the only options available are raw and qcow2...whatever that is... Sorry meant: Primary vDisk Bus: Sata
January 20, 20206 yr Author 23 minutes ago, jpowell8672 said: Sorry meant: Primary vDisk Bus: Sata Tried that. Doesn't make any difference.
January 20, 20206 yr Author 36 minutes ago, John_M said: You can edit the xml to change it - switch from form view to xml view with the toggle at the top of the page. Like this?
January 20, 20206 yr 10 minutes ago, rmp5s said: Like this? <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_860_S3Z1NB0M229066F' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk>
January 20, 20206 yr On 10/31/2019 at 1:09 PM, rmp5s said: I have a W10 VM that I use (try to use, anyway...) to render videos in Adobe. It's just on the array and the disk speeds are SO...INCREDIBLY...SLOW...that it takes an unbelievably long time to render. I stopped a render yesterday after over 2 hours because it was BARELY making progress...my flaccid dual core laptop did the entire render in that same amount of time. At the rate the server was going, it would seriously have taken 10 hours?...maybe 12? I don't even know. It's INCREDIBLY slow and, when I look at resource manager, I notice the disk access is pegged. Disk speeds seem to be the culprit. So...I have a spare Samsung 860 Evo laying around. This got me thinking, how could I install it and dedicate it to the VM? What I'm wondering is, is it possible to assign that disk ONLY to that VM? Maybe using "unassigned devices"? Also, would it be possible to move the VM onto the SSD after I install it or will I have to create a new VM? No big deal if I have to reroll a new VM. Thank you!! Are you setting up a new Windows 10 VM or trying to convert your original VM to your dedicated SSD?
January 20, 20206 yr Author 1 minute ago, jpowell8672 said: Are you setting up a new Windows 10 VM or trying to convert your original VM to your dedicated SSD? Trying to convert. Already DD'd the vdisk to the SSD. Just trying to get the VM to use the SSD now.
January 20, 20206 yr Author Getting this error now. IThinking I don't have the disk ID correct. I copied it from the main page...is there another place to see the disk ID?
January 20, 20206 yr 3 minutes ago, rmp5s said: Trying to convert. Already DD'd the vdisk to the SSD. Just trying to get the VM to use the SSD now. Since you are having so much trouble, setting up a fresh Windows 10 VM using your SSD would likely be much easier for you.
January 20, 20206 yr Author Just now, jpowell8672 said: Since you are having so much trouble, setting up a fresh Windows 10 VM using your SSD would likely be much easier for you. Yea, could be. This really hasn't been THAT bad so far, though. And it's looking like this is the last piece of it. If I can't get this to work, I can definitely roll a new server. No problem.
January 20, 20206 yr 19 minutes ago, rmp5s said: Getting this error now. IThinking I don't have the disk ID correct. I copied it from the main page...is there another place to see the disk ID? Yes. SSH into your server (or open Command Line from Tools) to navigate to the directory, type cd /dev/disk/by-id The, to list all your disks, type ls You'll see something like this; Find your disk, and select the first instance of it (none of the 'part' bits). Select up to, but not including, the '@''. That's your ID. (I've highlighted one in the first column, above). I set up many of my VMs like this with dedicated SSDs. Here's an example of one of my passthroughs, for reference; <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-CT240BX500SSD1_1923E18670CA'/> <target dev='hdd' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> Good luck PS: check you have the type set to 'block', not 'file' when using /disk/by-id. Your latest error indicates you might have it set to file? Edited January 20, 20206 yr by meep
January 20, 20206 yr https://wiki.unraid.net/index.php/UnRAID_6/VM_Management#Using_a_physical_disk_in_a_VM.2C_including_one_with_an_OS_already_installed
January 20, 20206 yr Author 7 minutes ago, meep said: You'll see something like this; Find your disk, and select the first instance of it (none of the 'part' bits). Select up to, but not including, the '@''. That's your ID. (I've highlighted one in the first column, above). Good luck PS: check you have the type set to 'block', not 'file' when using /disk/by-id. Your latest error indicates you might have it set to file? Simple enough!! Up until...any tips on telling which disk is which? lol I have no clue which is the SSD. And, yup, it was set to block, not file already.
January 20, 20206 yr Author 6 minutes ago, jpowell8672 said: https://wiki.unraid.net/index.php/UnRAID_6/VM_Management#Using_a_physical_disk_in_a_VM.2C_including_one_with_an_OS_already_installed I'll go this route if I can't get all I've already done to work. I feel like I'm so close!!
January 20, 20206 yr Ok so you are just putting your Windows 10 VM image on the SSD not installing Windows 10 to SSD. <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/vdisk_share/vmname/vdisk1.img'/> <backingStore/> <target dev='hda' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk>
January 20, 20206 yr <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_860_S3Z1NB0M229066F' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk>
January 20, 20206 yr Author 2 minutes ago, jpowell8672 said: <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_860_S3Z1NB0M229066F' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> Tried that already. It gives the error above. I believe I have the device ID wrong. I tried looking it up using the method above but I have no idea how to tell which device is which.
January 20, 20206 yr 2 minutes ago, rmp5s said: Tried that already. It gives the error above. I believe I have the device ID wrong. I tried looking it up using the method above but I have no idea how to tell which device is which. Main Tab> Unassigned Devices Identification is ID
January 20, 20206 yr Author 1 minute ago, jpowell8672 said: Main Tab> Unassigned Devices Identification is ID That's what I thought. That's what I've been using and it's giving me an error. Then, when I do the "dev/disk/by-id/" thing, I don't see that disk ID anywhere...at all... Very confusing...
January 20, 20206 yr You could have installed a new VM already as suggested earlier but I guess this is a learning lesson if time does not matter.
January 20, 20206 yr 22 minutes ago, rmp5s said: Simple enough!! Up until...any tips on telling which disk is which? lol I have no clue which is the SSD. And, yup, it was set to block, not file already. You are close. You’re just passing in a disk Id that doesn’t exist. It needs to be one of those in the by-I’d/ directory, but which one? have a look in tools -> system devices. At the bottom it lists scsi devices, which might have some mapping, or offer a clue. or go to unassigned devices and click the i on to the left of each drive to expand the volume structure. Any clues there? if I had to guess, I’d guess the 4th scsi device, at the top of the second column. The other 3 have a similar structure (part) that would suggest they match your 3x array devices. Edited January 20, 20206 yr by meep
January 20, 20206 yr Author 2 minutes ago, meep said: You are close. You’re just passing in a dusk I’d that doesn’t exist. It needs to be one of those in the by-I’d/ directory, but which one? have a look in tools -> system devices. At the bottom it lists scsi devices, which might have some mapping, or offer a clue. EXACTLY what I'm thinking, too. Looking at "system devices" doesn't scream anything to me...I don't see anything in common between the "/by-id" list and the "system devices" list. You all see anything?
January 20, 20206 yr 3 minutes ago, rmp5s said: EXACTLY what I'm thinking, too. Looking at "system devices" doesn't scream anything to me...I don't see anything in common between the "/by-id" list and the "system devices" list. You all see anything? Nope. I added a few more suggestions to my previous post. You could also also search the unraid boot log file for some of those strings. Might offer further clues.
Archived
This topic is now archived and is closed to further replies.