saarg

It's set to -1, it's just that I copied it from a running VM and then the port is set in the xml file.

I found out what was causing my VM's not to autostart It was the tag for VNC! I had this in my xml file: <graphics type='vnc' port='5901' autoport='no' listen='192.168.1.5'> <listen type='address' address='192.168.1.5'/> </graphics> After changing it to this, everything works: <graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='no'> <listen type='address' address='0.0.0.0'/> </graphics> The only problem I have now is that I have to reboot unraid a couple of times before the DVB card is correctly passed through to my VM. It might have something to do with vfio-bind is run in the go file a while after libvirt is started.

<filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Recordings'/> <target dir='recordings'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </filesystem> recordings /mnt/recordings 9p trans=virtio,version=9p2000.L,nobootwait,rw,_netdev 0 0 1. Array disk 2. HDD 3. /mnt/user 4. SSD /mnt/cache (Qcow2 and Raw tested) 5. NA 6. BTRFS (Not sure if you mean the cache disk or the file system inside the VM. Ext4 filesystem inside VM) 7. Rsync 8. 75MB/s Updated some info as it seems you changed the questions in the first post.

I was just about to type that I might be wrong

JustinChase did not give you the full tag for the usb tablet, and that is probably why it is not working. It should be like this: <input type='tablet' bus='usb'> <alias name='input0'/> </input>

Have you tried to change some of your options in fstab? Not sure if all of your options are valid and the best option. Have a look at this link for mounting options: https://www.kernel.org/doc/Documentation/filesystems/9p.txt. This is what I have on my fstab and my speed on a test I did now was 73.62MB/s: recordings /mnt/recordings 9p trans=virtio,version=9p2000.L,nobootwait,rw,_netdev 0 0

I might have found a bug. If you enable autostart on a vm, then edit the domain xml (just hitting save without doing anything), the autostart gets removed. Is this by design or a bug?

Here is my virtman.img and the syslog. From the syslog it looks like virtman.img is mounted long before (20 seconds) libvirt starts. The symlinks are created when I toggle autostart. I was thinking to disable autostart of libvirt in the settings of virtman and starting libvirt from the go file, but have to wait until some scheduled recordings are finished. Does disabling libvirt in the settings page stop the mounting of virtman.img also? Edit: Another thing I noticed is that autostarting vm's and using vfio-bind is not that easy. Looking at the syslog binding the pci device to vfio is done almost two minutes after libvirt gets started. I was hpoing that this was my problem, but since I tried with a vm that did not use autostart, that was not the case. syslog.txt virtMan.zip

Also are your vm's on your cache or non array drive? Shouldn't matter for cache but if non array gets mounted on or after array starts then the vm's can't start since their images aren't available. It did not work to do as you suggested. The vm's are on my cache drive. As said before, the vm's start if I restart libvirt, so it seems to me that there is something in the boot process that prevents the vm's to start. I was thinking that it might have been that I was using passthrough in my vm's (pci and usb), but just tried to set a test vm I had to autostart with the same result. The other vm's had their autostart disabled during the test.

I'll try that

I cannot seem to get the autostart to work when booting unraid. I at first thought it was something I did with the configuration files, but it's the same problem after replacing the modified configuration files with the unraid ones. Autostart works if I go to Settings --> Virtman and stop and start libvirt. Since Autostart works when stopping/starting libvirt manually there shouldn't be any problems with permissions? logfile.txt

You have to add vfio_bind in your go file and add the pci devices you want to pass through like this: /usr/local/sbin/vfio-bind 0000:03:00.0 Multiple pci devices are separated by a space.

Do you have an option in the uefi setup that is called Full HD Uefi? It is on the main page on my motherboard (H97 Pro4). When this was set as auto it made problems for me like the boot loops you're having. I have it disabled.

To me this sounds like a problem with your usb stick than a software problem. I would try another usb stick to see if that works. Do you have the usb stick in the boot menu when this happens?

Did you change add websocket='-1' in your xml file like this? <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics>

RobJ gave you the option to skip Pre-read

I do not consider my movies and music worth enough to spend money on a parity drive. I have the physical disks, so no problem ripping them again. If there is something else I absolutely need to have, I back it up to external drives. When 6TB drives gets cheaper I might add one for parity.

It's good to hear that the problem is solved. I do not know if this is normal behavvior when rebuilding disks as I do not have a parity disk, so no need to rebuild. I also have some problems getting unmenu to load for the first couple of tries, but after 2-3 refreshes it works fine.

With the new libvirt package in the pluggin, it turns on sasl2 for tcp connections to libvirt. I can't figure out how to turn it off. So you need a username/password to connect to libvirt. Without sasl2 you could use any unRAID username/password. That command creates it and stores it in/etc/libvirt/passwd.db. This will show you the users in that db. sasldblistusers2 -f /etc/libvirt/passwd.db I tried changing settings in /etc/libvirt/libvirtd.conf but couldn't turn it off. I might look at commenting out /etc/sasl2/libvirt.conf Did you change this setting in libvirtd.conf: auth_tcp = "none"

I had a similar problem here. I got a lot of time outs trying to copy files to my shares and reading speed was extremely slow. Also starting and stopping the array took ages. It turned out that one of my drives suddenly started getting a lot of bad blocks. After removing the drive, I got my speeds back. Luckily for me I'm moving from a NAS to Unraid and haven't deleted the content of the NAS yet, so the contetn was easily available. It might no t be the same issue, but it might be good to check the smart reports of your drive.

Just wondering if that was a problem with cifs shares you had or on the passthrough you have now also?

He uses the noauto option in fstab and needs to mount it manually after boot. He did mention something about why in an earlier post I think.