similar to: CentOS 5.4 64bit default Xen install won''t start, garbled boot screen

Hi everyone Ok this is really strange. I''ve been messing around with Xen for the past few weeks on a 32bit test machine and CentOS 5.4 and it''s been working fine. At the weekend I went into the office to install Xen on our server but I had a major problem. The server is a home-build with a Tyan s5211 motherboard with an Intel i3210w chipset CentOS 5.4 64bit installed and

Hi all! I can't for the life of me get xen to run - under both stable and testing the packages give a garbled local console right after dom0 is finished booting, just when one would expect a login prompt. The garbled screen looks a bit like screens full of kernel booting messages scrolling/paging by at breakneck speed. Lines are tearing and overlapping ... difficult to describe. Anyway, it

I have two servers with identical hardware ... TYAN i3210w system boards with dual intel gigabit interfaces, and a PCI intel gigabit nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5 Every other time I reboot, the nics initialize in a different order. anaconda had setup /etc/modprobe.conf with alias lines for the cards: alias eth0 e1000 alias eth1 e1000e alias eth2 e1000e However,

I am currently using a Dell PowerEdge server R610 with Xen 4.0 installed and the 2.6.31.13 pvops kernel. I am accessing the server console using the iDRAC KVM feature of the dell management console. Does anyone know how to configure the console option in the grub menu so that all the boot messages can be seen on the mgmt console? Currently I can view only the Xen bootup messages if I dont specify

Hi all, After rebooting my CentOS 5.5 server, i have the following message: ================================== Red Hat nash version 5.1.19.6 starting EXT3-fs: unable to read superblock mount: error mounting /dev/root on /sysroot as ext3: invalid argument setuproot: moving /root failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a

I am installing Xen on a remote server. I left the other kernels on the grub.conf and made xen the default to boot from. The box didn''t boot into Xen on reboot but I''m not sure why. Here is my Xen config file: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that #

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

Hello, I''m running a standard Debian Etch Xen server for testing. Today I ran a Debian update and it installed some new kernel-related packages. The install scripts said something about deleting unused symlinks, but I was in a hurry, so I can''t remember exactly. Now I''ve the problem that the server will not boot any more. After loading the hypervisor, the system

Hi, I have a couple of dual Xeon 3.0GHZ machines. Both have 4GB of memory. I''m trying to get them to boot Xen stable/2.0.6 (have tried 2.0.5 as well). Because they are remote, getting error messages can be tricky. When ''noreboot'' is set in grubs conf, they stop after the ''scrubbing free RAM'' message. If I remove the noreboot, I''m told a

I am having an issue with Megacli when adding or removing virtual disks. I will post a link to fpaste that has the issue shown. In brief whenever i add, or remove, a virtual disk via MegaCli the attempt succeeds and the adapter is configured but the OS remounts dm-0 in read only. dm-0 is my root lv. This issue does not happen if i boot into the default, non Xen, CentOS kernel. On stock

I've also had a few Xen systems grub entry issues. I'm not yet sure what triggers the events, but I do think there *may* be a correlation to the "/boot" part. I've found the Xen servers that have "/boot" before any of the the lines like "/boot/xen.gz" ended up missing complete grub entries. Not sure it's 100% true. Anyone else comment? Thanks PJ On

Dear ALL, I have encountered an issue while installing xen4.1.2 from source. No problem encountered while xen installation.While booting towards XEN kernel, i encountered the folowing error ******************** setuproot: moving /dev failed : No such file or directory no fstab,sys mounting internal defaults setuproot: error mounting /proc setuproot: error mounting /sys Kernel

Hi Today I updated one machine with CentOS-5.4 (2.6.18-164.6.1.el5) x86_64 (Intel(R) Xeon(R) CPU X5450 @ 3.00GHz) to "2.6.18-164.10.1.el5", but in some places, like /boot[1] and in the menu /boot/grub/menu.lst[2], appeared as 2.6.18-164.1.10 - the "1" and the "10" swapped. Did anybody else had similar problems? The update worked fine in i686 workstation and

Hi all, Recently I build XEN 4.1 (from the xen.org) on centIOS 5.5 (kernel 2.6.38.4). After changing the grub file and rebooting the machine, I am continuously getting out of memory error. The content of my grub file: default=0 timeout=5 serial --unit=0 --speed=115200 terminal --timeout=10 console serial splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.38.4) root

Hi, Anyone have that problem xen installation? [root at xen64-dev ~]# virsh autostart appl error: Failed to mark domain appl as autostarted error: internal error sexpr2string failed root at xen64-dev opt]# rpm -qa |grep libvirt libvirt-client-0.7.0-6.el5 libvirt-python-0.7.0-6.el5 libvirt-0.7.0-6.el5 [root at xen64-dev opt]# rpm -qa |grep xen xen-libs-3.4.2-2.el5

I previously sent this help request to xen-api rather than xen-users. My apologies for the re-send. ------------------- I am following http://www.gentoo.org/doc/en/xen-guide.xml to build a new box for use as dom0. For the dom0 kernel configu I used as a basis a previous, working config from a non-xen kernel. That previous kernel (2.6.32-gentoo-r7) exhibits no console video problem. My new xen

On 12/01/2014 04:48 AM, Bob Ball wrote: > Hi all, > > Following instructions at http://wiki.centos.org/QaWiki/Xen4 to setup Xen on CentOS 6.4. Unfortunately after installing Xen and modifying the boot line there is a kernel panic during the boot process causing the host to enter a reboot loop. Console log attached. > > [<ffffffff81575480>] panic+0xc4/0x1e1 >

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz