phildep8 Posted January 19, 2016 Share Posted January 19, 2016 (edited) - Edited November 30, 2018 by phildep8 Quote Link to comment
ashman70 Posted January 19, 2016 Share Posted January 19, 2016 What kind of VM are you trying to create? Can you post a screen shot of the error? Can you post your XML? Quote Link to comment
ashman70 Posted January 19, 2016 Share Posted January 19, 2016 Your CPU does not support VT-D, you'll need replace/upgrade it if you want to create virtual machines inside of UnRaid. You may have an option for VT-D in your BIOS but your CPU does not support hence why IOMMU is disabled, it need to be enabled. Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 Your CPU does not support VT-D, you'll need replace/upgrade it if you want to create virtual machines inside of UnRaid. That's not strictly true, vt-d is only required for passthrough. Must have vt-x though... I think... Also as a thought, have you got enough freespace and try creating the VM on a disk share rather than a user share. Also running a VM image on a parity protected share is a bad idea. But hopefully you've got that location as cache only, in which case change /mnt/user/ to /mnt/cache/ Quote Link to comment
ashman70 Posted January 19, 2016 Share Posted January 19, 2016 Whilst I think you are technically correct, I think most people creating VM's un UnRaid want to pass through hardware which is simply not possible in the absence of VT-D support in the CPU. They can probably create a VM but not do too much with it except access it through VNC and use it without any local hardware. Quote Link to comment
ashman70 Posted January 19, 2016 Share Posted January 19, 2016 Is your objective to pass through your video card or other hardware to your VM? Quote Link to comment
ashman70 Posted January 19, 2016 Share Posted January 19, 2016 I don't think you will even be able to get network access though without VT-D, I could be wrong though. Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 I don't think you will even be able to get network access though without VT-D, I could be wrong though. He will.... Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 Try running this.. qemu-img create -f raw /path/to/nameofvm.img 20G Also, try removing the spaces from the path, not sure why that should make any difference, but may be tripping it up somewhere... Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 That command line worked and the img file is there at 20GB. Well you can use that to create your VM with then. Out of interest, try creating a vdisk without all the spaces, for no other reason than I'd like to work out why you had a problem to start with.. Quote Link to comment
saarg Posted January 19, 2016 Share Posted January 19, 2016 That command line worked and the img file is there at 20GB. Well you can use that to create your VM with then. Out of interest, try creating a vdisk without all the spaces, for no other reason than I'd like to work out why you had a problem to start with.. +10 on this Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 Just specify it in the webui /mnt/path/to/disk/vdisk.img Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 Yep! It boots into the ISO now. So just out of curiosity, what do you think would cause this? Not got a clue... I was hoping it was the /mnt/user instead of a /mnt/disk1 or /mnt/cache/ as that can cause problems with docker containers occasionally. Or that it was a spaces issue. Now I'm out of theories. But at least we got you running. Also, assign a different core than 0, Host has preferential rights to 0.. Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 Thank you! Will do No problem... Quote Link to comment
saarg Posted January 19, 2016 Share Posted January 19, 2016 Yep! It boots into the ISO now. So just out of curiosity, what do you think would cause this? Aliens, definitely aliens To be a little bit more serious, it might be that some combination of the file or folder name trips up the VM manager. There might be some clues in the diagnostics zip created under tools --> diagnostics for limetech. Quote Link to comment
CHBMB Posted January 19, 2016 Share Posted January 19, 2016 Yep! It boots into the ISO now. So just out of curiosity, what do you think would cause this? Aliens, definitely aliens To be a little bit more serious, it might be that some combination of the file or folder name trips up the VM manager. There might be some clues in the diagnostics zip created under tools --> diagnostics for limetech. That's a good point... phildep8 would you mind posting this so we can try and figure it out... Please...... Pretty please..... Quote Link to comment
CHBMB Posted January 20, 2016 Share Posted January 20, 2016 Sure thing. Here it is. Did you restart your Unraid box after solving this? The libvirt log is empty... I'm going to try and test on my machine.... Quote Link to comment
CHBMB Posted January 20, 2016 Share Posted January 20, 2016 OK, worked it out, it was the periods.... Not Working.... /mnt/user/VMs/Debian 8.2.0 x64/ /mnt/user/VMs/Debian8.2.0x64/ Working /mnt/user/VMs/Debian820x64/ /mnt/user/VMs/Debian 8 2 0 x64/ Quote Link to comment
jonp Posted January 20, 2016 Share Posted January 20, 2016 OK, worked it out, it was the periods.... Not Working.... /mnt/user/VMs/Debian 8.2.0 x64/ /mnt/user/VMs/Debian8.2.0x64/ Working /mnt/user/VMs/Debian820x64/ /mnt/user/VMs/Debian 8 2 0 x64/ Please file this as a defect report. Quote Link to comment
CHBMB Posted January 20, 2016 Share Posted January 20, 2016 Please file this as a defect report. Done, and I'd like to thank phildep8 for continuing to provide answers to questions after his problems were solved, helping nail the cause down. 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.