similar to: set Domain-0 default memory allocation

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

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

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 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, 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

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 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

Hi all. I''ve got a situation with Fedora 18 on a dual Xeon E5506 box, 16GB RAM, Tyan S7002 motherboard with the latest BIOS. Because of all the issues, I''m starting to think maybe there''s something wrong with the box itself, maybe something strange going on with the BIOS or mobo resources. Although this box was in service without incident for about 2 years prior. I

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 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

There is some interest lately in making a self-contained grub2 boot image - call it pvgrub2, used for booting paravirtual domU in xen where a grub2 config is installed. First attempt------------------ I first tried using the grub2*.src.rpm from the C7 vault. I configured as shown belowhttps://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/ for headers, I used

I've been trying to use memdisk with grub2 to boot some iso images -( I've done this without any problem with pxe ) There is a memdisk.mod in /boot/grub/ and I've seen some material talking about this, but no example of a menu. After trying countless permutations - Right now I have : menuentry "Memtest-Plus 4.2" { echo `hello` insmod lvm

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Hardware specs: Dell PowerEdge R410 32GB RAM DDR3 1TB RAID-1 HD (Perc H200 RAID controller) Processor: 2 - Intel XeonE5620 2.4Ghz 12M Cache Turbo HT 1066MHz SO: Debian Squeeze last update: 14/10/2010 uname -a: "Linux spo-r1-u4 2.6.32-5-xen-amd64 #1 SMP Fri Sep 17 22:00:48 UTC 2010 x86_64 GNU/Linux" At boot, xen-hypervisor is loaded

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.

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

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

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

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Either Xen, or the Dom0 kernel (I guess you know better) spits out error messages about ata4 containing "status: { DRDY ERR }" (similar error can be found googling DRDY ERR). I'm not putting the whole error message here because I couldn't copy-paste the message at the booting stage. I'm adding the autoconfigured menu