boelle

well it has just been put on hold the box froze up after hours of use, and my situation is a bit delicate... i'm on benefits so cant aford to buy new hardware, the plan was to have one box to run 2 VM's so i in the end could save some electricity. on the other hand i need the VM's to be stable....

the box froze up after some hours of use... i guess my hardware is a big no go after all... or am i mistaken?

Hmmm Thanks for the tip, will der if i can Cook up something

btw.... does my BIOS settings look right?

was it that one? that was not quite what i was after... this would require to open a browser and click shutdown.... if one does that by mistake and the other is working on something.... my idea would be a bit more "foolproof" as the VM's would have been killed from the vm before the box powers off

Its not the array.... Its the whole unraid box i was thinking about ie first man out of bed press the power button, since the VM's are set to auto start they will start up then i click on shut down pc as i would on any windows pc a few hours later tina which knows nothing about unraid would do the same... now i would like it to shutdown the unraid box and power it off completely... did you really mean the array or the box as a whole?

So i had somewhat success with getting my first VM's running i can set them to start with the box.... great... but when when either me or tina kills the vm before we go to bed it would be nice if a shutdown was started.... ie when no VM is running i know i could prob use putty to ssh in to the box and tell it to do a shutdown... but not sure if that is a good to do from within the VM

So i figure my route here is to invest in a usb soundcard or an box that can extract the sound from the HDMI if the system can run with the hdmi as sound card... i would have liked to use the onboard sound as it could take care of both my speakers and headphones at the same time

ACS needs to be on or it freezez the box if i try to start a VM... or could i be a setting in syslinux.cfg? EDIT... it was when i enabled the onboard sound card...

that combo worked with ACS Override on and the added stuff in config file now turned ACS Override off but its building parity (yes just added a drive for that), can i safely reboot during that or should i wait?

CPU: Core i7 960 MB: Asus P6T6 WS Revolution - https://www.asus.com/Motherboards/P6T6_WS_Revolution/ GPU: Gigabyte GV-N680OC-2GD - http://www.gigabyte.com/products/product-page.aspx?pid=4178#ov RAM: 3*4 GB DDR3 (in tripple channel mode) need more data? just so i get the right stuff first time arround EDIT: GPU for Unraid is and crappy one i pulled from an old HP pc: Asus GeForce 8500GT 512MB - http://www.ascendtech.us/asus-geforce-8500gt-512mb-dvi-hdmi-s-vid_i_vc512hpgf8500gt.aspx

1 of them yes. Or so was the plan. I also have a gtx 680, That no also barked at me, but maybe the other screws things up just by being there? Do I get it right that unraid also needs a card on its own?

thought i would add pictures to show my BIOS settings and attached a fresh diagnose zip tower-diagnostics-20151025-2019.zip

added vfio_iommu_type1.allow_unsafe_interrupts=1 again now i can start the VM and i see the blue window logo and the spinning thingy but the spinning stops and nothing happens the system does not lock up a bit progress :-D

tried to remove 2 of the GPU's, still the same

nope did not help Execution error internal error: early end of file from monitor: possible problem: 2015-10-25T15:47:41.928158Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2015-10-25T15:47:41.928181Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 16 2015-10-25T15:47:41.928188Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2015-10-25T15:47:41.928197Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2015-10-25T15:47:41.928205Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

bummer.. there was an update... will flash and see if it helps side Q: when i click edit XML on the VM why do i not get a box with text to edit?

yes that was the first thing i checked even before i started to take apart my machines to merge them in to one will double check, even the best can miss a number and it can make the whole difference

i have come to the same conclusion, now i just need to fix it but have no idea on how.. all i know is that the info screen has given the go for hardware pass through and if i add that unsafe interrupts line it can start but then the hole box frezzes up... not only the vm but also unraid i guess that since i have uploaded a new dignose zip there is not much else i can bring to the table...

given its sunday i dont expect anything to happen but are there any extra info i could bring forward that would be a big helper in getting things to run? i can assign keyboards and mouse to my vm's but as soon i assign a physical GPU or the onboard sound it refuses to start.. and for games vnc are just a bit to slow in updating and cumbersome as the only extra machine i have is a ras pi

yep.. can at least run the installer if i opt for VNC as GPU EDIT: only hardware i can assign is mouse and keyboard. if i select soundcard i get a similar error but different hardware id

hmmm seems like VNC works.... only a short term "patch" thou

is there or could there be any relation to that i cant edit XML ? i can click it but no XML shows up...

maybe this one is so complicated that a service session is needed?

with that enabled and the following settings in VM i get : Execution error internal error: early end of file from monitor: possible problem: 2015-10-24T23:50:22.503526Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2015-10-24T23:50:22.503551Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 16 2015-10-24T23:50:22.503559Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2015-10-24T23:50:22.503568Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2015-10-24T23:50:22.503578Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized