search for: menuentrys

Does anyone know if it is possible to 'hide' a grub menuentry with CentOS 7 ? I have a custom menuentry that I don't want to be seen on the grub screen - but it needs to be selectable as the entry to boot via 'grub2-reboot' I've scanned the grub2 documentation - but I can't find anything obvious - so I'm guessing it can't be done - unless someone knows

I recently updated the kernel on an Ubuntu 11.04 PVM domU. The dom0 is an up to date Debian Squeeze host (Xen 4.0.1). Attempting to start the domU after this with xm create gives "Error: Boot loader didn''t return any data!". I ran pygrub against the domU manually, I got the following: Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line

> Date: Tuesday, October 15, 2019 14:52:39 +0100 > From: James Pearson <james-p at moving-picture.com> > > Does anyone know if it is possible to 'hide' a grub menuentry with > CentOS 7 ? > > I have a custom menuentry that I don't want to be seen on the grub > screen - but it needs to be selectable as the entry to boot via > 'grub2-reboot' >

I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64 bit version using the tutorial at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/ on a Lenovo thinkcentre workstation. When I boot I get a kernel panic. If I boot the Linux kernel that I compiled using the

Hello, I compiled xen on ubuntu, but at the bot i got the kernel panic message. I enabled the support to ext4 fs. This is kernel panic error: EXT3-fs: unable to read superblock ETX4-fs (md0): unable to read superblock FAT: unable to read boot vector Kernel panic - not syncing: VFS: Unable to read superblock(9,8) My grub.cfg generated by update-grup: menuentry ''Ubuntu, with Linux

I installed CentOS 7 on a Shuttle X27D box (dual-core Atom 330), and so far it seems to work fine, but it didn't set up a Grub2 entry for the existing Windows XP installation in the first partition (MBR). Running os-prober generates no output. fdisk shows that the NTFS partition is still present as /dev/sda1, and still has the bootable flag set. I added a menuentry for Windows to the end of

Hai, I am using dell insprion 580 machine for xen installation and dom0 configuation. I compiled xen source code and configured the kernal. Grub entry given below menuentry ''Xen 4.0.0-rc8 / Ubuntu 10.4 kernel 2.6.32.25 pvops'' { insmod ext2 set root=''(hd0,3)'' multiboot (hd0,3)/boot/xen-4.0.0-rc8.gz module (hd0,3)/boot/vmlinuz-2.6.32.25 dummy=dummy

Hai, I am using dell insprion 580 machine for xen installation and dom0 configuation. I compiled xen source code and configured the kernal. Grub entry given below menuentry ''Xen 4.0.0-rc8 / Ubuntu 10.4 kernel 2.6.32.25 pvops'' { insmod ext2 set root=''(hd0,3)'' multiboot (hd0,3)/boot/xen-4.0.0-rc8.gz module (hd0,3)/boot/vmlinuz-2.6.32.25 dummy=dummy

Following is one grub entry menuentry "Ubuntu, Linux 2.6.32.27" { insmod ntfs set root=''(hd0,2)'' search --no-floppy --fs-uuid --set 96f65c80f65c6313 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) linux /boot/vmlinuz-2.6.32.27 root=/dev/sda2 loop=/ubuntu/disks/root.disk ro quiet splash initrd

Greetings! This is my first contribution, so please let me know if there is anything I should be doing differently. I am following the instructions found here: <https://wiki.centos.org/Contribute>. Your /FirstnameLastname/ username: MitchellRoe The proposed subject of your Wiki contribution(s): Corrected path for getting menu entries The proposed location of your Wiki contribution(s):

I''m running Xen 4.1 (4.1.3-3ubuntu1.3) on an Ubuntu 12.10 server with an AMD FX-8150 processor (8 cores) and 16 GB of RAM. When I boot the server, Xen sees only 3 GB of RAM (instead of 16 GB). If I try to create a domU with more than about 1.5 GB of RAM, the create fails with messages saying it "could not allocate memory for HVM guest". Here''s the output when I do

Hi there, I''ve been trying to find out why my X server is not working with xen and my ati radeon driver, this is what I''ve got uname -a Linux netwarrior 3.2.4-debian #1 SMP Sun Mar 11 22:50:18 ART 2012 x86_64 GNU/Linux xorg.conf Driver "fglrx" grub config menuentry ''Debian GNU/Linux, with Linux 3.2.4 Debian'' --class debian --class gnu-linux

Hi. I''m trying to run Xen 4.0.1 with Debian Squeeze in Dom0 My grub config: menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64'' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set root=''(hd0,msdos1)'' search --no-floppy --fs-uuid --set e719719a-35aa-4ada-8ab5-9b6c676bc89e

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.0-5 Severity: important The hypervisor loads OK but then fails to load my dom0 kernel. I get an erorr message "not an ELF binary" followed after 5s by a hypervisor reboot. /boot/grub/grub.cfg contains: menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux 2.6.22-3-vserver-amd64 (single-user mode)" { set root=(hd0,1)

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

I am trying to specify a static IP on the new dracut format. I was using this: http://man7.org/linux/man-pages/man7/dracut.cmdline.7.html So my grub entry consists menuentry "Install CentOS 8" { linux /boot/vmlinuz noverifyssl ks=https://something ip=192.168.1.3::192.168.1.1:255.255.255.0::eth0:on:192.168.1.1 biosdevname=0 net.ifnames=0 ksdevice=eth0 inst.sshd sshd=1

Hello Xen folks, I use Debian Squeeze. I want to passthrough PCI devices. With the old stable Debian (grub legacy) i did not have problems. I edit /etc/default/grub like: quote: GRUB_CMDLINE_XEN_DEFAULT="quiet xen-pciback.permissive xen-pciback.hide=(00:14.2)(01:05.1)" I run "update-grub". Now i look at /boot/grub/grub.cfg: ### BEGIN /etc/grub.d/20_linux_xen

Am 14.03.23 um 12:30 schrieb Rob Kampen: > OK, > > found out the problem as to why it doesn't boot any kernel except 36.2 > > the system reports that it cannot find > > vmlinuz-3.10.0-1160.88.1.el7.x86_64 > > or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64 > > hence a manual selection from the grub menu when in front of the machine

I am trying to boot a grub entry for CentOS 8 menuentry "Server Install CentOS 8" { linux /boot/vmlinuz noverifyssl ks= https://devgeis.LayeredSolutionsInc.com:443/kickstart/ks_update_to_server8.cfg biosdevname=0 net.ifnames=0 ksdevice=eth0 ip=192.168.1.13 gateway=192.168.1.1 netmask=255.255.255. 0 nameserver=192.168.1.1 inst.sshd sshd=1 initrd /boot/initrd.img

Hi all- I''m using Ubuntu 12.04 and compiled unstable on revision 25605:9950f2dc2ee6, the compilation completed cleanly and I issued sudo make install. I modified the grub entry for Xen 4.1 as follows: menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux 3.2.19'' --class ubuntu --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2