similar to: Boot problem with Debian Squeeza and Xen

Hi folks, I would like to test Xen3.3 on CentOS 5.5 on an older machine which is not 64bit capable. Since this is just a "first impression" test I do not want to fuzz with compiling the kernels and tools myself (that comes in a later step). Can someone please point me to a repo with 32bit Xen3.3 kernels for CentOS 5? GITCO supplies 64bit kernels only, and googling brought up

Odd question I know. I am looking for source for as recent a kernel as possible running the old style xenlinux/xenified kernel (i.e. capable of running the xen3.3.x hypervisor). Any ideas where I can get this - preferably in git form? I think Stefano Stabellini had something that worked up to 2.6.36 (from memory). And yes, we would all prefer all our customers moved to xen4 but this is difficult

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

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

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

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

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

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

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. 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 would like to run 10 x Windows 2003 server(enterprise edition) guests VM on top of my Xen3.3 box. Each guest vm need 5 terminal service connections. I am not sure how to buy the guest license. I think 2 possible ways, can anyone give some idea to me: 1. buy 10 x Enterprise edition license and buy 5 TS CAL to each window license 2. buy 1 x datacenter edition license

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, 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 am running Xen 4 and want users to be able to install arbitrary HVM images. We want both PV and emulated drivers to appear. The reason for this is for compatibility with images that were prepared for Xen 3.3, which assume emulated devices exist at boot time (particularly for running the boot loader). If I do not specify on the boot line xen_emul_unplug=never, then under some guest OS''s

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 I have trouble with Quard Core Opteron and windows 2008(x86). By the way Windows device manager show 4 processors, BUT task manager show only one core. I found that my problem is not new. But solutions, provided by those people did not helped me. By the way, my windows is enterprise version, and as far as I know, it allows up to 8 processor sockets, so the trouble is not, that windows

Hi, Keir, This patch is a bugfix for saving and restoring MSI/MSI-X across S3. Currently, Dom0''s PCI layer unmaps MSI when S3 and maps them back when resuming. However, this triggers unexpected behaviors. For example, if the drivers still holds that irq at the point of unmapping MSI, Xen will force unbind that pirq. But after resume, we have no mechanism to rebind that pirq. The device