Question about emulating ARM using oVirt
--_000_d4def217330a4755862e229ac6fd32c4IPESRVMAILipesystemsloc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi and just wanted to say love oVirt. I'm using oVirt 3.5 on Fedora20 to help with are devel/testing needs. Are s= oftware runs on top of Linux both in Intel and ARM platforms. While oVirt = can handle very well the intel side of things I still need to run everythin= g on ARM on real hardware. What I'm wondering is there a plan to support at= least ARM emulation using QEMU now libVirt has been fixed. Thank Chapman.... --_000_d4def217330a4755862e229ac6fd32c4IPESRVMAILipesystemsloc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-language:EN-US;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate {mso-style-priority:99; mso-style-link:"Balloon Text Char"; margin:0cm; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif"; mso-fareast-language:EN-US;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} span.BalloonTextChar {mso-style-name:"Balloon Text Char"; mso-style-priority:99; mso-style-link:"Balloon Text"; font-family:"Tahoma","sans-serif";} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri","sans-serif"; mso-fareast-language:EN-US;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Hi and just wanted to say love oVirt. <o= :p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">I’m using oVirt 3.5 on Fedora20 to help with a= re devel/testing needs. Are software runs on top of Linux both in Intel and= ARM platforms. While oVirt can handle very well the intel side of th= ings I still need to run everything on ARM on real hardware. What I’m wondering is there a plan to support at leas= t ARM emulation using QEMU now libVirt has been fixed. <o:p></o:p></p=
<p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Thank<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Chapman….<span style=3D"mso-fareast-language:E= N-GB"><o:p></o:p></span></p> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </body> </html> --_000_d4def217330a4755862e229ac6fd32c4IPESRVMAILipesystemsloc_--
On 12/11/2014 06:16 AM, Richard Chapman wrote:
Hi and just wanted to say love oVirt.
I’m using oVirt 3.5 on Fedora20 to help with are devel/testing needs. Are software runs on top of Linux both in Intel and ARM platforms. While oVirt can handle very well the intel side of things I still need to run everything on ARM on real hardware. What I’m wondering is there a plan to support at least ARM emulation using QEMU now libVirt has been fixed.
Thank
Chapman….
I can't say there is a real plan to do so at this point, but it shouldn't block you from writing a custom hook changing the xml we pass to libvirt to envoke qemu-kvm with arm instead of qemu-kvm. you can (ab)use maybe some existing behaviors/properties, as well as add more of your own via custom properties (and for fancy - custom ui plugins to show those custom properties in the proper dialogs) I'd say that's a good start to adding such support as an add-on, before considering it in the main code base. that's actually how we sometime develop a new feature - first "try it for sanity" via a custom hook to understand its scope and the issues.
Thank for the pointers I'll try it over xmas :) Chapman.... -----Original Message----- From: Itamar Heim [mailto:iheim@redhat.com] Sent: 12 December 2014 13:09 To: Richard Chapman; Devel@ovirt.org Cc: Michal Skrivanek; Dan Kenigsberg; Scott Herold; Barak Azulay Subject: Re: [ovirt-devel] Question about emulating ARM using oVirt On 12/11/2014 06:16 AM, Richard Chapman wrote:
Hi and just wanted to say love oVirt.
I'm using oVirt 3.5 on Fedora20 to help with are devel/testing needs. Are software runs on top of Linux both in Intel and ARM platforms. While oVirt can handle very well the intel side of things I still need to run everything on ARM on real hardware. What I'm wondering is there a plan to support at least ARM emulation using QEMU now libVirt has been fixed.
Thank
Chapman....
I can't say there is a real plan to do so at this point, but it shouldn't block you from writing a custom hook changing the xml we pass to libvirt to envoke qemu-kvm with arm instead of qemu-kvm. you can (ab)use maybe some existing behaviors/properties, as well as add more of your own via custom properties (and for fancy - custom ui plugins to show those custom properties in the proper dialogs) I'd say that's a good start to adding such support as an add-on, before considering it in the main code base. that's actually how we sometime develop a new feature - first "try it for sanity" via a custom hook to understand its scope and the issues.
On Dec 15, 2014, at 12:37 , Richard Chapman <richard.chapman@ipe-systems.co.uk> wrote:
Thank for the pointers I'll try it over xmas :)
also, if it helps you may want to check out some of the patches done by Eldorado guys when they were adding Power7 support. There were quite a few patches directly adding the support, but while I would agree the custom properties and hooks are best at this point it still can help you to understand all the different places… Look at our gerrit, master branch, 2013 onwards, and filter these guys: owner:"Leonardo Bianconi <lbianc@gmail.com>" owner:"Gustavo Frederico Temple Pedrosa <gustavo.pedrosa@eldorado.org.br>" owner:"Vitor de Lima <vdelima@redhat.com>" Thanks, michal
Chapman....
-----Original Message----- From: Itamar Heim [mailto:iheim@redhat.com] Sent: 12 December 2014 13:09 To: Richard Chapman; Devel@ovirt.org Cc: Michal Skrivanek; Dan Kenigsberg; Scott Herold; Barak Azulay Subject: Re: [ovirt-devel] Question about emulating ARM using oVirt
On 12/11/2014 06:16 AM, Richard Chapman wrote:
Hi and just wanted to say love oVirt.
I'm using oVirt 3.5 on Fedora20 to help with are devel/testing needs. Are software runs on top of Linux both in Intel and ARM platforms. While oVirt can handle very well the intel side of things I still need to run everything on ARM on real hardware. What I'm wondering is there a plan to support at least ARM emulation using QEMU now libVirt has been fixed.
Thank
Chapman....
I can't say there is a real plan to do so at this point, but it shouldn't block you from writing a custom hook changing the xml we pass to libvirt to envoke qemu-kvm with arm instead of qemu-kvm. you can (ab)use maybe some existing behaviors/properties, as well as add more of your own via custom properties (and for fancy - custom ui plugins to show those custom properties in the proper dialogs)
I'd say that's a good start to adding such support as an add-on, before considering it in the main code base. that's actually how we sometime develop a new feature - first "try it for sanity" via a custom hook to understand its scope and the issues.
participants (3)
-
Itamar Heim -
Michal Skrivanek -
Richard Chapman