similar to: GRUB2 configuration for Xen 4 on Ubuntu Linux 10.04

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

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

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

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

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

Hi all, I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze Xen4.0 and now have problems with starting the Dom0 kernel. I always get the error message: Kernel panic not syncing: the kernel parameter noapic is incompatible with xen. My grub.cfg is: menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386'' --cl$ insmod part_msdos

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

Hi, I am using Xen 4.2.3 installed on an Intel Atom with a Debian Dom0 and 3 Debian domU''s installed. I am trying to run some benchmarks using the Arinc653 scheduler. I have edited my grub options to boot with ''maxcpus=1 sched=arinc653'' options. I can boot the dom0 and verify that the scheduler is enabled. However when I xl create, the VM is created but I cannot

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

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

I have a couple Debian 6 HVM VMs. From what I''ve read, Debian 6''s standard kernels have pv_ops already enabled. I''d like to convert these to pv for the following reasons (Assuming both of are valid expectations): 1) so the VMs use pv for the NICs 2) so the VMs properly respond to shutdown/reboot commands from xm I''m having trouble converting them. I believe

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.

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

hi folks, anyone around who knows how to setup grub2 to allow at boot time a static memory allocation for the Domain-0. I use debain squeeze, lates update''s and my actual grub2 config doesn''t work automaticlly at boot time. i configured the arg "dom0_mem=4096M" in the grub.cfg section multiboot as shown bellow: *** menuentry ''Debian GNU/Linux, with

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

Hi, we´ve got a bad problem here. We installed a new server with debian squeeze sw-raid and lvm. We´ve installed the the actual xen-linux-system-2.6.32-5-xen-amd64? system with grub2 but get an XEN BUG. We´ve tried alot, tested grub-legacy version but cannot get the XEN kernel to boot up. The XEN BUG occurs a  second after grub boots the kernel and there are no outputs at the serial console with

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,