methanoid Posted April 5, 2021 Share Posted April 5, 2021 (edited) QEMU package normally contains flavours so QEMU-Arm, QEMU-PPC etc. Would enable the virtualisation of additional machines like PPC-Macs, AmigaOne PPC and so on. I've seen videos of both running well on x86 machines with QEMU-PPC Edited April 6, 2021 by methanoid 1 Quote Link to comment
uek2wooF Posted April 15, 2021 Share Posted April 15, 2021 +1 for qemu-system-ppc, -s390x, -sparc, and well anything else I might need someday. Quote Link to comment
uek2wooF Posted April 15, 2021 Share Posted April 15, 2021 Oh and to the OP, what I do is just run fedora in a kvm and then install all the qemu-sytem-* emulations I want in there. The nested kvm performance seems ok, I am not doing any heavy lifting in mine (ppc and s390x). Quote Link to comment
BillDStrong Posted May 3, 2022 Share Posted May 3, 2022 I don't think those use nesting, they use the jit to run code. Nesting is for the same system arch only, so x86-64 int the case of Unraid. Quote Link to comment
SimonF Posted October 7, 2022 Share Posted October 7, 2022 On 4/5/2021 at 1:54 PM, methanoid said: QEMU package normally contains flavours so QEMU-Arm, QEMU-PPC etc. Would enable the virtualisation of additional machines like PPC-Macs, AmigaOne PPC and so on. I've seen videos of both running well on x86 machines with QEMU-PPC PPC aarm64 and riscv have been added. But no template support just binaries. Quote Link to comment
methanoid Posted May 30, 2023 Author Share Posted May 30, 2023 On 10/7/2022 at 9:23 PM, SimonF said: PPC aarm64 and riscv have been added. But no template support just binaries. I missed the notification for this but not running unRAID right now but coming back V soon. I dont suppose you know if you have SIO's MacInABox running (it adds the Virt-manager interface) if the Qemu-PPC and Qemu-Arm etc options show up in that? I'd love to have my unRAID box (when its back) run everything I could ever want Quote Link to comment
SimonF Posted May 30, 2023 Share Posted May 30, 2023 7 hours ago, methanoid said: I missed the notification for this but not running unRAID right now but coming back V soon. I dont suppose you know if you have SIO's MacInABox running (it adds the Virt-manager interface) if the Qemu-PPC and Qemu-Arm etc options show up in that? I'd love to have my unRAID box (when its back) run everything I could ever want Sorry I dont run MacOS but do have virt manager running undrr docker will check. 1 Quote Link to comment
methanoid Posted May 21 Author Share Posted May 21 On 5/30/2023 at 9:22 PM, SimonF said: Sorry I dont run MacOS but do have virt manager running undrr docker will check. patiently waiting last year for that check Quote Link to comment
SimonF Posted May 21 Share Posted May 21 8 hours ago, methanoid said: patiently waiting last year for that check So sorry I thought had replied. Quote Link to comment
bmartino1 Posted May 21 Share Posted May 21 39 minutes ago, SimonF said: So sorry I thought had replied. is that the virt-man docker? I usually have to grab proxmox QEMU code and use xml qemu commands to get this to work in unraid. https://github.com/m-bers/docker-virt-manager For some reason it no longer in the Comuntiy app store with lattest 6.12.10 I remember else where in another form post that the template floats. flash drive \config\plugins\dockerMan\templates-user my-Virt-Manager.xml Quote Link to comment
SimonF Posted May 21 Share Posted May 21 41 minutes ago, bmartino1 said: is that the virt-man docker? I usually have to grab proxmox QEMU code and use xml qemu commands to get this to work in unraid. https://github.com/m-bers/docker-virt-manager For some reason it no longer in the Comuntiy app store with lattest 6.12.10 I remember else where in another form post that the template floats. flash drive \config\plugins\dockerMan\templates-user my-Virt-Manager.xml 2.37 kB · 0 downloads Yes this is my template. <?xml version="1.0"?> <Container version="2"> <Name>Virt-Manager</Name> <Repository>mber5/virt-manager:latest</Repository> <Registry>https://hub.docker.com/r/mber5/virt-manager</Registry> <Network>bridge</Network> <MyIP/> <Shell>sh</Shell> <Privileged>false</Privileged> <Support/> <Project/> <Overview>The virt-manager application is a desktop user interface for managing virtual machines through libvirt.
 It primarily targets KVM VMs.
 It presents a summary view of running domains, their live performance &amp; resource utilization statistics, wizards enable the creation of new domains, and configuration &amp; adjustment of a domain’s resource allocation &amp; virtual hardware. An embedded VNC and SPICE client viewer presents a full graphical console to the guest domain.</Overview> <Category>Tools:Utilities</Category> <WebUI>http://[IP]:[PORT:80]</WebUI> <TemplateURL>https://raw.githubusercontent.com/redvex2460/docker-templates/master/redvex2460/virt-manager.xml</TemplateURL> <Icon>https://raw.githubusercontent.com/redvex2460/docker-templates/master/redvex2460/images/vman.png</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <DateInstalled>1682756013</DateInstalled> <DonateText>If you like my work please consider Donating.</DonateText> <DonateLink>https://paypal.me/RedVex2460Gaming</DonateLink> <Requires/> <Config Name="libvirt-sock" Target="/var/run/libvirt/libvirt-sock" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/var/run/libvirt/libvirt-sock</Config> <Config Name="images" Target="/var/lib/libvirt/images" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/var/lib/libvirt/images</Config> <Config Name="/dev/kvm" Target="/dev/kvm" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/dev/kvm</Config> <Config Name="HOSTS" Target="HOSTS" Default="" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="false">['qemu:///system']</Config> <Config Name="RootFolder" Target="/root" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/vman/root</Config> <Config Name="WEBGUI" Target="80" Default="" Mode="tcp" Description="" Type="Port" Display="always" Required="false" Mask="false">8185</Config> </Container> 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.