similar to: new install of Xen 4.6 hangs on Loading initial ramdisk

?Not sure if this actually made it to the list the first time.? Here is the SERIAL output (bottom of message after your questions).? Googling the error indicates it's something people ran into a few years back but was supposedly fixed.? Any ideas? I can verify that if I REMOVE the second CPU, it boots into Xen kernel no problem.? The CPU itself doesn't matter, as I can swap either

Re: Contents of CentOS-virt digest... Best regards, Bob Vargas On Sat, Nov 28, 2015 at 7:00 AM, <centos-virt-request at centos.org> wrote: > Send CentOS-virt mailing list submissions to > centos-virt at centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-virt > or, via email, send a

As mentioned yesterday, Xen 4.6 packages are now available for testing. These also include an update to libvirt 1.3.0, in line with what's available for CentOS 7. Please test, particularly the upgrade if you can, and report any problems here. To upgrade: yum update --enablerepo=centos-virt-xen-testing To install from scratch: * Install centos-release-xen from centos-extras yum install

Hallo, I am currently installing XEN on an ARM64 EFI machine. (Debian Testing), Therefore, I installed the following packages: __________________________________________________________________ root at armbox:/etc# dpkg -l "xen*" | awk '/^ii/ {print $2 "\t\t" $3}' xen-hypervisor-4.6-arm64 4.6.0-1+nmu2 xenstore-utils 4.6.0-1+nmu2 root at

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

On 01/14/2016 06:57 PM, George Dunlap wrote: > As mentioned yesterday, Xen 4.6 packages are now available for > testing. These also include an update to libvirt 1.3.0, in line with > what's available for CentOS 7. Please test, particularly the upgrade > if you can, and report any problems here. > > To upgrade: > > yum update --enablerepo=centos-virt-xen-testing >

I have released to the master mirror the following packages for Xen4CentOS: b518e3b0fd4f735b34d7784815793cb787283d9029776bd9794cedeb274b9204 kernel-3.18.21-16.el6.x86_64.rpm 4b17373a0ef6806b26d02eb87fc299020beb60b6e31ed08a9c57d30a1410fbe7 kernel-devel-3.18.21-16.el6.x86_64.rpm cacedf6771849f7525145ad4ed7d36a2cad5b49b546173bb7c132b236cb7ac49 kernel-doc-3.18.21-16.el6.noarch.rpm

I'm trying to debug what I believe to be a kernel bug (https://lists.centos.org/pipermail/centos-devel/2016-March/014463.html) and I'm trying to set up systemtap for that. I'm trying to set up systemtap on kernel 3.18.21-17.el6.x86_64 (Xen 4.4.3-10.el6) and it requires the kernel-debuginfo package, however I cannot find anywhere package kernel-debuginfo-3.18.21-17.el6.x86_64.rpm. In

On 7 March 2016 at 14:42, Johnny Hughes <johnny at centos.org> wrote: > On 03/03/2016 01:22 PM, Thanos Makatos wrote: >> I'm trying to debug what I believe to be a kernel bug >> (https://lists.centos.org/pipermail/centos-devel/2016-March/014463.html) >> and I'm trying to set up systemtap for that. >> >> I'm trying to set up systemtap on kernel

On 11/01/2015 12:07 PM, Karel Hendrych wrote: > Hi, just a heads-up: 3.18.21 didn't boot up on HP ML310e Gen8 v2, SATA drives in AHCI mode, / on software raid 1, no LVM. It ended up in kernel panic > with unable to mount root fs. Attached. No difference in grub kernel/xen settings. > > I didn't investigate the things deeper so far. 4.4.3-3/3.18.17 is booting fine. > >

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

I am trying to add libvirt to a linux machine running a custom built linux- there is no packet manager, everything is compiled using buildroot. On this VM server, I am running libvirt-1.2.2 and the linux kernel is 3.18.21 Libvirtd starts and runs in the background. I can add/edit VMs using Virt-install. If I try to connect to the local qemu, everything works: virsh -c qemu:///system If I ssh in

Now I understand what you mean the the "-samefile" parameter of "find". As requested I have now run the following command on all 3 nodes with the ouput of all 3 nodes below: sudo find /data/myvolume/brick -samefile /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397 -ls node1: 8404683 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43

To quickly resume my current situation: on node2 I have found the following file xattrop/indices file which matches the GFID of the "heal info" command (below is there output of "ls -lai": 2798404 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 As you can see this file has inode number 2798404, so I ran

Hi, Sorry for mailing again but as mentioned in my previous mail, I have added an arbiter node to my replica 2 volume and it seem to have gone fine except for the fact that there is one single file which needs healing and does not get healed as you can see here from the output of a "heal info": Brick node1.domain.tld:/data/myvolume/brick Status: Connected Number of entries: 0 Brick

I did a find on this inode number and I could find the file but only on node1 (nothing on node2 and the new arbiternode). Here is an ls -lai of the file itself on node1: -rw-r--r-- 1 www-data www-data 32 Jun 19 17:42 fileKey As you can see it is a 32 bytes file and as you suggested I ran a "stat" on this very same file through a glusterfs mount (using fuse) but unfortunately nothing

Hi Ravi, Thanks for your hints. Below you will find the answer to your questions. First I tried to start the healing process by running: gluster volume heal myvolume and then as you suggested watch the output of the glustershd.log file but nothing appeared in that log file after running the above command. I checked the files which need to be healing using the "heal <volume> info"

On 07/31/2017 02:00 PM, mabi wrote: > To quickly resume my current situation: > > on node2 I have found the following file xattrop/indices file which > matches the GFID of the "heal info" command (below is there output of > "ls -lai": > > 2798404 ---------- 2 root root 0 Apr 28 22:51 >

I'm trying to install CentOS 5.5 on a couple of servers of type IBM System x3550 M3, but it's not going too well. Actually, the install setup phase runs as expected, and the actual installation also appears to be successful, but the system will not boot - I just get a message (presumably) from BIOS saying that boot from hard disk 0. If I start the installer again after this, or boot

The following have been added to the virt6-xen-44-testing repo: x86_64: kernel-3.18.21-13.el6.x86_64 kernel-devel-3.18.21-13.el6.x86_64 kernel-firmware-3.18.21-13.el6.noarch kernel-headers-3.18.21-13.el6.x86_64 perf-3.18.21-13.el6.x86_64 src: kernel-3.18.21-13.el6.x86_64 Please test these for a week or so and we will move them into production next week. I am also building this kernel into