Arbadacarba Posted April 28, 2022 Author Share Posted April 28, 2022 Sorry, I've been busy with work and away, and have a 4 year old so... Got this to run without throwing up any errors but the VM doesn't see the card any more: VM.xmljupiter-diagnostics-20220427-2336.zip Quote Link to comment
ghost82 Posted April 28, 2022 Share Posted April 28, 2022 (edited) 3 hours ago, Arbadacarba said: Got this to run without throwing up any errors but the VM doesn't see the card any more Hi, I'm not 100% sure, because in the diagnostics logs the latest messages in qemu don't seem to be correct in disabling device.json: -device '{"driver":"vfio-pci","host":"0000:05:00.0","id":"hostdev0","bus":"pci.0","addr":"0x6"}' \ The above is in json format. However it's strange that you are able to run the vm without any error with the current xml... If limetech updated qemu without updating libvirt, maybe you need to change in the xml from this: <qemu:capabilities> <qemu:del capability='device.json'/> </qemu:capabilities> to this: <qemu:capabilities> <qemu:del capability='device.json+hotplug'/> </qemu:capabilities> Worth a try... Attach new diagnostics with this change. It's a pity that the new libvirt isn't included in RC5, but I saw that you already wrote it in the appropriate thread. Edited April 28, 2022 by ghost82 1 Quote Link to comment
Arbadacarba Posted April 28, 2022 Author Share Posted April 28, 2022 I was wrong... it is working... I just hadn't configured it correctly in the pfsense software... Now I need to find a supply of compatible USB network devices for my clients... Small medical clinics that run their medical records through an online service provider... If their internet is down they lose ALL ability to function. Can't even call the patients to cancel the appointments because they cannot see who is coming or their contact info. A secondary internet connection is an option but at a cost of 100$ a month for a service they will hopefully never use... It's a hard sell... But if I can give them the ability to turn their hotspot on, on the office admin's phone to get access... Thanks ghost82... I wish it was more seamless, (on unraids part) but I'm very thankful that you were there to help. 1 Quote Link to comment
ghost82 Posted May 8, 2022 Share Posted May 8, 2022 Just for info, now unraid 6.10RC7 includes libvirt 8.2.0, so this applies from this version: <qemu:override> <qemu:device alias='YOURALIASHERE'> <qemu:frontend> <qemu:property name='x-msix-relocation' type='string' value='bar2'/> </qemu:frontend> </qemu:device> </qemu:override> Quote Link to comment
Arbadacarba Posted May 22, 2022 Author Share Posted May 22, 2022 Sitting here with no internet... Unsure of why as of yet, we had a huge storm, but it went offline much later. Thought I would give this a try now that I'm on 6.10 final... And no luck. I attempted to start with the non working version of the xml (Added the cards and made the addition above (Manually adding the alias)) Here's the xml that I'm trying... it still appears to be removing Alias' though, so I manually inserted one. pfsense try.xml Then it spits out this error: And then I get this when I go back in to look at the xml: pfsense result.xml And Diagnostics: jupiter-diagnostics-20220521-2218.zip Thanks AGAIN, Quote Link to comment
Arbadacarba Posted May 22, 2022 Author Share Posted May 22, 2022 (edited) Tried backing up a step: another try.xml With the result: Added Diagnostics jupiter-diagnostics-20220522-1411.zip Edited May 22, 2022 by Arbadacarba Added Diags Quote Link to comment
ghost82 Posted May 22, 2022 Share Posted May 22, 2022 Hi, only the "another try" seems to be correctly configured: however there's no diagnostics, so we cannot see why it fails. The other xmls, including that inside diagnostics have no trace of the override block, and this cause the error. Please attach diagnostics with the correctly modified override block. 1 Quote Link to comment
Arbadacarba Posted May 22, 2022 Author Share Posted May 22, 2022 (edited) Thanks Ghost82 I will do so Edited May 22, 2022 by Arbadacarba Quote Link to comment
Arbadacarba Posted May 24, 2022 Author Share Posted May 24, 2022 jupiter-diagnostics-20220522-1411.zip Diagnostics after attempting to boot "another Try" vm. Quote Link to comment
ghost82 Posted May 24, 2022 Share Posted May 24, 2022 1 minute ago, Arbadacarba said: Diagnostics after attempting to boot "another Try" vm. mmm nope and pfSense - Cerberus has not the new block. Can you retry? Quote Link to comment
Arbadacarba Posted May 25, 2022 Author Share Posted May 25, 2022 Created a new VM and pasted the xml in... Tried again with same results... Immediately saved Diagnotics... Hopefully it shows up this time... pfsense - Test jupiter-diagnostics-20220524-2255.zip Quote Link to comment
ghost82 Posted May 25, 2022 Share Posted May 25, 2022 mmm for some reason it is not saving the block in the vm, sorry to re-ask again, are you sure you are saving correctly the xml? Paste the xml, save, open again the xml, does the block is there? Quote Link to comment
ghost82 Posted May 25, 2022 Share Posted May 25, 2022 (edited) It seems another user has having issues in saving custom things in his xml, starting in 6.10...can you try the virsh command, i.e. in terminal 'virsh edit 'name of vm'' to see if it works there? Edited May 25, 2022 by ghost82 Quote Link to comment
ghost82 Posted May 25, 2022 Share Posted May 25, 2022 (edited) I think I found the issue: when you edit a vm in the xml view make 2 changes: on the top of the xml, change this line: <domain type='kvm'> with this: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> Then, add the block at the bottom. Once you made your changes save the xml and it will be saved correctly. Just tried this with unraid 6.10.1 and for some odd behavior it strips the xmlns line with the validation schemas...Even more odd is that it exits like if you saved it, but it didn't. Using virsh edit command fails too (obviously because the xml lacks the validation schemas too), but at least it points to an understandable error. Edited May 25, 2022 by ghost82 Quote Link to comment
Arbadacarba Posted May 27, 2022 Author Share Posted May 27, 2022 (edited) On 5/25/2022 at 2:09 AM, ghost82 said: mmm for some reason it is not saving the block in the vm, sorry to re-ask again, are you sure you are saving correctly the xml? Paste the xml, save, open again the xml, does the block is there? Just tried again as I have a few minutes, ans when I reoponed it the block was gone... Interestingly so is the last part of the seclabel section: </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> This is what I saved: </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:override> <qemu:device alias='hostdev0'> <qemu:frontend> <qemu:property name='x-msix-relocation' type='string' value='bar2'/> </qemu:frontend> </qemu:device> </qemu:override> </domain> Maybe that's ok? I know this is not your problem, and I sure appreciate your help... But where? do we go from here? I don't understand the issue well enough to create a bug report. Arbadacarba Edited May 27, 2022 by Arbadacarba Quote Link to comment
ghost82 Posted May 27, 2022 Share Posted May 27, 2022 8 minutes ago, Arbadacarba said: Just tried again as I have a few minutes, ans when I reoponed it the block was gone... did you edit also the wrong domain line? <domain type='kvm'> without the schemas the xml will not validate and it will not save the block. But if you modify that line as written in my last post the block will save, I tried it. Quote Link to comment
Arbadacarba Posted May 27, 2022 Author Share Posted May 27, 2022 I actually did... but it wiped that out too... I tried changing just that and making a trivial change to the name of the VM... the name change stuck, but: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> reverted back to: <domain type='kvm'> This is all in the GUI... Maybe I missed something... Did it work if edited in CLI? Quote Link to comment
ghost82 Posted May 27, 2022 Share Posted May 27, 2022 (edited) Try with virsh command, look at this thread: https://forums.unraid.net/topic/123933-unraid-610-win10-vm-not-able-to-start-intel-btwifi-3168-device-error-code-10/?do=findComment&comment=1130894 export nano as editor then run virsh edit, save with ctrl+o Edited May 27, 2022 by ghost82 Quote Link to comment
Arbadacarba Posted May 27, 2022 Author Share Posted May 27, 2022 First off, thank you for the export nano note... I had just figured that out... I hate VI with a passion. Doesn't seem to save from there either... Save to a temp file? Quote Link to comment
ghost82 Posted May 27, 2022 Share Posted May 27, 2022 I confirm there's a problem that needs to be investigated. Will update. 1 Quote Link to comment
Arbadacarba Posted June 20, 2022 Author Share Posted June 20, 2022 For now I've installed a USB wifi Dongle that seems to be working, but I really would like to use the one inside the machine. Quote Link to comment
ghost82 Posted June 20, 2022 Share Posted June 20, 2022 (edited) I'm continuing to follow this, don't worry I don't forget. As soon as unraid will be out with something different for virtualization (and/or libvirt and/or qemu) I will test it and let you know. But for now...it's bugged... Edited June 20, 2022 by ghost82 1 Quote Link to comment
Arbadacarba Posted March 27, 2023 Author Share Posted March 27, 2023 Debating if anything is changing in 6.12... May try again 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.