bungee91

1) Didn't attempt, sorry but didn't work for the other 2 people, certainly will if still needed. 2) default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS with KVM menu default kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode 3) Looping (started from reboot sequence, it's a bit long) https://www.youtube.com/watch?v=LNkcxr4Y9Gk Normal Boot (for comparison, also long and a complete boot) https://www.youtube.com/watch?v=L3vBf-cPZbE 4) Non UEFI is default, no special options, most stuff unneeded turned off (blurry, but still informative, resized/zipped, download button at the top) https://drive.google.com/file/d/0B0_CMCHyY8iWNVgxU0tNMGYtams/view?usp=sharing

I've noticed this same condition lately and (for what it may be worth) also have an ASRock board, but not the same as it's a Z97 chipset. I found it odd to say the least, and never had this issue prior to lately. The weird part is that I don't get to a default "no boot device, press a key ..." message. It seems like what is happening is that it attempts to boot from USB, fails, and then loops in this manner. If this is the condition it would make a lot of sense on Unraid/USB boot device being the culprit and not the BIOS/post process. A complete power off fixes this condition for me also.

Trying adding this line after <qemu:commandline> and prior to your devices. <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> JonP has his example on the 1st post.

Since we are emulating a Q35 chipset, is it recommended to install chipset drivers for this in Windows?

WebVirt for me after copy/paste into a new XML looks like this, in case it helps any. <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os>

Any input on this? I'd love to start playing with this again, but complete lock-ups & the parity check afterwards was annoying.

I edited this again, I must have had something wrong as it works great now!

No I get it, but thanks... Again the question is WITHOUT passing through a GPU, I'm playing with TV tuner/capture card because GPU pass through was locking up the entire server on reboot/shutdown of the VM. If this is no longer the case, I have a GPU just waiting to be passed.

Will do, but question (worry). Without it if it doesn't successfully boot (without passing through a GPU) how am I to know where/what it may be doing?.. I'm basically blind if the remote connection just fails? I assume the best answer here is to pass a GPU so that I can see? Or just hope all is well?...

XML attached (had to change extension to .txt in order to attach), also lspci -k output Sorry to derail the thread all about me! Win8WebVirtMgr.txt lspci_output.txt

No updates since June, so I'm as recent as I can be. So when you're messing with you VM and GPU pass-through, no eject or anything is needed when rebooting/shutting down?

I have a Z97 chipset, so I'm current/modern however I just don't know what it does? I just get stuck at boot, no blue screen, no halt, just a spinning little wheel. I'd be more than happy to share, if needed. I think a lot of people are looking forward to it.. Now about Windows and restarting/ejecting?... Input would be very helpful, as hard locking up the entire server due to a restart got old REAL quick!..

Thanks for some input on this, I think it will be helpful to a lot of people. A couple of questions that I have. [*]When passing through 1 device that is not a GPU/video card, do you need to include this line in the <qemu:commandline> section, and what exactly does it do? "<qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/>" In my case I was experimenting passing through a tv tuner/capture card, tried both ways, I believe both were hit or miss. [*]It seems that when passing through a device in Windows (8.1 for my example) I can get it to install the drivers and function, however after shutting down the VM, or restarting I get stuck at the boot screen. If I remove the pass-through it starts right up. Do you HAVE to eject any pass through device prior to shutdown/reset? I have automated this with Devmanview, however I still have issues and it is inconsistent [*]What is the correct syntax (an example would be nice) to add to the go script for vfio-bind at bootup? I've attempted /usr/local/sbin/vfio-bind 0000:0#:00.0 0000:0#.00.1 (with my proper addresses) and I get an error of some sort on the console. [*]When do we get to "play" with your special compiled XBMC (Kodi...Grrrr) build that you've been working on?... I'm certainly looking forward to it, and even if it is somewhat Beta it would be nice to get a chance to try it out.

XBMC household here (boo to Plex!.. ) Anyhow I'm all for the testing, and will play with the customized XBMC build. GPU pass-through and complete server lockups got old, so I haven't played in a while. Hopefully this is not the case with using OpenElec or the custom build. My non pass-through Win7 VM has been rock solid for quite a while now.

If this is a user share called "movies" it would be /mnt/user/movies

I'm glad it's not only me. I played around with this http://forum.xbmc.org/showthread.php?tid=189241 Using VNC on in the xml to do the install (no GPU passthrough set at this point). It seems to take forever but it does install minimal Ubuntu. I then SSH'd into it once booted and attempted the 2nd part of the install with XBMC. I also did this through VNC however it failed stating the wrong video card/drivers aren't installed. I then used an xml with the proper GPU passthrough enabled, started it up, and the entire server froze dead at start. I'm pretty sick of complete lockups when playing with GPU passthrough, so for now I'm done playing. I think this method can work, and then you can do an in-place upgrade to Gotham easy enough. I'm currently having to do a parity check, so no time to play for a little while.

Alright, I'm calm now and good to go! The only docker I really cared about was MariaDB and my XBMC library. Once I transferred it's template I installed it, stopped the newly made docker, replaced the new folder with my old (backed up) MariaDB program folder, and it started and worked perfectly!! I apologize for my frustration, it was frustrating and I always think "I've got this, no problem" and, well, ... nope. I should backup better just in case in the future. All is well..

Thank you to the both of you, and I apologize for my frustration. I understand the "beta" part, and also understand the need for the change even though I didn't experience the out of space issues yet. The greyed out area was odd, it took me a couple of clicks and it allowed me to type. I assumed the initial place for /mnt/disk1 when I hit start would do something, however it just changed for a second and went back to stopped. This must be because it is merely a suggested place, and not actually typed as the location. So when I hit start, it didn't have a location to go to so it failed. Now that I was able to type /mnt/cache/docker.img it created it just fine, did it's thing, and now it is running!!! I did backup the programs I had as far as the directory, and I also have their templates. I will now continue to attempt to get them back setup.

I'm at a loss here, everything was well in Beta 7, now this docker move fiasco and everything is broken! I likely did everything wrong, didn't properly backup, and likely lost my MariaDB database. So help is appreciated. This is what I have at this point, a basically fresh Beta 8 install. Under extensions I have docker, it does nothing. If I click start, it does not. In that page it says docker image /mnt/disk1/docker.img I don't have one there, no clue if I'm supposed to put one there?.. So I hit start, it does nothing. Do I need to put an image there, was it supposed to do this automatically and I fucked it up? Damn did this all work well before prior to this upgrade! It states that "When you visit the Extensions/Docker page you will notice a box to enter a Docker image file. When you click 'Start' the file name you specify will be created and a btrfs file system will be created inside that file. Next the file is loop mounted onto /var/lib/docker. You are also able to resize the file (expand only, shrink not supported yet), and scrub (check) the file system. The default size of "10" (meaning 10GB) seems reasonable to start with." I never get an option to "enter a docker image file" it is listed as disk 1 and greyed out. When I hit start it does nothing, nada..

I've successfully setup a Windows 7 and 8.1 VM for testing/playing in beta 7 (working extremely well too!), however no luck with setting up an XBMCbuntu VM at all! Not sure if anyone else has had success or not. I'm able to initially boot the iso fine, select install, I get the text with "ok, ok, ok,"etc... on the screen, and then it goes black and hangs. I never actually get to a setup screen. I have my xml setup with the iso to boot, and then a qcow2 raw image as an available installable disc, however I never get to the point of selecting/installing. I had thought it may be a linux problem, and something having to do with the kernel, or bootloader, or something I need to assign to the libvirt xml, but I've tried multiple ways with the same failures. I am hoping to set this up as a dedicated setup with GPU passthrough specifically for a media playback purpose. With the Windows xml's, I only need to create them correctly, and run a "virsh create win7.xml" (for example) and all is well. This works perfectly fine and I can VNC into the XBMCbuntu install, it just hangs badly shortly after starting the process. Any help is appreciated, I can share my XML, etc... to try and see what I may be doing wrong.

Settings, share settings, move now (see pic). Actually, that's for V6. I can't remember it may be the same, if not look around, it's in there.

Did you happen to add any settings to your syslinux.cfg file? For the Unraid one without Xen (so with KVM) I added this to mine, grouping is exactly what it should be now afterwards. This is the last line of that entry, the most important for this is the "pcie_acs_override=downstream" append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream initrd=/bzroot

Since we had the same issue with IOMMU grouping, the ACS downstream flag in the syslinux.cfg worked great, and I was able to get GPU passthru working with Windows 7. However I still had to mess with the eject scripts and such to not have the entire machine lockup on a powerdown or reset of the VM. I plan to use the passthrough on a dedicated XBMCUbuntu or Openelec setup. Either way your previous issue should be all set, also I wouldn't hold out for iGPU passing as it doesn't look like that's happening anytime soon.

I'm not experiencing issues with NFS, however I use it almost exclusively for all my shared libraries for XBMC. I had heard that the Raspberry Pi can have issues with high bitrate streaming with Samba, and not an issue with NFS so that's what I use. I believe JonP has said in another thread he uses it exclusively, so I'm not sure his reason.

Thanks for the feedback and clarification... There are a lot of us VERY anxious to get to kick the tyres (as someone else said) of B7. After that I will start my searching, and constant refreshing in regards to Beta 8...LOL