similar to: [PATCH] virt-v2v: silence P2V build error on x86_64

On 4/21/20 1:36 AM, Todd Lewis wrote: > Works perfectly thank you. > I did get an issue when trying to compile an rpm > > The autobuild did run into an error when trying to create the rpm. > Not a big deal. I can make my own spec file. > > EXTRA_RELEASE="" 1: ^^^ > if [ -x /usr/bin/rpmbuild ] > then > rpmbuild --nodeps \ > --define

--- autobuild.sh | 40 +++++++++++++++++++++++++++++++++++ autogen.sh | 65 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 105 insertions(+), 0 deletions(-) create mode 100755 autobuild.sh diff --git a/autobuild.sh b/autobuild.sh new file mode 100755 index 0000000..8a90a78 --- /dev/null +++ b/autobuild.sh @@ -0,0 +1,40 @@ +#!/bin/sh +#oVirt viewer autobuild

* .gitignore: Ignore RPM specfile & coverage data * Build.PL: Generate specfile during build * autobuild.sh: Build control file * virt-v2v.spec.PL: RPM specfile * MANIFEST.SKIP: Ignore test coverage data --- .gitignore | 3 + Build.PL | 3 +- MANIFEST | 3 + MANIFEST.SKIP | 1 + autobuild.sh | 65 ++++++++++++++++++++++ virt-v2v.spec.PL | 160

- perform dns lookup on hostname, - randomize local tunnel port - simple autobuild script - bump rpm spec version --- autobuild.sh | 41 +++++++++++++++++++++++++++++++++++++++++ main.c | 14 +++++--------- ovirt-viewer.spec | 9 ++++++++- tunnel.c | 29 ++++++++++++++++++++--------- 4 files changed, 74 insertions(+), 19 deletions(-) create mode 100755

Cool. I'll try it out On Thu, Apr 16, 2020 at 8:38 AM Michal Privoznik <mprivozn@redhat.com> wrote: > > On 4/14/20 6:49 PM, Todd Lewis wrote: > > I was looking for a virDomainSnapshotCurrent > > I wish I had time to learn to properly Code in C, haven't touch it > > since that late 90's > > I'm only only coding in php out of necessity. > >

Works perfectly thank you. I did get an issue when trying to compile an rpm The autobuild did run into an error when trying to create the rpm. Not a big deal. I can make my own spec file. EXTRA_RELEASE="" if [ -x /usr/bin/rpmbuild ] then rpmbuild --nodeps \ --define "extra_release $EXTRA_RELEASE" \ --define "_sourcedir `pwd`" \ -ba --clean

update server autobuild to set up a new isolated vm environment and go through the server installer process and rails tests --- autobuild.sh | 65 ++++++++++++++++++++++++++++++++++++++++++ ovirt-installer-test-answers | 21 +++++++++++++ ovirt-server-test.ks | 37 ++++++++++++++++++++++++ 3 files changed, 123 insertions(+), 0 deletions(-) create mode 100644

The following two patches fixes / reimplements the oVirt appliance project, installing the entire oVirt stack including all server and node components on one machine. These patches are intended to be checked out and used to build the appliance rpm, after which it is installed provides the /usr/sbin/ovirt-appliance-ctrl script to install/uninstall the appliance. The first patch merely removes

The $vmdk value is a directory name in ESX.pm, although the later codes replace '/' with '_', the volume name isn't still friendly, for example, it looks like this: # virsh vol-list pool-dir Name Path ----------------------------------------- esx4.1-rhel6.2-x86_64_esx4.1-rhel6.2-x86_64

Hello, I am managing several virtual machines (a predefined set) with virsh, and I would like to make sure that all VMs are booted when the host reboots. What is the recommended approach for this? Thanks, Daniel Gonzalez -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, i got this error during build: make[2]: Entering directory `/home/panter/ovirt/node' { test ! -d "ovirt-node-1.0.3" || { find "ovirt-node-1.0.3" -type d ! -perm -200 -exec chmod u+w {} ';' && rm -fr "ovirt-node-1.0.3"; }; } test -d "ovirt-node-1.0.3" || mkdir "ovirt-node-1.0.3" (cd gptsync && make

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of

On 02/14/2012 11:01 AM, Jun Koi wrote: > On Tue, Feb 14, 2012 at 11:47 PM, Alex Jia <ajia at redhat.com> wrote: >> Hi Jun, >> I assume you haven't changed libvirt default URI, it may be a issue, >> I want to know whether it works for you if you explicitly specify >> --connect qemu:///system with virt-install? I think a root reason >> probably is your disk

----- Forwarded Message ----- From: "Andrew Holway" <a.holway at syseleven.de> To: "Alex Jia" <ajia at redhat.com> Cc: kvm at vger.kernel.org Sent: Friday, August 17, 2012 4:24:33 PM Subject: Re: [libvirt-users] vm pxe fail Hello, On Aug 17, 2012, at 4:34 AM, Alex Jia wrote: > Hi Andrew, > I can't confirm a root reason based on your information, perhaps

Autobuild has to be updated to call make in the recipe directory and move the resulting iso to the main build directory. Importing the existing autotest.sh script from ovirt-node-image Signed-off-by: Mike Burns <mburns at redhat.com> --- autobuild.sh | 7 + autotest.sh | 764 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 771 insertions(+), 0 deletions(-)

Hi Alex, when I got this error, it was a vnc listener problem. Is there other actives vms on this server? try to change the port number to see if the problem was solved. <graphics type='vnc' listen='0.0.0.0' port='5909'/> Good Luck. Josir Gomes Date: Thu, 15 Mar 2012 18:07:07 +0800 > From: Alex Jia <ajia at redhat.com> > To: ??? <zhanggp at

Added a new subdirectory called "isobuilder" to the project. Created a new Makefile that only allows for creating the livecd version of the oVirt node. Adjusted the build environment to work with the kickstart files that are found in the repo and not ones installed via any previous RPM. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- configure.ac | 1 +

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

hi everyone a good basher around here? I try in a script: _rdiffBack="rdiff-backup -v5 --tempdir /tmp/ --no-eas --exclude-other-filesystems --exclude-symbolic-links" _rdffiExclude="--exclude '**/~*' --exclude '**.tmp' --exclude-regexp '(.glusterfs|.trashcan|temp)'" _execCom=${!2} _sourceDir=${1} _backupTo=${3} __backMeUp() { for _sourceDir in