Hi, Any other comments for this topic?
BR, Zhenyu On Mon, Jul 20, 2020 at 9:17 AM Zhenyu Zheng <[email protected]> wrote: > Hi Nir, > > Thanks alot for the quick response and information, actually I also > worked a little bit on libvirt and other from our > team has experiences in qemu, those projects works OK on ARM platform, it > is just the capability might be less > when comparing to other platforms, for example, myself just added the > getHost() capability for ARM64 in libvirt and > now planning to work on compareCPU() API, after that we will have better > migration workflow on ARM platform. > > For resources, actually, yes, I think we can provide those for oVirt > community, could you tell me more details about > what kind of resources are more suitable, our current resources are mostly > VMs from public cloud, will that be OK? > > BR, > > Zhenyu > > On Mon, Jul 20, 2020 at 2:07 AM Nir Soffer <[email protected]> wrote: > >> On Sun, Jul 19, 2020 at 5:04 PM Zhenyu Zheng <[email protected]> >> wrote: >> > >> > Hi oVirt, >> > >> > We are currently trying to make oVirt work on ARM64 platform, since I'm >> quite new to oVirt community, I'm wondering what is the current status >> about ARM64 support in the oVirt upstream, as I saw the oVirt Wikipedia >> page mentioned there is an ongoing efforts to support ARM platform. We have >> a small team here and we are willing to also help to make this work. >> >> Hi Zhenyu, >> >> I think this is a great idea, both supporting more hardware, and >> enlarging the oVirt >> community. >> >> Regarding hardware support we depend mostly on libvirt and qemu, and I >> don't know >> that is the status. Adding relevant lists and people. >> >> I don't know about any effort on oVirt side, but last week I added >> arm builds for >> ovirt-imageio and it works: >> >> https://copr.fedorainfracloud.org/coprs/nsoffer/ovirt-imageio-preview/build/1555705/ >> >> We have many dependendencies, but oVirt itself is mostly python and java, >> with >> tiny bits in C or using ctypes, so it should not be too hard. >> >> I think the first thing is getting some hardware for testing. Do you >> have such hardware, >> or have some contacts that can help to get hardware contribution for this? >> >> Nir >> >>
