search for: loader_type

Displaying 20 results from an estimated 49 matches for "loader_type".

2005 Jun 13
2
[PATCH] fix x86_64 initrd support
Looks like x86_64 never quite handled initrd''s. This brings x86_64 in line with i386 in that it doesn''t check LOADER_TYPE (which will be zero anyway). Now initrd is working fine for me on x86_64. Signed-off-by: Chris Wright <chrisw@osdl.org> ===== linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/setup.c 1.6 vs edited ===== --- 1.6/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/setup.c 2005-06-08 01:34:42 -07:00...
2016 Apr 20
1
Re: uefi built from tiancore via edk2 can't persist boot changes
...me_VARS.fd</nvram> > </os> > > This allows the firmware binary to be upgraded centrally, while every VM > can keep its private varstore. > > The virt-install(1) manual describes this, under the example > > --boot > > loader=/.../OVMF_CODE.fd,loader_ro=yes,loader_type=pflash,nvram_template=/.../OVMF_VARS.fd > > The way you specified it implies that the varstore range will be mapped > as read-only pflash directly from the unified OVMF.fd file, which > happens to make the varstore non-writeable. In addition, the real > varstore file will be mapped b...
2007 Aug 09
0
[PATCH] linux/x86: retrieve VESA capabilities in dom0
...===================================================== --- head-2007-08-07.orig/arch/i386/kernel/setup-xen.c 2007-08-07 10:40:43.000000000 +0200 +++ head-2007-08-07/arch/i386/kernel/setup-xen.c 2007-08-09 12:21:12.000000000 +0200 @@ -1669,23 +1669,12 @@ void __init setup_arch(char **cmdline_p) bootloader_type = LOADER_TYPE; if (is_initial_xendomain()) { - /* This is drawn from a dump from vgacon:startup in - * standard Linux. */ - screen_info.orig_video_mode = 3; - screen_info.orig_video_isVGA = 1; - screen_info.orig_video_lines = 25; - screen_info.orig_video_cols = 80; - screen_info.orig_v...
2016 Mar 21
4
uefi built from tiancore via edk2 can't persist boot changes
Apologies if this has been gone over, but I believe I have checked the intertubes more than a bit..... I am using libvirt and have vms booting under an OVMF.fd to use an efi firmware. I can create vms, linux ubuntu, and they will boot up. However, everytime I reboot am I dropped into the default efi shell provide by the tianocore build. Then I must walk the FS to the booting efi app and run, in
2016 Mar 24
0
Re: uefi built from tiancore via edk2 can't persist boot changes
...9; >/var/lib/libvirt/qemu/nvram/guest_name_VARS.fd</nvram> </os> This allows the firmware binary to be upgraded centrally, while every VM can keep its private varstore. The virt-install(1) manual describes this, under the example --boot loader=/.../OVMF_CODE.fd,loader_ro=yes,loader_type=pflash,nvram_template=/.../OVMF_VARS.fd The way you specified it implies that the varstore range will be mapped as read-only pflash directly from the unified OVMF.fd file, which happens to make the varstore non-writeable. In addition, the real varstore file will be mapped below *that*, which is co...
2007 May 09
1
[patch 2/9] lguest: the guest code
...#ifdef CONFIG_ACPI + acpi_disabled = 1; + acpi_ht = 0; +#endif + + add_preferred_console("hvc", 0, NULL); + + if (boot->initrd_size) { + /* We stash this at top of memory. */ + INITRD_START = boot->max_pfn*PAGE_SIZE - boot->initrd_size; + INITRD_SIZE = boot->initrd_size; + LOADER_TYPE = 0xFF; + } + + pm_power_off = lguest_power_off; + start_kernel(); +} diff -puN /dev/null drivers/lguest/lguest_asm.S --- /dev/null +++ a/drivers/lguest/lguest_asm.S @@ -0,0 +1,53 @@ +#include <linux/linkage.h> +#include <linux/lguest.h> +#include <asm/asm-offsets.h> +#include &lt...
2007 May 09
1
[patch 2/9] lguest: the guest code
...#ifdef CONFIG_ACPI + acpi_disabled = 1; + acpi_ht = 0; +#endif + + add_preferred_console("hvc", 0, NULL); + + if (boot->initrd_size) { + /* We stash this at top of memory. */ + INITRD_START = boot->max_pfn*PAGE_SIZE - boot->initrd_size; + INITRD_SIZE = boot->initrd_size; + LOADER_TYPE = 0xFF; + } + + pm_power_off = lguest_power_off; + start_kernel(); +} diff -puN /dev/null drivers/lguest/lguest_asm.S --- /dev/null +++ a/drivers/lguest/lguest_asm.S @@ -0,0 +1,53 @@ +#include <linux/linkage.h> +#include <linux/lguest.h> +#include <asm/asm-offsets.h> +#include &lt...
2007 Apr 18
1
[PATCH 0/8] lguest
As promised to Andrew, and with much thanks to Andi Kleen for feedback, this is the new series of lguest patches. Main change is the move to drivers/lguest (for future non-i386 expansion), but lots of cleanups driven by Andi's feedback and the documentation effort (which made me examine every line of code). It's not perfect, but it's definitely useful. Cheers, Rusty. List of
2007 Apr 18
1
[PATCH 0/8] lguest
As promised to Andrew, and with much thanks to Andi Kleen for feedback, this is the new series of lguest patches. Main change is the move to drivers/lguest (for future non-i386 expansion), but lots of cleanups driven by Andi's feedback and the documentation effort (which made me examine every line of code). It's not perfect, but it's definitely useful. Cheers, Rusty. List of
2016 Nov 28
2
[PATCH] builder: Rearrange how template-building scripts work.
...ch arch)); + add "--vcpus=1" + ); + + add "--os-type=linux"; + add (sprintf "--os-variant=%s" (os_variant_of_os os arch)); + + (match tmpefivars with + | Some (code, vars) -> + add "--boot"; + add (sprintf "loader=%s,loader_ro=yes,loader_type=pflash,nvram=%s" + code vars) + | _ -> () + ); + + add (sprintf "--initrd-inject=%s" ks); + let os_extra = + match os with + | Debian _ | Ubuntu _ -> "auto" + | Fedora _ | RHEL _ | CentOS _ -> + sprintf "ks=file:/%s"...
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which
2007 May 09
1
[patch 3/9] lguest: the host code
...__pa(pg0); @@ -485,13 +488,6 @@ __init void lguest_init(void) add_preferred_console("hvc", 0, NULL); - if (boot->initrd_size) { - /* We stash this at top of memory. */ - INITRD_START = boot->max_pfn*PAGE_SIZE - boot->initrd_size; - INITRD_SIZE = boot->initrd_size; - LOADER_TYPE = 0xFF; - } - pm_power_off = lguest_power_off; start_kernel(); } diff -puN drivers/lguest/lguest_asm.S~lguest-the-host-code drivers/lguest/lguest_asm.S --- a/drivers/lguest/lguest_asm.S~lguest-the-host-code +++ a/drivers/lguest/lguest_asm.S @@ -10,7 +10,8 @@ * This is where we begin: we have...
2007 May 09
1
[patch 3/9] lguest: the host code
...__pa(pg0); @@ -485,13 +488,6 @@ __init void lguest_init(void) add_preferred_console("hvc", 0, NULL); - if (boot->initrd_size) { - /* We stash this at top of memory. */ - INITRD_START = boot->max_pfn*PAGE_SIZE - boot->initrd_size; - INITRD_SIZE = boot->initrd_size; - LOADER_TYPE = 0xFF; - } - pm_power_off = lguest_power_off; start_kernel(); } diff -puN drivers/lguest/lguest_asm.S~lguest-the-host-code drivers/lguest/lguest_asm.S --- a/drivers/lguest/lguest_asm.S~lguest-the-host-code +++ a/drivers/lguest/lguest_asm.S @@ -10,7 +10,8 @@ * This is where we begin: we have...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 03/13] lguest64 core
...ef CONFIG_X86_MCE + mcheck_disable(NULL); +#endif +*/ +#ifdef CONFIG_ACPI + acpi_disabled = 1; + acpi_ht = 0; +#endif + if (boot->initrd_size) { + /* We stash this at top of memory. */ + INITRD_START = boot->max_pfn*PAGE_SIZE - boot->initrd_size; + INITRD_SIZE = boot->initrd_size; + LOADER_TYPE = 0xFF; + } + pm_power_off = lguest_power_off; + + start_kernel(); +} + +asm("lguest_maybe_init:\n" + " cmpq $"__stringify(LGUEST_MAGIC_R13)", %r13\n" + " jne 1f\n" + " cmpq $"__stringify(LGUEST_MAGIC_R14)", %r14\n" + " jn...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 03/13] lguest64 core
...ef CONFIG_X86_MCE + mcheck_disable(NULL); +#endif +*/ +#ifdef CONFIG_ACPI + acpi_disabled = 1; + acpi_ht = 0; +#endif + if (boot->initrd_size) { + /* We stash this at top of memory. */ + INITRD_START = boot->max_pfn*PAGE_SIZE - boot->initrd_size; + INITRD_SIZE = boot->initrd_size; + LOADER_TYPE = 0xFF; + } + pm_power_off = lguest_power_off; + + start_kernel(); +} + +asm("lguest_maybe_init:\n" + " cmpq $"__stringify(LGUEST_MAGIC_R13)", %r13\n" + " jne 1f\n" + " cmpq $"__stringify(LGUEST_MAGIC_R14)", %r14\n" + " jn...
2007 Apr 18
43
[RFC PATCH 00/35] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths