search for: isofiles

Before any tests are run, the ISO is checked and if it doesn't exist then the script exits with an explicit failure. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/autotest.sh b/autotest.sh index c67931a..904b961 100755 --- a/autotest.sh +++ b/autotest.sh @@ -723,6 +723,10 @@ done

Hello, I have a simple shell script that I use to generate an iso installer depending on the release version that I want. The thing is that I extract isolinux and menu.c32 from the syslinux rpm of the latest redhat release. The reason I am doing it this way is because of the This is what does it: copymenu32() { # $ cat /local/kickstart/templates/os-updates.txt # RedHat-5.8|20120425

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(-)

If the -p option is provided, then no VMs are destroyed. Instead they, and their related networks, are left intact. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/autotest.sh b/autotest.sh index c9f8a2d..b72ec98 100755 --- a/autotest.sh +++ b/autotest.sh @@ -219,6 +219,9 @@

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once

By default it's 120 ms, but can be changed through command line arguments. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 16 ++++++++++------ 1 files changed, 10 insertions(+), 6 deletions(-) diff --git a/autotest.sh b/autotest.sh index c67931a..bcd9bd5 100755 --- a/autotest.sh +++ b/autotest.sh @@ -62,6 +62,7 @@ Usage: $ME [-n test_name] [LOGFILE] -i:

Well you can all read the thread here for the technical details: http://lists.gnu.org/archive/html/qemu-devel/2010-08/threads.html#00133 but the bottom line for anyone who wasn't in that discussion or on IRC last week is that we have to change the way that the appliance is built in libguestfs so that we don't depend (as much) on the qemu -initrd option. The bad thing is this is loads of

...9;'hvm'' device_model = ''/usr/lib/xen-4.0/bin/qemu-dm'' memory = ''512'' shadow_memory = ''8'' # drives #root = ''/dev/sda1'' disk = [ ''phy:/dev/sdb,ioemu:xvda,w'', ''file:/home/isofiles/ubuntu-11.04-server-i386.iso,ioemu:hdc:cdrom,r'' ] # hostname name = ''phyfog'' # networking dhcp = ''dhcp'' vif = [''mac=00:16:3e:11:22:33,type=ioemu, bridge=xenbr0''] # behaviour boot=''d'' on_poweroff = ''destr...

Now that it appears that some folks are able to get the 5.4 downloads (and a GREAT BIG THANK YOU to all the centos team members who make this possible!) I'm wondering when the updates will begin flowing so that those of us running 5.3 can do "yum upgrade" and enjoy all the benefits too? Thanks in advance! -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us

Dear, "Xenoppix-x86-64(Xen3.0.2+KNOPPIX-x86_64-5.0.1) CD size" is released. http://unit.aist.go.jp/itri/knoppix/xen/index-en.html Xenoppix-x86-64 exploits latest CPU (Intel Core2 Duo and AMD Athlon64). * Xenoppix-x86-64 boots both X86 and X86_64 linux kernel on HVM of Xen. * Xenoppix-x86-64 looks like KNOPPIX but all packages are replaced for X86_64. * Xenoppix-x86-64 also

I noticed that the --attach option was not covered in the synopsis. This commit documents all of the missing command line parameters in the synopsis. --- customize/virt-customize.pod | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/customize/virt-customize.pod b/customize/virt-customize.pod index 3fe9050..8fb9931 100644 --- a/customize/virt-customize.pod +++

Allow the user to specify a template in --list mode, which will be the only result in the resulting output (instead of all the available templates). This makes it easier to find out the details of a specific template. --- builder/builder.ml | 6 ++++++ builder/cmdline.ml | 3 ++- builder/virt-builder.pod | 13 +++++++------ 3 files changed, 15 insertions(+), 7 deletions(-) diff

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Simple code motion, no behaviour changes. --- builder/builder.ml | 46 ++++++++++++++++++++++++++-------------------- 1 file changed, 26 insertions(+), 20 deletions(-) diff --git a/builder/builder.ml b/builder/builder.ml index 9c26573..ec9919f 100644 --- a/builder/builder.ml +++ b/builder/builder.ml @@ -75,6 +75,30 @@ let remove_duplicates index = false ) index +(* Look for the

Add the possibility to choose which architecture use to build the wanted image (--arch). Since this implies that running commands on the guest is usually not possible when the architecture is different than the host one, another new option (--allow-foreign-arch-ops) allows to run commands nevertheless. The caching scheme is adapted to account for the architecture (with --print-cache showing the

On Tuesday 11 March 2014 10:09:45 Richard W.M. Jones wrote: > On Mon, Mar 10, 2014 at 02:28:20PM +0100, Pino Toscano wrote: > > Add the possibility to choose which architecture use to build the > > wanted image (--arch). Since this implies that running commands on > > the guest is usually not possible when the architecture is > > different than the host one, another new

Setting timezone is easy. It turns out to be almost impossible to set keyboard layout in virt-builder sanely, so I have added some examples instead. Coming up next, setting languages in virt-builder (clue: very very very hard). Rich.

There's not going to be an easy way to present this patch. It's huge and interconnected. Anyway, what it does is lay the groundwork for a new tool which I'm calling 'virt-customize'. virt-customize is virt-builder, but without the part where it downloads a template from a respository. Just the part where it customizes the template, that is, installing packages, editing

Previously we had lots of types like String, Device, StringList, DeviceList, etc. where Device was just a String with magical properties (but only inside the daemon), and DeviceList was just a list of Device strings. Replace these with some simple top-level types: String StringList and move the magic into a subtype. The change is mechanical, for example: old

Very large but mechanical change to the generator. Rich.