similar to: Problems: xen with 4 processors!

Keir, This would also be appropriate for 3.1.0, since the /usr/lib fix makes pygrub work on ia64 Presently pygrub only looks in /efi/redhat/elilo.conf. It should check for other distributions, plus a couple fallback locations. Signed-off-by: Aron Griffis <aron@hp.com> diff -r 6d64f9eefad5 -r 67df28389f46 tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub Wed May 02 14:50:56 2007

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Dear list, I would like to add and test EFI boot support for a live system. Since I use isolinux and syslinux for everything, I would be glad to have syslinux.efi as boot loader for EFI-only machines, so I can just keep all syslinux.cfg files, help files and boot screen as they are. I checked out version 6.00-pre git of syslinux (the "firmware" branch) and was able to compile efi32 and

Hi Everyone, I'm trying to get an asus motherboard to netboot. It has an integrated Nvidia boot agent that's supposed to network boot pxe happily. I've setup the necessary services and environments in tftpd, however, the boot agent is running into trouble requesting files from the tftp server. It always seems to receive File Not Found errors. The filenames are specified properly

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

Hi, I installed the xen in server with CentOS 6, but not create vm. [root@localhost oracleteste]# xm create oracleteste.cfg Using config file "./oracleteste.cfg". Started domain oracleteste (id=9) [root@localhost oracleteste]# xm list Name                                        ID   Mem VCPUs      State   Time(s) Domain-0                                     0  1024     1     r-----   

Hello, xl.cfg.pod.5 documentation tweaks/improvements: - videoram: Document that only qemu-xen-traditional device-model currently supports changing the amount of video memory for stdvga graphics device. - videoram: Better document the default amount of videoram for both stdvga and Cirrus. - stdvga: Add a note that stdvga allows bigger amount of videoram and bigger resolutions.

Signed-off-by: Rob Hoes <rob.hoes@citrix.com> --- docs/man/xl.cfg.pod.5 | 18 +++++++------- tools/libxl/libxl_create.c | 57 ++++++++++++++++++++++++++++++++++---------- 2 files changed, 55 insertions(+), 20 deletions(-) diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 769767b..c18604d 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -1009,14

Hi, I am trying to create a boot cd for ia64 systems which will go into the efi shell, map to fs0 (cdrom) and give a help message on screen. I have tried creating a CD using isolinux but this boots as the Red Hat AW2.1 CD 1 and ignores the message file. After selecting the efi shell and mapping to fs0 then entering - elilo linux ks=nfs:<ip address>:<kickstart file> I get the message

Hello, I''m using the following configuration on 8 different servers: xen 4.1.2 from opensuse 12.1 with Kernel 3.1.10-1.9-xen AMD Phenom(tm) II X6 1075T 8GB ram Dom0 : 1GB memory and 2 vcpus on core 0 (via boot option dom0_mem=1024M dom0_max_vcpus=2) DomU : 1 PV guest (opensuse12.1) 1GB memory 2 vcpus on core 1 to 5 1 PV guest (opensuse12.1) 1GB memory 3 vcpus on core 1 to 5

I am getting the following error with memdisk when attempting to boot. I am booting UEFI device using elilo.efi and loading a elilo.conf file with below configuration. Attached is also a print sceen of the error I am getting about memdisk. # force chooser to textmenu chooser=textmenu delay=20 prompt # # the files containing the text (with attributes) to display # message=textmenu-message.msg

Hi, everyone, I installed the Xen3.1.0 based on Fedora8 and enter the Dom0 successfully. The kernel of dom0 is linux-2.6.18-xen0. But the Xorg could not start in the Dom0. When I use the "startx" command to start the X server, the error information is following: ......... (==) Using config file: "etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in

Hi Peter, I'm doing some work for HP creating various flavours of bootable CDs, and am using isolinux for i386 and elilo for ia64. We wanted the same interface on both systems, with the ability to choose a boot option from a menu with the cursor keys. To implement this I enhanced isolinux to support two new control fields in the message file: 0x01 ^A Mark left- or right-hand end of the

Hi, On 02/04/2016 11:10, Thomas Schmitt via Syslinux wrote: > Hi, > > Ady wrote: >> I very much doubt that there is any ISO image, publicly >> available or not, that can boot optical media in UEFI mode by means of >> Syslinux for EFI as of today. I hope this status will change at some >> point. >> [...] >> I doubt that syslinux.efi (renamed as

Tags: patch fixed-upstream Patch below allows this package to be built on ia64. Xen has supported ia64 since ~3.0.1. Thanks, Alex diff -urN a/xen-3.0-3.0.4-1/debian/arch/defines b/xen-3.0-3.0.4-1/debian/arch/defines --- a/xen-3.0-3.0.4-1/debian/arch/defines 2007-07-17 12:40:58.000000000 -0600 +++ b/xen-3.0-3.0.4-1/debian/arch/defines 2007-07-17 12:41:17.000000000 -0600 @@ -5,3 +5,4 @@

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

Hi all, In xen-4.1.2 src/tools/libxl/libxl_dm.c, there is a function called `libxl_build_device_model_args_old`, the func will build qemu-dm cmdline args according to the xl-formated configuration file specified by xl create domid: 2 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Strip off blktap sub-type prefix to /home/malei/c2.delta.img (drv