search for: bootloading

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: Friday, January 15, 2016 8:41 PM > To: Tal Lubko; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 01/14/2016 02:50 PM, H. Peter Anvin via Syslinux wrote: > > On

On Monday, 15 August 2016 16:26:51 CEST Richard W.M. Jones wrote: > On Mon, Aug 15, 2016 at 04:48:29PM +0200, Pino Toscano wrote: > > Create an object hierarchy to represent different bootloaders for Linux > > guests, moving the separate handling of grub1 and grub2 in different > > classes: this isolates the code for each type of bootloader together, > > instead of

...iles anyway. grub can''t boot domU''s natively (typically), and pygrub obviously can''t do vice versa. The config syntax has a lot of things that aren''t relevant to the domU case. At least, the pygrub approach needs to be optional rather than the primary bootloading method. This proposal covers three parts: the configuration file changes, the bootloader interface, and the new ''root'' bootloader. Config file ----------- Taking a lead from the disk configuration, the ''kernel'' and ''ramdisk'' options are exten...

This enables the usage of a bootloader, i.e., pygrub, when starting a domain using xm in Xen-API mode. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1337273492 -3600 # Node ID cdb947baea102aa6a1d53472f8a3e5f2d6cc485e # Parent ac45608496cd85b0bf1aed6e5b869b4a86ca672f libxl: do not overwrite user supplied config when running bootloader. Currently when running the bootloader libxl will update b_info->u.pv.kernel, .ramdisk, .cmdline and .bootloader. This can

On Tue, Jul 18, 2017 at 03:46:38PM +0200, Pino Toscano wrote: > On Tuesday, 18 July 2017 12:01:12 CEST Richard W.M. Jones wrote: > > In SUSE guests, handle the case where > > Bootloader::Tools::GetDefaultSection () returns undef. > > > > Previously this would return an empty string and cause a bogus error > > in subsequent code: > > > > virt-v2v:

On Tuesday, 18 July 2017 15:57:47 CEST Richard W.M. Jones wrote: > On Tue, Jul 18, 2017 at 03:46:38PM +0200, Pino Toscano wrote: > > On Tuesday, 18 July 2017 12:01:12 CEST Richard W.M. Jones wrote: > > > In SUSE guests, handle the case where > > > Bootloader::Tools::GetDefaultSection () returns undef. > > > > > > Previously this would return an empty

Hi all ! Thanks for the very good support of Dell R320 hardware, perc H310 is well supported, BCM5720 seems to work correctly and performances are great. The only problem i have found is very strange. The FreeBSD bootloader take many times to load, 30sec-2minutes to boot the kernel and show the bootloader menu. After that, the system boots properly, at a normal speed. Is there any issue or

Create an object hierarchy to represent different bootloaders for Linux guests, moving the separate handling of grub1 and grub2 in different classes: this isolates the code for each type of bootloader together, instead of scattering it all around. This is mostly code refactoring, with no actual behaviour change. --- po/POTFILES-ml | 1 + v2v/Makefile.am | 2 + v2v/bootloaders.ml

Not all UEFI guests can survive conversion, because of lost bootloader information in UEFI NVRAM. But some guest can cope with this because they have a fallback bootloader and use UEFI Removable Media Boot Behavior. (see https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_A_Feb14.pdf 3.5.1.1 Removable Media Boot Behavior) to load. If UEFI firmware can't find a bootloader in its

Package: xen-utils-4.4 Version: 4.4.1-9+deb8u8 Severity: normal Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a DomU configuration in "/etc/xen/cfg/" -- bootloader = '/usr/lib/xen-default/bin/pygrub' After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the DomU silently fails to start. Examination of the log files shows that the

Create an object hierarchy to represent different bootloaders for Linux guests, moving the separate handling of grub1 and grub2 in different classes. This will allow us to support more bootloaders in the future. This is mostly code refactoring, with no actual behaviour change. --- po/POTFILES-ml | 1 + v2v/Makefile.am | 2 + v2v/bootloaders.ml | 317

On 01/13/16 00:13, Tal Lubko via Syslinux wrote: > > OK. I'll try that. > Any thoughts regarding the requirement to store the bootloader inside the BIOS chip? > That is fundamentally up to your BIOS. The best is to expose the bootloader in the BIOS as a (readonly) disk drive using standard BIOS or EFI interfaces. -hpa

On Tuesday, 18 July 2017 12:01:12 CEST Richard W.M. Jones wrote: > In SUSE guests, handle the case where > Bootloader::Tools::GetDefaultSection () returns undef. > > Previously this would return an empty string and cause a bogus error > in subsequent code: > > virt-v2v: error: libguestfs error: statns: statns_stub: path must start > with a / character > --- I'm

In SUSE guests, handle the case where Bootloader::Tools::GetDefaultSection () returns undef. Previously this would return an empty string and cause a bogus error in subsequent code: virt-v2v: error: libguestfs error: statns: statns_stub: path must start with a / character --- v2v/linux_bootloaders.ml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git

I recently used a purchased centos 5.2 dvd to install. It all went smoothly, and I am up and running automagically it seems to have upgraded itself to 5.3 Final One peculiarity: I believe I was given the choice of: --installing the bootloader into mbr or --no bootloader install I did not want my mbr overwritten, so I chose no bootloader Why is there no choice of 1st sector of root partition?

How do I resolve this issue? Please help me. ################################################ [root@xenhost2 ~]# xe vm-list uuid=0a0efde9-a92f-3619-478c-64edd8b0adf8 uuid ( RO) : 0a0efde9-a92f-3619-478c-64edd8b0adf8 name-label ( RW): rhel52 power-state ( RO): halted ################################################ [root@xenhost2 ~]# xe vm-start

I'm trying to understand what the extlinux bootloader code written into a partition needs to successfully start. I have a disk with four partitions, the second is marked active and contains a kernel, initrd and root FS and extlinux has been run on it. If I use mbr.bin as the initial bootloader the system boots fine. I need this to work within an environment supplied by a third party. They

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: Tuesday, January 19, 2016 9:17 PM > To: Tal Lubko; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 01/19/16 00:07, Tal Lubko via Syslinux wrote: > > > > To

On Mon, Aug 15, 2016 at 04:48:29PM +0200, Pino Toscano wrote: > Create an object hierarchy to represent different bootloaders for Linux > guests, moving the separate handling of grub1 and grub2 in different > classes: this isolates the code for each type of bootloader together, > instead of scattering it all around. > > This is mostly code refactoring, with no actual behaviour