htpcnewbie
-
Posts
295 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by htpcnewbie
-
-
Glad you got it working. In my signature there is a link to a thread where I have the xml for win8.1. In that xml I pass through audio, video and the corresponding pcie controller for USB ports. I initially started off with win7 but switched to win8.1 since I wanted to pass through USB Pci controller and I couldn't do that with win7 on my setup.
I saw a thread about passing through cdeom, jonp was helping figure out the details. Passing through audio and video should work without much effort.
htpcnewbie and dmacias, Thank You, you guys rock! Win7 is up and running like a champ. Not as clean a file directories as I would like, but this is totally a learning curve for me, I'll worry about the petty stuff when I setup as a main server.
Now it seems I'm in the same spot I was in with Xen. All I have is my onboard audio, so I guess I'll have to figure out how to pass this through to windows, is that what passthrough is?
And I'm back to that pesky DVD/CD usb rom, so I can use Makemkv to add files to my drives. Can't see how a guy can have the ultimate HTPC without this capability.
Again, any and all help would be appreciated, where the heck do I start?
Thanks Again, Dave
Do you think a usb controller card would help with this, I noticed it in other posts...
-
Yeah, just use the iso files that you have downloaded on your computer. You can also use imgburn Windows software to burn to iso from cdrom.
I'm doing something wrong, you guys posted and it all made sense to me until I went to work.
I currently have the Win7.iso and the virtio.iso on both cd and flash drive. So I say, let's do it, I put my flash drives each in a USB port (2.0), boot up unraid. KVM, virtman, libvirt running, all systems go! Go to the "Create VM", go to install image, no USB showing, go to virtio drivers (iso), no USB showing.
I'm looking at htpcnewbie, "<source file='/mnt/disk/SSD1/vm/media/Windows81Pro.iso'/>" and "<source file='/mnt/disk/SSD1/vm/media/virtio-win-0.1-81.iso'/>" and it looks like the files are already SSD drive equivalent to my cache drive (also I just named it cache instead of SSD). My question is "How in the heck did you get these iso's from cd/Flash drive onto your cache drive/SSD. This is the obstacle I can't seem to get over, everything else makes sense to me if only I could get that far.
Thanks, guys for the help so far….Dave
Edited by me, I'm over thinking, I'm downloading directly to an image file I created on my cache drive, is this correct? We'll find out…..
-
++1
I see your point and on the other hand I think that unRAID had already passed that boundary .... with KVM/XEN/Docker support included I would think that drivers should be included as well. Not only DVB driver btw...
-
kristisdad - I think it would be easier if you make iso soft copies of both the files. In my limited experience, I am not aware of anyone who has installed them through the cdrom. I prefer the command line definitions, see whether these help you. I have indicated line numbers to highlight what you need to change using my xml file copied below. I use notepad++ for Windows editing and it is a gnu/freeware download.
0. Download and install "Virtual Machine Management" and "Libvirt support" plugins by dmacias72. See this thread for info: http://lime-technology.com/forum/index.php?topic=35858.0. Once this is installed, you may have to reboot (I am unsure). After proper installation you will see a "KVM" tab on the top of the unraid GUI in between "Docker" and "Tools". I typically use xml's to make my KVM's. To manually add a kvm using xml file, click on KVM > "Add XML" and copy paste the xml's to define a kvm. You can see defined kvm's in KVM > "Virtual Machines". Here you can start, stop or change vcpu's and memory for the defined kvm's. There is also an option to create a kvm using a GUI in KVM > "Create VM". You may find working with gui easier but the steps below are mostly outlined working with a xml.
1. to make qcow2 file for Win7 installation:
qemu-img create -f qcow2 Win7x64.qcow2 20G
2. Download the iso image of the virtio drivers from my post earlier
3. make or download an iso image of the Win7
4. I am copying an xml below. In this xml file, change the location of the (1)-line #34, (2)-line #40 and (3)-line #46 corresponding to where you have saved the files.
Note: Line #17 has <boot dev='cdrom'/>. This will boot into win iso installation.
5. When you proceed toward installation, you will get a prompt for drivers. Chose "have disk" or something like "browse" and navigate to the drive that is shown as a mount for (2) iso. I think you need to navigate to the AMD64 drivers folders and when selected, the virtio drivers will be installed.
6. The qcow2 file you created for Win7 installation will show up as a drive for Windows installation. Chose this and proceed with installation.
7. After all the installation is done, shutdown the vm. For shutting down the vm, use the GUI. You can either edit the xml file or make a new one. Change line #17 to <boot dev='hd'/>. Start the vm.
8. For logging into the kvm machine you can either use vnc or remote desktop. I personally prefer Windows remote desktop (RD) since this works quite well even with VNC disabled when you passthrough a video card. For RD, make sure you name the machine something easy and you can just use this name to remote desktop into.
Win7 installation xml file:
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>win-install</name> <uuid>0b001083-f7ad-48a9-b298-6ed0afed515a</uuid> <description>win-install</description> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>1953125</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='cdrom'/> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'/> <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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/SSD1/vm/media/Windows81Pro.iso'/> <target dev='sdd' bus='sata'/> <readonly/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/SSD1/vm/media/virtio-win-0.1-81.iso'/> <target dev='sde' bus='sata'/> <readonly/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/disk/SSD1/vm/image/Win7x64.qcow2'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <controller type='ide' index='0'> </controller> <controller type='sata' index='0'> </controller> <controller type='pci' index='0' model='pcie-root'> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> </controller> <controller type='pci' index='2' model='pci-bridge'> </controller> <interface type='bridge'> <source bridge='br0'/> <model type='virtio'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target port='0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5901' autoport='yes' listen='10.10.1.121' keymap='en-us'> <listen type='address' address='10.10.1.121'/> </graphics> <video> <model type='cirrus' vram='9216' heads='1'/> </video> <memballoon model='virtio'> </memballoon> </devices> </domain>
I believe the vm's are recognized by uuid's. If you make a new xml file, ensure it has a unique uuid not defined in your other kvm's. The uuid's can be generated easily here: https://www.uuidgenerator.net/
This is where I'm at. I have Win7x64 iso and the Virtio drivers iso on a CD, however, they are not seen on the "Create VM" screen from my cd player (USB). This didn't happen on the Xen install because the XML forced the cd to be seen. ('file:/mnt/cache/VMs/Windows7/Win7x64.iso,hdc:cdrom,r'). Same with the drivers. How do I make this happen?
I see reference to a "create Template section", but I can't find it, would the template allow the dvd/cd player to be seen?
Is this the template: Posted by JustinCase on 30October?
Where can I find all the fill in's, this is daunting to this old guy!
Dave
-
You will need to download the windows virtio drivers. It can be obtained from here as an iso image: http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers
In the xml file you will have two iso's: win71 iso & virtio iso
1. Use Win71 iso as boot and during installation, use browse for drivers option, go to the virt iso drive and load up the drivers in AMD64 directory
2. After installation of Windows, shutdown the kvm and change the boot to 'hd' which should be pointing to the qcow2 image.
I do not have access to my machine currently but you can get a simple xml file for this from these forums.
The process is fairly simple but could be time consuming if you are trying to figure out the first time. Ping again here if you get stuck or need the xml files.
I got Win7 installed with the instructions by Ghunter in the XEN forum. All was going great until I tried to use the DVD player and like everyone else I hit the roadblock, so I continued on my quest.
Then I decided to try the KVM, which seems to be the answer, however, I started following the instructions through the first two install steps and hit another brick wall. Seems like from there everyone was trying to connect to Win thru the VNC viewer, but I can't seem to figure out the Windows installation.
I see the Window setup screen, can I use the Win7x64.iso from my VMs file that I set up on my cache disk when I setup it up in XEN (XEN is currently turned off) or do I need to start from scratch with the iso from the dvd.
Which part of the Windows virtio drivers do I use, do I install them from an iso like Win7?
Are these files, isos, xml, and drivers setup in the cache drive, or where do they get setup at?
I have NO XML file experience except to edit XML templates. My build is new so I'm not worrying about throwing anything out of whack, just tryin to get up and running. Is there a good template to start out with that can be doctored. I see plenty of snippets, but not quite sure how to put them together..
I'm kinda really lost, so any step by step installation sure would be appreciated.
Thanks, Dave
-
Glad it worked for you as well
I got an initial warning that the active drive cannot be increased but went ahead with the process and in the end I saw my C: drive with increased +20GB.
Excellent! You were right. As simple as this
-
Hi - I was trying to upgrade two docker containers (binhex/arch-madsonic and needo/plex). I used the unraid gui to stop the containers and remove the images before pulling in the new images. I am uncertain what happened since removal of the images seems to have stalled for a long time (> 30 mins). The page output was blank, I closed the window. I now see that the images seem corrupted and unable to remove them from command line as well.
Copied below is a screenshot from the gui for dockers and also codes from the terminals.
root@Tower:/boot# docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE <none> <none> 600f116b71d2 9 weeks ago 1.142 GB lonix/btsync latest a5a41c440ad3 3 months ago 422.3 MB gfjardim/logitechmediaserver latest 9ea52a152291 4 months ago 882.5 MB gfjardim/crashplan latest 788c1027ec0e 4 months ago 990 MB needo/plex latest 7513a7c079c8 4 months ago 722.8 MB smdion/docker-htpcmanager latest 09054a45505d 5 months ago 526.1 MB needo/couchpotato latest ca69334311ca 6 months ago 530 MB
root@Tower:/boot# docker rmi -f 600f116b71d2 Error response from daemon: No such image: 600f116b71d2 2015/01/14 08:57:10 Error: failed to remove one or more images root@Tower:/boot# docker rmi -f 7513a7c079c8 Error response from daemon: No such image: 7513a7c079c8 2015/01/14 08:57:22 Error: failed to remove one or more images
root@Tower:/boot# docker rmi needo/plex Error response from daemon: No such image: needo/plex 2015/01/14 09:05:58 Error: failed to remove one or more images
How do I remove these two containers so I can pull in updated versions?
-
++1 on dual parity. As some drives get older, the chances of a failure are increased. If we are able to replace the drives as they get older we decrease this likelihood but with a dual parity we can be 'encouraged' to keep utilizing the older drives until a failure occurs. As others have pointed out, the probability of a similar aged drive failing during a disk rebuild is higher and a dual parity would greatly increase the confidence that data is safe.
Dual parity is definitely #1 on my list of new features. I have 6 drives in my system. It used to be the case that I needed 4 drives for storage (plus one cache and one parity), but now that hard drives are getting so large I would easily be able to dedicate 2 of them to parity: 2 parity, 3 data, 1 cache is plenty of space now that 4TB drives are commonplace.
Hard drives are currently growing more rapidly than the data that I'm accumulating, and ensuring that the array can survive 2 concurrent failures is very important to me.
-
Looks like you are running Windows 8? I have a Win 8.1 Pro and I was able to do this last week. I increased the qcow2 image by 20GB and increased the size of C: by that amount. In the windows management window, right click on the c: and chose extend. I got an initial warning that the active drive cannot be increased but went ahead with the process and in the end I saw my C: drive with increased +20GB. If you want some screenshots of any specific information let me know.
Hi,
I created a 30GB virtual qcow2 disk. The phisical disk is formatted as XFS. Later I resized my virtual disk to 60GB.
This is what I have now:
root@Tower:/mnt/vm/w8# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 7.5G 103M 7.4G 2% /boot /dev/loop0 1.8M 92K 1.6M 6% /etc/libvirt /dev/sdf1 112G 46G 67G 41% /mnt/vm
root@Tower:/mnt/vm/w8# df -T Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/sda1 vfat 7800304 104468 7695836 2% /boot /dev/loop0 ext4 1843 92 1541 6% /etc/libvirt /dev/sdf1 xfs 117162564 47828660 69333904 41% /mnt/vm
root@Tower:/mnt/vm/w8# qemu-img info w8_gaming_00.qcow2 image: w8_gaming_00.qcow2 file format: qcow2 virtual size: 60G (64424509440 bytes) disk size: 26G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false
Inside my vm I see this in disk management (see attached pic).
I tried to extend the initial 30GB volume and windows tells me it is not possible. What other way can I try to extend the disk size to the total virtual size?
-
That's good info, thank you. I imagined that parity will be rebuilt even if I am adding new empty drives. Good to know parity will be rebuilt only if the new drives have data on them. The three new drives are being precleared and will be done by tomorrow. The parity is not being upgraded, just the drives which are smaller than 3tb. I will follow what you have suggested, thanks.
The way I did it I never really "lost" parity, but also, I did not need any additional slots, which was another goal I had due to my small system.
On the other hand, my way might actually wind up making the drives work a little harder since each of the rebuilds has to read all of every drive.
If you have plenty of slots, then another possibility would be to put in all of the new drives, including the larger parity drive if you need one, but don't assign them yet. Preclear all of these new drives if you haven't already. And then
0) If you are replacing parity to make it larger, then go ahead and replace it first and let it rebuild parity with the existing configuration.
1) Assign each of the new drives to a new slot in the array one at a time. Since they have already been cleared, unRAID will only need to format them which shouldn't take very long, and you will still have parity while you do this.
2) Move the data off the drives you are going to remove, remove the drives, and rebuild parity.
If you do it this way then you will have parity during all of the data moving.
-
I am planning to replace the drives and rebuild the parity with the new replaced drives. After I replace the drives parity will be lost. The idea is no matter which way, parity will need to be rebuilt at least once. I would rather replace 3 drives and then rebuild the parity.
Do not replace the old drives and expect them to be XFS, whether they are formatted as XFS is irrelevant, the rebuild process will rebuild the drive bit for bit, including the filesystem. The rebuilt drive will be reiser when it's done. There is no way around this.
-
trurl - Looks like I am in a similar situation as you are. The best we can do with is have the parity rebuild once. Given that I am replacing 3 drives at once here is what I think would be most efficient in my scenario.
a. format the new 3 drives as xfs that is unraid compatible and rsync the data from 3 old unraid drives to the new ones.
b. REPLACE the 3 old drives with the new xfs formatted drives and add a 4th xfs drive to unraid <- parity will built after this step, only once for this entire process
c. Follow the established process of moving data from remaining existing unraid drive to the new 4th drive to convert the remaining to xfs
What I need help with is (a). How do I format a drive to unraid xfs compatible format so that I can add data to this drive and replace the older unraid drives?
Thank you for all the suggestions.
I recently converted all my array data drives to XFS. I also upsized some of my data drives like you are planning to do.
What I did was replace 3TB parity with 4TB and let it rebuild. Replace a 3TB data drive with 4TB and let it rebuild. Replace another 3TB data with 4TB and let it rebuiild.
At this point everything was still RFS, but with the extra space I was then able to move all of the data off one RFS drive onto others, and then reformat that now empty drive to XFS.
Then, move all of the data off another RFS drive onto other drives, and reformat that now empty drive to XFS.
Repeat as necessary. Except for the initial parity rebuild to upsize the parity disk, I was never running without parity. In fact since I still had that original parity disk I could have just put it back in if there was any problem.
-
Thanks Helmonder and Traxxus.
So summarize the recommended course of action:
1. add the 3 replacement disks to the current unraid array, format them as xfs and migrate the data to these three drives.
2. Remove the empty 3 drives (disks #2, #4 and #7) from unraid -> parity will be lost and a rebuild will be needed soon after this.
3. Add a spare 4TB drive to array to help move and convert the remaining 6 drives one after another to XFS so that parity is preserved during this process.
Is this the best recommended approach?
Do one thing at a time. This won't be a quick process, and if something goes wrong you want to be able to pin down when/where it happened. I wouldn't replace the disks yet, since the rebuild is going to rebuild the disk bit by bit, which includes the filesystem, so do that last.
Easiest way, assuming you have the ability/space to, would be to add the new drives you have as additional drives, format to XFS, and start with those. Copy data from non-xfs drives to those new xfs drives, then format those now empty drives. Rinse and repeat. Your total array size is 20 TB, and the new drives are 10, so that would cut down on the amount of musical chairs you have to do. Then after you are done, you can shrink your array and remove those 3 drives you wanted to remove.
If you don't have room for the new drives, then same thing, just with your existing drives.
There's a sticky about this. http://lime-technology.com/forum/index.php?topic=37490.0
-
Hi - I have an array of 12 disks including parity out of which 2 are already xfs converted. I want to replace 3 smaller disks (disks #2, #4, #7 - picture below) and convert the remaining 11-2-3=6 disks to xfs. I have in hand the 3 replacement disks (4, 3, 3 TB) and another 3 backup disks (4, 4, 4 TB).
a. I am wondering what is the best way to do this? In some ways I do not mind replacing as many disks as possible at one go since I have an external backup of my critical data.
b. If I want to "insert" a xfs formatted data disk into the array and rebuild the parity, what is the best way to do this? The last time I tried inserting a xfs formatted disk with data on it, Unraid did not recognize the format. I had to reformat it the disk in Unraid GUI and copy the data back on that disk.
Thanks!
-
Hi - I have couple of older drives that I want to pass through to my Win 8.1 KVM and use these for backups. I noticed that for a large number of smaller files (like pictures) it was better to have them in a local VM drive for quicker access and Lightroom likes it as well. This also serves as a backup for the critical media content for which I'd like multiple backups.
Is it possible to mount the drives using SNAP that are passed through to Win8.1 KVM? If I could do this, running rsync to get backups from /mnt/user would be easier. I passed through the drives using the xml code (below), formatted them in Win8.1 as ntfs. I noticed couple of issues:
a. One of the drives shows up as ntfs in SNAP and other shows with an older reiserfs format.
b. I copied few files to these two drives in both unraid terminal window and in Windows. The files copied through terminal do not show up in Windows and vice-versa for both the drives.
This makes me think I cannot access the drives in unraid if they are passed through. Is this behavior expected and what other easier options there may be to do rsync of files between HDD passthrough and /mnt/share?
xml code for HDD passthrough:
<disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-id/ata-WDC_WD15EADS-00S2B0_WD-WCAVY1215789' /> <target dev='vdb' bus='virtio' /> </disk>
-
Monkeystar - Following Jon's previous post, I would try passing the sat tuner with
<qemu:arg value='vfio-pci,host=07:00.0,bus=root.1,addr=00.2'/>
Can I get a little help on a similar issue please?
I have XBMCbuntu installed and I've added TVheadend as a TV back end (I really wanted to use OPENELEC but I can't get it installed because of the HDD driver issue, hopefully UnVM's will help with that) I've added a dual Sat tuner card to my VM and edited my XML like below including all relevant additions to go script's etc.
<qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1a.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=07:00.0,bus=pcie.0'/> </qemu:commandline>
device 01:00.0 and 01:00.1 is my AMD 6450 graphics card and sound card. 00:1a.0 is my USB controller I've had these passed through for a while and they all work great. device 07:00.0 is the new dual sat tuner card I've added. I passed it through last night and the machine has booted fine but I haven't had chance to set the card up yet. TV headend does recognise it but before i try and configure it do i need to tweak my xml at all or does it look right as i have both the USB controller and the sat card on pcie.0?
-
That explains, thanks Jon. When I changed the slot, the device showed up unknown ethernet controller in Win 8.1 device manager. Installed the drivers and the installation was smooth. However, when I checked with Ceton diagnostics, it said the device wasn't found. I use J River Media Center 20 for my HTPC and that program started being unresponsive. Even after I shut down the program, other programs showed unresponsive behavior. Forced shutdown from task manager did not work and even after destroy/start the VM the trend continued.
I finally deleted this VM image and fired up a backup VM image (did not want to deal with uninstalling the Ceton drivers). The part I love about the KVM is I deal with the entire HTPC OS as a file, take backups of images and replace them when needed, awesome!
You mentioned about another VM to try, upcoming beta release?
That setting applies to the virtual hardware assignment. So you are assigning a physical device to a virtually created PCI slot (created by QEMU). On a real bus, having both of these as .1 would be like trying to install two physical cards into the same slot.
Can you elaborate on the instability to which you are referring? Was this crashing the host or just the guest VM? Very interested to see someone with a Ceton card get it working. There is another VM I'd like to have you try once we finish figuring out your windows issues.
-
Jon - I think that worked, I was able to see the device in Win 8.1. Installed the drivers but the system became very unstable, keeps crashing often. For now I am going to disable this. I am curious about how you determined the address as addr=00.2?
Hi - I am trying to pass through a pcie x1 Ceton infinitv 4 TV tuner card. I think I am having trouble defining the correct bus and slot for this, can someone please help?
Relevant output from lspci -knn
09:00.0 PCI bridge [0604]: Tundra Semiconductor Corp. Device [10e3:8111] (rev 02) Kernel driver in use: vfio-pci 0a:08.0 Non-VGA unclassified device [0000]: Device [1b7c:0004] (rev 01) Subsystem: Device [1b7c:0004] Kernel driver in use: vfio-pci
The above two devices show up when I add this tuner card. To check I added vfio-bind of both 0000:09:00.0 and 0000:0a:08.0 and tried adding each one independently in my xml.
For the 09:00.0 address, the relevant xml part is:
<qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=09:00.0,bus=root.1,addr=00.1'/>
The output on command line:
root@Tower:/mnt/disk/SSD1/vm/image# virsh start win81x64cetonpci error: Failed to start domain win81x64cetonpci error: internal error: early end of file from monitor: possible problem: 2015-01-08T02:09:09.800674Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: vfio: Assignment of PCIe type 0x7 devices is not currently supported 2015-01-08T02:09:09.800696Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: vfio: 0000:09:00.0 Error adding PCI capability 0x10[0x3f]@0xc0: -22 2015-01-08T02:09:10.826825Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: Device initialization failed. 2015-01-08T02:09:10.826843Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: Device 'vfio-pci' could not be initialized
When I add 0a:08.0 to my xml using:
<qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=0a:08.0,bus=root.1,addr=00.1'/>
and start my domain:
root@Tower:/mnt/disk/SSD1/vm/image# virsh start win81x64cetonpci error: Failed to start domain win81x64cetonpci error: internal error: early end of file from monitor: possible problem: 2015-01-08T02:21:37.387610Z qemu-system-x86_64: -device vfio-pci,host=0a:08.0,bus=root.1,addr=00.1: PCI: slot 0 function 1 not available for vfio-pci, in use by vfio-pci 2015-01-08T02:21:37.387633Z qemu-system-x86_64: -device vfio-pci,host=0a:08.0,bus=root.1,addr=00.1: Device initialization failed. 2015-01-08T02:21:37.387640Z qemu-system-x86_64: -device vfio-pci,host=0a:08.0,bus=root.1,addr=00.1: Device 'vfio-pci' could not be initialized
It appears the second one with address 0a:08.0 may be right one but the definition is incorrect.
Change the XML for the second device to this:
<qemu:arg value='-device'/>
<qemu:arg value='vfio-pci,host=0a:08.0,bus=root.1,addr=00.2'/>
-
Hi - I am trying to pass through a pcie x1 Ceton infinitv 4 TV tuner card. I think I am having trouble defining the correct bus and slot for this, can someone please help?
Relevant output from lspci -knn
09:00.0 PCI bridge [0604]: Tundra Semiconductor Corp. Device [10e3:8111] (rev 02) Kernel driver in use: vfio-pci 0a:08.0 Non-VGA unclassified device [0000]: Device [1b7c:0004] (rev 01) Subsystem: Device [1b7c:0004] Kernel driver in use: vfio-pci
The above two devices show up when I add this tuner card. To check I added vfio-bind of both 0000:09:00.0 and 0000:0a:08.0 and tried adding each one independently in my xml.
For the 09:00.0 address, the relevant xml part is:
<qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=09:00.0,bus=root.1,addr=00.1'/>
The output on command line:
root@Tower:/mnt/disk/SSD1/vm/image# virsh start win81x64cetonpci error: Failed to start domain win81x64cetonpci error: internal error: early end of file from monitor: possible problem: 2015-01-08T02:09:09.800674Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: vfio: Assignment of PCIe type 0x7 devices is not currently supported 2015-01-08T02:09:09.800696Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: vfio: 0000:09:00.0 Error adding PCI capability 0x10[0x3f]@0xc0: -22 2015-01-08T02:09:10.826825Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: Device initialization failed. 2015-01-08T02:09:10.826843Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=pcie.0: Device 'vfio-pci' could not be initialized
When I add 0a:08.0 to my xml using:
<qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=0a:08.0,bus=root.1,addr=00.1'/>
and start my domain:
root@Tower:/mnt/disk/SSD1/vm/image# virsh start win81x64cetonpci error: Failed to start domain win81x64cetonpci error: internal error: early end of file from monitor: possible problem: 2015-01-08T02:21:37.387610Z qemu-system-x86_64: -device vfio-pci,host=0a:08.0,bus=root.1,addr=00.1: PCI: slot 0 function 1 not available for vfio-pci, in use by vfio-pci 2015-01-08T02:21:37.387633Z qemu-system-x86_64: -device vfio-pci,host=0a:08.0,bus=root.1,addr=00.1: Device initialization failed. 2015-01-08T02:21:37.387640Z qemu-system-x86_64: -device vfio-pci,host=0a:08.0,bus=root.1,addr=00.1: Device 'vfio-pci' could not be initialized
It appears the second one with address 0a:08.0 may be right one but the definition is incorrect.
-
Peter - Would it be possible to skip one or couple of application from routing through the VPN and let is go through the WAN? I need plex and madsonic to pass through, PIA VPN allows only one port forward.
Hi,
First, I did this function with help from other resources that asked for this features, and If some one can highlight to me how to verify above issue and how to solve it I would be happy, I'm far away an expert of routing.
Since I don't can't support these extra function to route traffic, I think to remove this from the plugin, and user hopefully can come up with a solution outside the plugin.
//Peter
-
Yep, I am passing the Intel controller.The right usb ports (below the PS/2 KB) are USB5 and I had trouble passing it when using Win7 (no passthrough worked for me with Win7). I have not checked passing through the USB5 port with Win8. I think most of the ports are on usb3, the Intel controller. Maybe a x1 usb pcie card could help, like this one http://www.newegg.com/Product/Product.aspx?Item=N82E16815166026?
root@Tower:~# lspci | grep USB 00:14.0 USB controller: Intel Corporation Device 8cb1 00:1a.0 USB controller: Intel Corporation Device 8cad 00:1d.0 USB controller: Intel Corporation Device 8ca6 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142
So you are using the intel controller. Crud, I was really hoping to avoid that. Aren't the four rear USB ports and the internal port all on that controller? That's a lot of ports for me to forward through when I only need one of them for my USB active extender, and that only leaves me with 2 for other machines. Maybe I did my testing wrong.
-
reluctantflux - Here is my output from lspci and the highlighted one is the one I am passing for USB (usb3/BUS 003). This config has the pci usb slots passing through, so I am not sure whether some of them are not visible to Unraid.
EDIT: looks like I cannot make the bold that is input in code format but I have not removed the bold code to highlight the relevant code.
"
root@Tower:/mnt/disk/SSD1/vm/image# lspci 00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Haswell PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Haswell PCI Express x8 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06) [b]00:14.0 USB controller: Intel Corporation Device 8cb1[/b] 00:16.0 Communication controller: Intel Corporation Device 8cba 00:19.0 Ethernet controller: Intel Corporation Device 15a1 00:1a.0 USB controller: Intel Corporation Device 8cad 00:1b.0 Audio device: Intel Corporation Device 8ca0 00:1c.0 PCI bridge: Intel Corporation Device 8c90 (rev d0) 00:1c.2 PCI bridge: Intel Corporation Device 8c94 (rev d0) 00:1c.3 PCI bridge: Intel Corporation Device 8c96 (rev d0) 00:1c.6 PCI bridge: Intel Corporation Device 8c9c (rev d0) 00:1d.0 USB controller: Intel Corporation Device 8ca6 00:1f.0 ISA bridge: Intel Corporation Device 8cc4 00:1f.2 SATA controller: Intel Corporation Device 8c82 00:1f.3 SMBus: Intel Corporation Device 8ca2 01:00.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Tahiti XT [Radeon HD 7970] 01:00.1 Audio device: AMD/ATI [Advanced Micro Devices, Inc.] Tahiti XT HDMI Audio [Radeon HD 7970 Series] 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 11) 05:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0b:00.0 USB controller: ASMedia Technology Inc. Device 1142
output from lsusb (note BUS 003 is missing here since it is being passed through)
root@Tower:/mnt/disk/SSD1/vm/image# lsusb Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 005 Device 002: ID 8564:1000 <<- This is the unraid key. Location: Leftmost bottom slot on the mobo, forward looking aft. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
vfio-bind in go, the last address is for usb pci
#For KVM videocard video & hdmi audio pass thru /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:00:14.0
my xml (bold toward the end is the pci passthrough for usb3)
<domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>win81x64pci</name> <uuid>d8d5720f-e23f-40d4-8a6b-19864c464c41</uuid> <description>win81x64pci</description> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'/> <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='qcow2' cache='none' io='native'/> <source file='/mnt/disk/SSD1/vm/image/Win81x64.qcow2'/> <backingStore/> <target dev='vdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/SSD1/vm/media/Windows81Pro.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <alias name='sata0-0-0'/> <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/disk/SSD1/vm/media/virtio-win-0.1-81.iso'/> <backingStore/> <target dev='sdd' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0e:6d:3d'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> [b] <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.0,bus=root.1,addr=00.1'/>[/b] </qemu:commandline> </domain>
So you're passing through the ASMedia controller, and not the intel one, correct? Can you show me your "Universal Serial Bus Controllers" section of Device Manager? I'm curious on if you have different host controllers showing than me. Also, I read this could be an issue with the Bios, having the USB 3.0 supporting legacy devices.
-
Hey reluctantflux - I have been meaning to ping and let you know about this but travelling this week and got busy. I tried win8.1 with the xml that I posted earlier on this thread and the Pci pass through for usb3 worked without trouble in first go. You were right about it not working in win7 though but it worked in win8.1.
My unraid key is moved to usb5 slot, bottom left side (front looking aft). I think the inside USB slot, inside usb2 headers and mobo right side slots are on usb3 which I am passing through. Can you try this config and see whether it works on your win8.1?
Merry Christmas and Happy Holidays!
EDIT: I just checked the xml I posted earlier and seems it is my first pass using usb5 pass through. If you are having trouble let me know and I can send my working version of xml. I will be back home this Monday.
htpcnewbie and I have the same motherboard, and I came across having the same issues as they were. It is not a Win7 issue, as the same thing happens in Win8. Basically, the controller shows up in device manager, but it has a yellow exclamation because it has failed to start. We have the ASRock Xtreme6 LGA1150 motherboard. Here's a few commands with their outputs:
root@Tower:~# lspci | grep ASMedia 05:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142 root@Tower:~# lsusb Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 007: ID 04f2:0841 Chicony Electronics Co., Ltd HP Multimedia Keyboard Bus 005 Device 016: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 005 Device 008: ID 046d:0a1f Logitech, Inc. G930 Bus 005 Device 006: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 005 Device 013: ID 0cf3:3002 Atheros Communications, Inc. AR3011 Bluetooth Bus 005 Device 011: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 005 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 005 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 010: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 004: ID 045e:006d Microsoft Corp. eHome Remote Control Keyboard keys Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. Bus 003 Device 002: ID 0781:5580 SanDisk Corp. SDCZ80 Flash Drive Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Tower:~# readlink /sys/bus/usb/devices/usb5 ../../../devices/pci0000:00/0000:00:1c.6/0000:0c:00.0/usb5 root@Tower:~#
-
Hi,
I recently bought an intel SAS expander RES2SV240, this is paired with IBM M1015 flashed to IT mode and firmware P19 (read few posts about P20 having issues). I am using both the SAS ports from the IBM as inputs to the Intel expander. All the disks are recognized and seems to be okay from outside. I started a parity check to see how the data transfer speeds compare without the Intel expander. It as been only few hours since I started the parity check and as of now, the speeds 'appear' to be only slightly slower. I was watching a video simultaneously on my Win8.1 KVM and noticed the video 'slightly' stutter. Checking the logs, I see some strange warnings and errors that I haven't seen before. Shown below is a snippet and I have attached the entire log. I am not sure what 'ata6' is being referred here, and whether the errors point to a lose sata cable on one disk or a sas cable or something wrong with the expander itself?
Almost all the errors seem to have occurred around 16:00 hrs.
On another note, is there a way to get a continuous record of the parity check speeds, time or % complete vs check speed in MB/s? It would be great to compare two scenarios with all the disks spinning and accessing data.
Thanks!
...
Dec 18 16:00:02 Tower kernel: ata6: EH complete
Dec 18 16:00:02 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen
Dec 18 16:00:02 Tower kernel: ata6.00: irq_stat 0x08000000, interface fatal error
Dec 18 16:00:02 Tower kernel: ata6: SError: { UnrecovData Handshk }
Dec 18 16:00:02 Tower kernel: ata6.00: failed command: WRITE DMA EXT
Dec 18 16:00:02 Tower kernel: ata6.00: cmd 35/00:00:18:77:00/00:04:00:00:00/e0 tag 7 dma 524288 out
Dec 18 16:00:02 Tower kernel: ata6.00: status: { DRDY }
Dec 18 16:00:02 Tower kernel: ata6: hard resetting link
Dec 18 16:00:02 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 18 16:00:02 Tower kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Dec 18 16:00:02 Tower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Dec 18 16:00:02 Tower kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Dec 18 16:00:02 Tower kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Dec 18 16:00:02 Tower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Dec 18 16:00:02 Tower kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Dec 18 16:00:02 Tower kernel: ata6.00: configured for UDMA/133
.....
Win7x64 - Help on install
in VM Engine (KVM)
Posted
I bought a Win 8.1 license since my attempts with Win7 for pcie passthrough weren't working, time to debug this issue was getting to be more precious than the price of a Win8.1 license. That being said, I do not have experience with Win8. I imagine Win8.1 has better support than Win8 but all Win8 licenses should work for Win 8.1, isn't that a free upgrade?
With Win7, I did not have any trouble with the audio and video passthrough. They work fine! Also usb devices passthrough using the device id's work fine. The problem with Win7 in my case was passing the entire pcie controller on which the usb devices reside. A quick primer on this- there are two ways to pass through the usb devices, first using usb device id and second passing the entire pcie controller of the usb device. In the former, you need to specify apriori which device you want to passthrough. In the latter, any device that is plugged into that controller gets passed through - a truly plug n play device port. For passing though a pci device, you need to vfio-bind the device address. Once you identify this address you can put that in the /boot/config/go file so that it gets vfio-bind every time a reboot occurs. For passing through the videocard and audio, you need to do this and that's where the vfio-bind references occur. Beware that once you vfio-bind an address, Unraid cannot see that pci device and you will need to reboot.
The plugins are in Unraid and not dependent on the KVM. Are you planning to install Plex and XBMC in the Windows KVM? I am using Plex docker and it works perfectly. I haven't tried XBMC plugin or docker. There is an active discussion about installing a headless XBMC docker and I believe it is still under development. I have XBMC (known as Kodi now) installed in my Win8.1 and works well. However, my primary HTPC media organizer is J River Media Center.