[libvirt] libvirt compiles on RISC-V (RV64G)
I'm happy to announce that libvirt compiles fine from git on Fedora/RISC-V. This has little or no practical value at all, since RISC-V lacks such essentials such as virtualization, qemu etc. However I suppose you could use it as a remote client. # file src/.libs/libvirt.so.0.2004.0 src/.libs/libvirt.so.0.2004.0: ELF 64-bit LSB shared object, UCB RISC-V, version 1 (SYSV), dynamically linked, BuildID[sha1]=525ed42ce6d1284c6a909bd6f1b0d6181e88af7b, not stripped # file tools/.libs/virsh tools/.libs/virsh: ELF 64-bit LSB shared object, UCB RISC-V, version 1 (SYSV), dynamically linked, interpreter /lib/ld.so.1, for GNU/Linux 2.6.32, BuildID[sha1]=67e2b69f9007c02137545fed1b7fd9b2871740ee, not stripped Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
On Wed, 2016-10-26 at 12:35 +0100, Richard W.M. Jones wrote:
I'm happy to announce that libvirt compiles fine from git on Fedora/RISC-V. This has little or no practical value at all, since RISC-V lacks such essentials such as virtualization, qemu etc. However I suppose you could use it as a remote client.
Did you actually try connecting to a remote libvirtd instance from the RISC-V machine? Does the test suite pass? Anyway, awesome news! Thanks for sharing, and keep up the good work :) -- Andrea Bolognani / Red Hat / Virtualization
On Wed, Oct 26, 2016 at 05:29:26PM +0200, Andrea Bolognani wrote:
On Wed, 2016-10-26 at 12:35 +0100, Richard W.M. Jones wrote:
I'm happy to announce that libvirt compiles fine from git on Fedora/RISC-V. This has little or no practical value at all, since RISC-V lacks such essentials such as virtualization, qemu etc. However I suppose you could use it as a remote client.
Did you actually try connecting to a remote libvirtd instance from the RISC-V machine?
No, the qemu emulation has no networking (real hardware will of course have networking).
Does the test suite pass?
I didn't try it. It's not massively important that libvirt actually works until the hypervisor specification is sorted out, and real hardware is widely available. Mainly the team want libvirt in order just to satify deps required to build other packages. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
On Wed, 2016-10-26 at 16:47 +0100, Richard W.M. Jones wrote:
I'm happy to announce that libvirt compiles fine from git on Fedora/RISC-V. This has little or no practical value at all, since RISC-V lacks such essentials such as virtualization, qemu etc. However I suppose you could use it as a remote client. Did you actually try connecting to a remote libvirtd instance from the RISC-V machine? No, the qemu emulation has no networking (real hardware will of course have networking).
Fair enough :)
Does the test suite pass? I didn't try it.
I realized the test suite is run as part of the RPM build, so if the RPM build succeeded it means the test suite must have passed! Yay! \o/
It's not massively important that libvirt actually works until the hypervisor specification is sorted out, and real hardware is widely available. Mainly the team want libvirt in order just to satify deps required to build other packages.
I assume packages that depend or build-depend on libvirt actually care about libvirt working :) You don't want to end up with a bunch of fully built packages that crash horribly the second you start using them ;) -- Andrea Bolognani / Red Hat / Virtualization
On Thu, Oct 27, 2016 at 09:56:07AM +0200, Andrea Bolognani wrote:
On Wed, 2016-10-26 at 16:47 +0100, Richard W.M. Jones wrote:
I'm happy to announce that libvirt compiles fine from git on Fedora/RISC-V. This has little or no practical value at all, since RISC-V lacks such essentials such as virtualization, qemu etc. However I suppose you could use it as a remote client. Did you actually try connecting to a remote libvirtd instance from the RISC-V machine? No, the qemu emulation has no networking (real hardware will of course have networking).
Fair enough :)
Does the test suite pass? I didn't try it.
I realized the test suite is run as part of the RPM build, so if the RPM build succeeded it means the test suite must have passed! Yay! \o/
Unfortunately not - I was building libvirt from git (in case it needed any changes). We're missing quite a few packages before libvirt can be built from the RPM, see these files (although they are a bit out of date): https://fedorapeople.org/groups/risc-v/logs/libvirt/ As new packages get built for Fedora 25, we are picking them up automatically and trying to build them for RISC-V: https://fedorapeople.org/groups/risc-v/autobuilder-status.html
It's not massively important that libvirt actually works until the hypervisor specification is sorted out, and real hardware is widely available. Mainly the team want libvirt in order just to satify deps required to build other packages.
I assume packages that depend or build-depend on libvirt actually care about libvirt working :) You don't want to end up with a bunch of fully built packages that crash horribly the second you start using them ;)
QA-ing the whole thing, beyond simple testing by hand, is quite difficult especially without solid hardware. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
participants (2)
-
Andrea Bolognani -
Richard W.M. Jones