On Thu, 27 Jun 2019 at 15:24, Paul Wouters <[email protected]> wrote: > > I build rpms on east or west usually. I guess I could use the “build” machine > but that sounds more complicated if I need to do them a lot to test something.
OTOH, the memory requirements for normal testing just doubled :-( Building and installing on "build" then cloning to the test VMs is much faster. If you're doing it a lot then perhaps a make target that automates the entire sequence which is something like: make kvm-uninstall-test-domains ./testing/utils/kvmsh.py --shutdown --chdir . build rpmbuild make kvm-install-test-domains ? > Paul > > Sent from mobile device > > > On Jun 27, 2019, at 13:48, Andrew Cagney <[email protected]> wrote: > > > >> On Thu, 27 Jun 2019 at 13:30, Paul Wouters <[email protected]> wrote: > >> > >>> On Thu, 27 Jun 2019, Andrew Cagney wrote: > >>> > >>> Have you tried doing this on the big bloated build machine: > >>> > >>> $ sudo virsh dominfo build > >>> Max memory: 524288 KiB > >>> Used memory: 524288 KiB > >> > >> With 512mb it works for me inside rpmbuild too? So I assume it works too > >> here? > >> > >>> $ make kvmsh-build > >>> [root@swanbase ~]# cd /source > >>> [root@swanbase source]# make man > >>> [root@swanbase source]# ... > >> > >> I'm confused what you are trying to tell me? > > > > The build domain, which can be logged into using: > > > > $ make kvmsh-build > > > > has 512mb of ram and should be sufficient for running xmlto (make man) > > and rpmbuild (make ?). It even has internet access. > > > > Have you tried using that (I don't think the test VMs need their ram > > increased). > _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
