Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't find bootable ISO in VM Manager

Featured Replies

Trying out the new beta 15 for unraid and I can't seem to find a correct bootable iso for it. I placed everything on the cache drive and start the VM (VirtIO, Win 7 ISO, and vdisk) and it says there's no bootable disk. What am I doing wrong and how can I restart the VM?

 

since this beta just came out there's barely anything on google about this.

Trying out the new beta 15 for unraid and I can't seem to find a correct bootable iso for it. I placed everything on the cache drive and start the VM (VirtIO, Win 7 ISO, and vdisk) and it says there's no bootable disk. What am I doing wrong and how can I restart the VM?

 

since this beta just came out there's barely anything on google about this.

Tame a screen shot of the page you configured the VM on and post it here.

  • Author

Attached is what I am seeing for the VM. The only thing I did since I posted this was change the boot order around in the XML file and it won't start now. I left it alone since until I get more help on here. For now this is all for testing so the naming scheme can change to whatever works best until I am able to successfully create multiple VMs to test if I am going to upgrade my server that supports VT-d.

58aad77e151ed_ss2015-04-26at12_30_11.png.79461d8851af93e07ad1a6bf964292e8.png

Attached is what I am seeing for the VM. The only thing I did since I posted this was change the boot order around in the XML file and it won't start now. I left it alone since until I get more help on here. For now this is all for testing so the naming scheme can change to whatever works best until I am able to successfully create multiple VMs to test if I am going to upgrade my server that supports VT-d.

 

Ok, not sure why this isn't working for you, but we will figure it out.  Can you copy and paste the XML for your VM here so I can have a peek?

  • Author

Attached is what I am seeing for the VM. The only thing I did since I posted this was change the boot order around in the XML file and it won't start now. I left it alone since until I get more help on here. For now this is all for testing so the naming scheme can change to whatever works best until I am able to successfully create multiple VMs to test if I am going to upgrade my server that supports VT-d.

 

Ok, not sure why this isn't working for you, but we will figure it out.  Can you copy and paste the XML for your VM here so I can have a peek?

 

Thanks for looking at this.

 

<domain type='kvm'>
  <name>My VM</name>
  <uuid>f38ea84a-f5d0-780e-c2c9-91081931d82f</uuid>
  <memory unit='KiB'>2621440</memory>
  <currentMemory unit='KiB'>524288</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>3</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.2'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='3' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none' io='native'/>
      <source file='/mnt/cache/My VM/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/cache/Windows_7_SP1.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/cache/virtio-win-0.1-100.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:ec:0b:09'/>
      <source bridge='virbr0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='vmvga' vram='16384' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
</domain>

Attached is what I am seeing for the VM. The only thing I did since I posted this was change the boot order around in the XML file and it won't start now. I left it alone since until I get more help on here. For now this is all for testing so the naming scheme can change to whatever works best until I am able to successfully create multiple VMs to test if I am going to upgrade my server that supports VT-d.

 

Ok, not sure why this isn't working for you, but we will figure it out.  Can you copy and paste the XML for your VM here so I can have a peek?

 

Thanks for looking at this.

 

<domain type='kvm'>
  <name>My VM</name>
  <uuid>f38ea84a-f5d0-780e-c2c9-91081931d82f</uuid>
  <memory unit='KiB'>2621440</memory>
  <currentMemory unit='KiB'>524288</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>3</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.2'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='3' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none' io='native'/>
      <source file='/mnt/cache/My VM/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/cache/Windows_7_SP1.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/cache/virtio-win-0.1-100.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:ec:0b:09'/>
      <source bridge='virbr0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='vmvga' vram='16384' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Hmm, can you drop to command line (SSH or telnet) for me and type the following:

 

virsh start "My VM"

 

Copy and paste the response you get back here.

  • Author

EDIT: Fixed the picture

 

Attached will be the console output after I typed that command.

58aad77e2a3bb_ss2015-04-26at04_29.28-min.png.2ef6655b728d7af2934684f8bb3775b4.png

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

  • Author

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

 

Tried that three times which is why I came here. I am unable to delete my VMs even after shutting the server down and manually doing it. I currently have 4 VMs in the list and none of them start. If I create a new one it'll work once and then stop at bootable media not found with those same settings. I have no idea how to restart my VM either.

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

 

Tried that three times which is why I came here. I am unable to delete my VMs even after shutting the server down and manually doing it. I currently have 4 VMs in the list and none of them start. If I create a new one it'll work once and then stop at bootable media not found with those same settings. I have no idea how to restart my VM either.

 

Ok, this is bizarre to say the least.  If you browse to the folder to where the virtual disk should be, it's there, yes?  Just want to make sure it's actually creating a folder and the vdisk.

 

There is a bug with adding additional vdisks to an existing VM, but shouldn't affect new VMs.

 

Are you typing the path into the VM Manager fields for ISO and vdisk or are you using the folder picker?

  • Author

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

 

Tried that three times which is why I came here. I am unable to delete my VMs even after shutting the server down and manually doing it. I currently have 4 VMs in the list and none of them start. If I create a new one it'll work once and then stop at bootable media not found with those same settings. I have no idea how to restart my VM either.

 

Ok, this is bizarre to say the least.  If you browse to the folder to where the virtual disk should be, it's there, yes?  Just want to make sure it's actually creating a folder and the vdisk.

 

There is a bug with adding additional vdisks to an existing VM, but shouldn't affect new VMs.

 

Are you typing the path into the VM Manager fields for ISO and vdisk or are you using the folder picker?

 

I reinstalled unRaid and it's kind of working now. The only difference I did was manually type Windows7 into the vdisk location once i used the drop down menu for everything else.

 

You can see where I am at in the following picture: http://puu.sh/hs3Bw/72bab32a68.png

 

Odd thing is the fact one of my drives will never mount and preclear didn't fix it. I also am having trouble taking it out of the array once I take it down, though that's something else.

58aad77e518d7_ss2015-04-26at07_28_14.png.7e58c625ddd2c3efd835b506e7f9fad6.png

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

 

Tried that three times which is why I came here. I am unable to delete my VMs even after shutting the server down and manually doing it. I currently have 4 VMs in the list and none of them start. If I create a new one it'll work once and then stop at bootable media not found with those same settings. I have no idea how to restart my VM either.

 

Ok, this is bizarre to say the least.  If you browse to the folder to where the virtual disk should be, it's there, yes?  Just want to make sure it's actually creating a folder and the vdisk.

 

There is a bug with adding additional vdisks to an existing VM, but shouldn't affect new VMs.

 

Are you typing the path into the VM Manager fields for ISO and vdisk or are you using the folder picker?

 

I reinstalled unRaid and it's kind of working now. The only difference I did was manually type Windows7 into the vdisk location once i used the drop down menu for everything else.

 

You can see where I am at in the following picture: http://puu.sh/hs3Bw/72bab32a68.png

 

Odd thing is the fact one of my drives will never mount and preclear didn't fix it. I also am having trouble taking it out of the array once I take it down, though that's something else.

 

Well I'm glad you were able to get a VM going, but sad to hear you have other issues with a malfunctioning drive.  There are tools in unRAID 6 to run SMART reports.  I would suggest opening a new thread in General Support for help on that front.  Come back here if you have further issues creating VMs.

  • Author

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

 

Tried that three times which is why I came here. I am unable to delete my VMs even after shutting the server down and manually doing it. I currently have 4 VMs in the list and none of them start. If I create a new one it'll work once and then stop at bootable media not found with those same settings. I have no idea how to restart my VM either.

 

Ok, this is bizarre to say the least.  If you browse to the folder to where the virtual disk should be, it's there, yes?  Just want to make sure it's actually creating a folder and the vdisk.

 

There is a bug with adding additional vdisks to an existing VM, but shouldn't affect new VMs.

 

Are you typing the path into the VM Manager fields for ISO and vdisk or are you using the folder picker?

 

I reinstalled unRaid and it's kind of working now. The only difference I did was manually type Windows7 into the vdisk location once i used the drop down menu for everything else.

 

You can see where I am at in the following picture: http://puu.sh/hs3Bw/72bab32a68.png

 

Odd thing is the fact one of my drives will never mount and preclear didn't fix it. I also am having trouble taking it out of the array once I take it down, though that's something else.

 

Well I'm glad you were able to get a VM going, but sad to hear you have other issues with a malfunctioning drive.  There are tools in unRAID 6 to run SMART reports.  I would suggest opening a new thread in General Support for help on that front.  Come back here if you have further issues creating VMs.

 

I still do. The picture in the link showed it didn't get past the "loading windows" screen. Is there a way I can restart the VMs similar to the other programs out there like virtualbox? If I can see the VM restarting I can test easier as it may be stuck on something.

Ok, try creating a new vm. Delete the one you created. See if the issue persists.

 

Tried that three times which is why I came here. I am unable to delete my VMs even after shutting the server down and manually doing it. I currently have 4 VMs in the list and none of them start. If I create a new one it'll work once and then stop at bootable media not found with those same settings. I have no idea how to restart my VM either.

 

Ok, this is bizarre to say the least.  If you browse to the folder to where the virtual disk should be, it's there, yes?  Just want to make sure it's actually creating a folder and the vdisk.

 

There is a bug with adding additional vdisks to an existing VM, but shouldn't affect new VMs.

 

Are you typing the path into the VM Manager fields for ISO and vdisk or are you using the folder picker?

 

I reinstalled unRaid and it's kind of working now. The only difference I did was manually type Windows7 into the vdisk location once i used the drop down menu for everything else.

 

You can see where I am at in the following picture: http://puu.sh/hs3Bw/72bab32a68.png

 

Odd thing is the fact one of my drives will never mount and preclear didn't fix it. I also am having trouble taking it out of the array once I take it down, though that's something else.

 

Well I'm glad you were able to get a VM going, but sad to hear you have other issues with a malfunctioning drive.  There are tools in unRAID 6 to run SMART reports.  I would suggest opening a new thread in General Support for help on that front.  Come back here if you have further issues creating VMs.

 

I still do. The picture in the link showed it didn't get past the "loading windows" screen. Is there a way I can restart the VMs similar to the other programs out there like virtualbox? If I can see the VM restarting I can test easier as it may be stuck on something.

From the VMs page, there are icons. Hover over the icons for a tooltip and it will tell you shat they do.  There is a restart icon, but it won't work if the VM is hung. For that, you have to force shutdown and start again (the eject button).

 

It sounds to me like you have a hardware issue which is why the installer isn't loading.

  • Author

I was starting to think it may be hardware since my cpu lack VT-D.

 

I am going to see if I can get a vm to run on the VirtualBox plugin before returning my cpu. If a cpu is going to run around the same temp at idle whether it is 35W or 120W I may as well invest in a nice xeon and get a g3258 or something for bother server I have planned.

 

Once I have an update on this issue I will reply and mark as fixed if I end up fixing it. Thanks for the help.

I was starting to think it may be hardware since my cpu lack VT-D.

 

I am going to see if I can get a vm to run on the VirtualBox plugin before returning my cpu. If a cpu is going to run around the same temp at idle whether it is 35W or 120W I may as well invest in a nice xeon and get a g3258 or something for bother server I have planned.

 

Once I have an update on this issue I will reply and mark as fixed if I end up fixing it. Thanks for the help.

Vtd is not required unless you are passing through a pci device like a GPU. Only vtx is required to create a traditional vm. My comment on your hardware was that I think you may have a faulty storage device.

 

Also is your cache drive an SSD or HDD?

  • Author

I was starting to think it may be hardware since my cpu lack VT-D.

 

I am going to see if I can get a vm to run on the VirtualBox plugin before returning my cpu. If a cpu is going to run around the same temp at idle whether it is 35W or 120W I may as well invest in a nice xeon and get a g3258 or something for bother server I have planned.

 

Once I have an update on this issue I will reply and mark as fixed if I end up fixing it. Thanks for the help.

Vtd is not required unless you are passing through a pci device like a GPU. Only vtx is required to create a traditional vm. My comment on your hardware was that I think you may have a faulty storage device.

 

Also is your cache drive an SSD or HDD?

 

 

EDIT: Had to load the scsi drivers to see the drive. First time ever having to do that on the install screen. Now it's officially installing.

 

i did get farther though now I don't see a hard drive to install windows 7 on. I am using a new 4TB WD Red. You can see what I mean in the attached picture.

 

58aad77e7713a_ss2015-04-27at05_07_37.jpg.f954a08fab11a1b6ee1045ae388c6123.jpg

I was starting to think it may be hardware since my cpu lack VT-D.

 

I am going to see if I can get a vm to run on the VirtualBox plugin before returning my cpu. If a cpu is going to run around the same temp at idle whether it is 35W or 120W I may as well invest in a nice xeon and get a g3258 or something for bother server I have planned.

 

Once I have an update on this issue I will reply and mark as fixed if I end up fixing it. Thanks for the help.

Vtd is not required unless you are passing through a pci device like a GPU. Only vtx is required to create a traditional vm. My comment on your hardware was that I think you may have a faulty storage device.

 

Also is your cache drive an SSD or HDD?

 

 

EDIT: Had to load the scsi drivers to see the drive. First time ever having to do that on the install screen. Now it's officially installing.

 

i did get farther though now I don't see a hard drive to install windows 7 on. I am using a new 4TB WD Red. You can see what I mean in the attached picture.

 

Glad you got it going finally!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.