similar to: menu.c32: not a COM32R image

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

Hey, I am trying to upgrade my kickstart usb key to 6.0 and I ran into a few issues. I boot with: ? append initrd=initrd.img ks=hd:sdb2:/ks.cfg repo=hd:sdb2:/centos and in the ks.cfg I have: ? harddrive --partition=sdb2 --dir=/centos and on sdb2 I have: ? sdb2:/centos/CentOS-6.0-x86_64-bin-DVD1.iso ? sdb2:/centos/CentOS-6.0-x86_64-bin-DVD2.iso It fails from the beginning unless I add /images

There's a mistake in HowTos/InstallFromUSBkey , so I'd like to ask that someone fix it, or that I be given editing rights. The mistake is that in the section on CentOS 6, step 8, the correct command is "syslinux /dev/sdb1" (only). Also, although this isn't a mistake, I'd like to suggest mentioning in step 1 that the reason why part of the USB key has to be formatted

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 @@

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:

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

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

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

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

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

I have seen this happening because the versions of the menu.c32 module and the installed syslinux do not match.

Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp

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

Hello, after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh): Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r Checked all log-files of my systems running 6.6 with same configuration -- never got such a message (We use NFS/autofs for home-directories, NIS and tcsh (login shell)).

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

This is the second generation of the edit-livecd tool that replaces our original bash script with a python version and aims to reuse as much as the livecd-creator libraries as possible. The main reason for the new creator class is to avoid the need for a kisckstart file in order to edit an existing livecd image. edit-livecd is useful for people who don't have the development and yum

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