search for: kernelopt

...em it works with ESXI v6.7. > > Hope it's not *offensive *in this thread, as it's syslinux topics. :) > > --- a sample conf of ipxe for your reference --- > # make sure you configure boot.cfg correctly. > # boot.cf > #prefix=http://172.16.234.112/images/esxi67/ > # kernelopt=http://172.16.234.112/images/esxi67/ks.cfg > > ---- > # IPXE > :esxi > # UEFI > kernel http://172.16.234.112/images/esxi67/efi/boot/bootx64.efi -c > http://172.16.234.112/images/esxi67/efi/boot/boot.cfg > # legacy. > #kernel http://172.16.234.112/images/esxi67/mboo...

Il 06/04/20 15:21, Simon Matter via CentOS ha scritto: >> Il 06/04/20 11:54, Georgios ha scritto: >>> Hi there! >>> I had a similar problem recently with grub. No idea why it doesnt work. >>> Try using grubby instead of grub2-mkconfig if you want the system to >>> keep your kernel parameters between boots. >>> >>> Something like:

...es 'blscfg' to store bootloader-independent boot entries in /boot/loader/entries (by default). grub2-mkconfig generates an initial configuration but grubby modifies the individual bootloader spec files in the entries directory. After It's updated the kernel arguments, it overrides the kernelopts in the grub.cfg and hard-codes them per-spec file. In addition to providing a bootloader-agnostic config file, another benefit of blscfg is that the EFI volume is usually a FAT32 filesystem and can't recover easily from filesystem errors. We want to avoid writing to the EFI volume repeatedly...

...lly? The reason I'm asking is I'd like to make a bootable restore > CD that will be fully automated. I don't want the end user to have to do > anything other than insert the CD and boot. Try prompt 1 timeout 30 default install label install kernel mykernel append <kerneloptions> for getting a boot:-Prompt for 3 seconds and then automagically start mykernel, or prompt 0 for getting it without boot:-Prompt. Everything else should be handled by the booted kernel/initrd/root-fs, but that's a different issue. Regards, Josef ____________________________________...

Hello, I know that this card has support in FreeBSD but I'm curious if anyone has used them under heavy load in a RAID-5 configuration. We're thinking of equipping two of these cards with 8 120GB Hitachi drives and run it in an RAID-5 array for video material. The usual data streams will likely be 2-3 streams at about 5-20MB/s (totally) and I know that a single drive will handle that,

Hello, I have a samba server installed on a Lenovo Laptop X100e with this ``smb.conf``: [global] workgroup = WORKGROUP security = user log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d server role = standalone server map to guest = bad user usershare allow guests = yes [homes] comment = Home Directories browseable = no read only =

...to store bootloader-independent boot > entries in /boot/loader/entries (by default). grub2-mkconfig > generates an initial configuration but grubby modifies the individual > bootloader spec files in the entries directory. After It's updated > the kernel arguments, it overrides the kernelopts in the grub.cfg and > hard-codes them per-spec file. > > In addition to providing a bootloader-agnostic config file, another > benefit of blscfg is that the EFI volume is usually a FAT32 filesystem > and can't recover easily from filesystem errors. We want to avoid > writing...

--autosysroot option uses suggestions to user on how to mount filesystems and change root suggested by --suggest option in virt-rescue. Commands are passed on kernel command line in format guestfs_command=command;. Command ends with a semicolon and there can be multiple commands specified. These are executed just before bash starts. On successfull run user is presented directly with bash in

...s (char **cmds); +static void parse_opts(int argc, char * argv[]); + static void __attribute__((noreturn)) usage (int status) { @@ -65,6 +68,8 @@ usage (int status) "Options:\n" " -a|--add image Add image\n" " --append kernelopts Append kernel options\n" + " --autosysroot Automatically use suggested mount commands\n" + " and chroot to guest. Needs --suggest to work\n" " -c|--connect uri Specify libvirt URI for -d opti...

...(int argc, char * argv[]); > + > static void __attribute__((noreturn)) > usage (int status) > { > @@ -65,6 +68,8 @@ usage (int status) > "Options:\n" > " -a|--add image Add image\n" > " --append kernelopts Append kernel options\n" > + " --autosysroot Automatically use suggested mount commands\n" > + " and chroot to guest. Needs --suggest to work\n" Hm I see --suggest and --autosysroot as separate modes: * --sug...

...>> static void __attribute__((noreturn)) >> usage (int status) >> { >> @@ -65,6 +68,8 @@ usage (int status) >> "Options:\n" >> " -a|--add image Add image\n" >> " --append kernelopts Append kernel options\n" >> + " --autosysroot Automatically use suggested mount commands\n" >> + " and chroot to guest. Needs --suggest to work\n" > Hm I see --suggest and --autosysroot as separate mod...

Hi, I tried to rewrite virt-rescue from C to OCaml. Goals were feature parity with C implementation, smaller codebase and hopefully better maintainability. I still don't know if I've covered everything right. So, please check it out. PS: my git send-email seems to be broken, so I'm sending it from thunderbird Thanks! maros

...AGE = 11 +OS_VARIANT_PAGE = 12 +RAM_CPU_PAGE = 13 +ENABLE_STORAGE_PAGE = 14 +LOCAL_STORAGE_PAGE = 15 +MANAGED_STORAGE_PAGE = 16 +BRIDGE_PAGE = 17 +VIRT_DETAILS_PAGE = 18 +CONFIRM_PAGE = 19 + +LOCATION="location" +KICKSTART="kickstart" +KERNELOPTS="kernel.options" +OS_TYPE="os.type" +OS_VARIANT="os.variant" +MEMORY="memory" +CPUS="cpus" + +class DummyMeter(progress.BaseMeter): + def _do_start(self, now = None): + logging.info("Starting...") + + def _do_end(self, amount...

...just looking for some feedback on the direction I'm going. The code won't get all the way to the define stage since I'm in the middle of retrofitting it to use virtinst instead of a home spun node definition.

...$< diff --git a/rescue/rescue.c b/rescue/rescue.c index 419242381..25c3ed88d 100644 --- a/rescue/rescue.c +++ b/rescue/rescue.c @@ -88,6 +88,8 @@ usage (int status) "Options:\n" " -a|--add image Add image\n" " --append kernelopts Append kernel options\n" + " --blocksize[=512|4096]\n" + " Set sector size of the disk for -a option\n" " -c|--connect uri Specify libvirt URI for -d option\n" " -d|--domai...

From: Nikolay Ivanets <stenavin@gmail.com> This patch depends on changes in 'common' sub-module posted here: https://www.redhat.com/archives/libguestfs/2020-February/msg00150.html v3 fixes issue found during code review: - options now appear in alphabetical order v2: Almost the same as v1 except '--blocksize' option description is moved into a common submodule (similar to

...s auto-detected. To override this and force a particular format use the I<--format=..> option. -=item B<-a URI> +=item B<-a> URI -=item B<--add URI> +=item B<--add> URI Add a remote disk. See L<guestfish(1)/ADDING REMOTE STORAGE>. -=item B<--append kernelopts> +=item B<--append> KERNELOPTS Pass additional options to the rescue kernel. @@ -170,9 +170,9 @@ If you have untrusted raw-format guest disk images, you should use this option to specify the disk format. This avoids a possible security problem with malicious guests (CVE-2010-3851)...

This version of the patch includes feedback from jboggs at redhat.com, including fixes to the BuildRequires and Requires in the spec file.

This patch obsoletes any previous ones. This is an upstream candidate, so I'm looking for feedback so we can push this and start using it.

This version fixes a few bugs found by jboggs. It also includes some logging facilities that need to be fleshed out more.