search for: saved_entri

This grub.cfg from a default fedora 19 Beta install caused pygrub failures.The previous pygrub commit fixed taht. So this example file added for reference. Signed-off-by: Marcel Mol <marcel@mesa.nl> --- tools/pygrub/examples/fedora-19.grub2 | 117 +++++++++++++++++++++++++++++++++ 1 files changed, 117 insertions(+), 0 deletions(-) create mode 100644 tools/pygrub/examples/fedora-19.grub2

Confirmed this issue. To reproduce: Install a fresh Wheezy AMD64 guest under Xen 4.1 (hypervirtualized, boot from the debian-7.1.0-amd64-CD-1.iso). Use "entire disk" automatic layout for partitioning, this creates /dev/xvda1 for / and /dev/xvda5 for swap. It will create /boot/grub/grub.cfg with many references to (/dev/xvda,msdos1) which works fine when the machine is booted

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

I''m trying to run Xen on Arch Linux with UEFI boot. I followed the steps for Xen in the Arch Linux Wiki https://wiki.archlinux.org/index.php/Xen I get the following when attempting to boot: Loading Xen 4.2.2 ... WARNING: no console will be available to the OS Loading Linux linux ... Loading initial ramdisk ... Unfortunately there is no console so I cannot determine what has gone wrong,

You get these if you install Debian Wheezy as HVM and then try to convert to PV. This is Debian bug #603391. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Tril <tril@metapipe.net> --- tools/pygrub/examples/debian-wheezy-hvm.grub2 | 104 +++++++++++++++++++++++++ tools/pygrub/src/GrubConf.py | 6 +- 2 files changed, 109 insertions(+), 1

Hello, I have installed the Xen 4.1.1 and a working kernel 2.6.32.43 which supports Xen on a Ubuntu Linux 10.04 LTS. However, I have never successfully booted the Hypervisor and Dom0. The screen is always black after some kernel messages rapidly go by. I think that I may pass the wrong parameters to the kernel or Hypervisor with GRUB2. Can any one share his/her working grub.cfg for GRUB2 with

On Sat, 2013-09-28 at 20:59 -0700, Tril wrote: > Backtrace from manual run of the buggy GrubConf.py: > # python /usr/lib/xen-4.1/lib/python/grub/GrubConf.py grub2 grub.cfg > WARNING:root:Unknown directive load_video > WARNING:root:Unknown directive terminal_output > WARNING:root:Unknown image directive load_video > Traceback (most recent call last): > File

This issue has been around for some months, but other things keep crowding out a fix. uname give me 3.10.0-1160.36.2.el7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021 yet I have 3.10.0-1160.76.1.el7.x86_64 3.10.0-1160.81.1.el7.x86_64 3.10.0-1160.83.1.el7.x86_64 3.10.0-1160.88.1.el7.x86_64 loaded. The system uses UEFI to boot. sudo ls -l /sys/firmware/efi gives: total 0 -r--r--r--.? 1 root

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

Booting a fedora 19 domU failed because a it could not properly parse the grub.cfg file. This was cased by set default="${next_entry}" This statement actually is within an ''if'' statement, so maybe it would be better to skip code within if/fi blocks... But this patch seems to work fine. --- tools/pygrub/src/GrubConf.py | 2 ++ 1 files changed, 2 insertions(+), 0

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 guys, It''s my first time here and in a mailing lists, I only participated in forums before. Please, If I make a mistake you should advise me. Let''s go! I was reading "xencommons not start" in a Remus Forum in order to install Remus. Well… I followed the tutorial < http://remusha.wikidot.com/configuring-and-installing-remus>, I reboot in xen_unstable and I had

hi guys, It''s my first time here and in a mailing lists, I only participated in forums before. Please, If I make a mistake you should advise me. Let''s go! I was reading "xencommons not start" in a Remus Forum in order to install Remus. Well… I followed the tutorial < http://remusha.wikidot.com/configuring-and-installing-remus>, I reboot in xen_unstable and I had

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can