Espressomatic Posted August 30 Share Posted August 30 (edited) I'm running 7 beta 2, so I don't know if this is a new issue. I'm trying to add a couple of command-line arguments to QEMU for a particular VM in the text box in the VM edit UI: After updating/saving and then coming back to edit, the arguments are gone, like this: If I display the inline XML (new feature), there's no XML displayed for this section - and going full XML view I can't find where these arguments should be inserted. Can anyone validate this with Unraid 6.x? Edited August 30 by Espressomatic Quote Link to comment
Solution SimonF Posted August 30 Solution Share Posted August 30 1 hour ago, Espressomatic said: I'm running 7 beta 2, so I don't know if this is a new issue. I'm trying to add a couple of command-line arguments to QEMU for a particular VM in the text box in the VM edit UI: After updating/saving and then coming back to edit, the arguments are gone, like this: If I display the inline XML (new feature), there's no XML displayed for this section - and going full XML view I can't find where these arguments should be inserted. Can anyone validate this with Unraid 6.x? You need to use libvirt xml format i.e. <qemu:commandline> <qemu:arg value='-vga'/> <qemu:arg value='vmware'/> </qemu:commandline> https://libvirt.org/kbase/qemu-passthrough-security.html Quote Link to comment
Espressomatic Posted August 30 Author Share Posted August 30 (edited) 59 minutes ago, SimonF said: You need to use libvirt xml format i.e. <qemu:commandline> <qemu:arg value='-vga'/> <qemu:arg value='vmware'/> </qemu:commandline> https://libvirt.org/kbase/qemu-passthrough-security.html Thanks for the heads up! Kind of thought the UI would create the XML based on what I typed into that box - sort of like every other form element on the page. If the box were pre-populated with <qemu:commandline> </qemu:commandline> then it would be instantly obvious what needed to be done. Edited August 30 by Espressomatic Quote Link to comment
Espressomatic Posted August 30 Author Share Posted August 30 (edited) Still can't get it to work. I'm in a hurry, about to head out the door, but the whole format (according to that link) seems completely obnoxious. Mainly because of the butchered XML - and the fact they're not using a nice structure of keys and values. Ugh... Ugly. But here's what I'd been trying to do, finally working: <qemu:commandline> <qemu:arg value='-boot'/> <qemu:arg value='menu=on,splash-time=5000'/> </qemu:commandline> Edited August 31 by Espressomatic Quote Link to comment
SimonF Posted September 2 Share Posted September 2 On 8/30/2024 at 7:42 PM, Espressomatic said: Kind of thought the UI would create the XML based on what I typed into that box - sort of like every other form element on the page. The amount of variables would be to large. Libvirt drop support for a similar process. Unfortunately support for the domxml-from-native command has been removed from recentish libvirt, because we found that in practice it was too unreliable and incomplete to be useful. There are two options other is qemu:override I will review help text. 1 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.