similar to: Centos7 Xen hypervisor console= options broken in default grub2 config

> This is what's defined in /etc/default/grub following the install of the > Xen: > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 > console=com1,tty loglvl=all guest_loglvl=all" > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > nomodeset" > > I didn't set these myself, this is what the

On Wed, May 17, 2017 at 8:44 AM, George Dunlap <dunlapg at umich.edu> wrote: > On Wed, May 17, 2017 at 4:20 PM, Jerry <jerryubi at gmail.com> wrote: > > This is what's defined in /etc/default/grub following the install of the > > Xen: > > > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo > com1=115200,8n1 > > console=com1,tty

On Wed, May 17, 2017 at 2:39 AM, George Dunlap <dunlapg at umich.edu> wrote: > On Wed, May 17, 2017 at 4:26 AM, Jerry <jerryubi at gmail.com> wrote: > > I always disable "rhgb quiet" on a fresh install because I don't like > boot > > messages being hidden from me, and now this other thing does it. I like > > details, I need the details, don't

On Wed, May 17, 2017 at 8:25 AM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > > This is what's defined in /etc/default/grub following the install of the > > Xen: > > > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo > com1=115200,8n1 > > console=com1,tty loglvl=all guest_loglvl=all" > >

On Wed, May 17, 2017 at 4:20 PM, Jerry <jerryubi at gmail.com> wrote: > On Wed, May 17, 2017 at 2:39 AM, George Dunlap <dunlapg at umich.edu> wrote: >> >> On Wed, May 17, 2017 at 4:26 AM, Jerry <jerryubi at gmail.com> wrote: >> > I always disable "rhgb quiet" on a fresh install because I don't like >> > boot >> > messages

On Wed, May 17, 2017 at 8:54 AM, Jerry <jerryubi at gmail.com> wrote: > > > On Wed, May 17, 2017 at 8:44 AM, George Dunlap <dunlapg at umich.edu> wrote: > >> On Wed, May 17, 2017 at 4:20 PM, Jerry <jerryubi at gmail.com> wrote: >> > This is what's defined in /etc/default/grub following the install of the >> > Xen: >> > >>

The new process for auto updates of grub upon kernel install is in the xen4centos testing repo. In order to test these as updates to an existing system, you can do this: 1. download the test repo file: http://dev.centos.org/centos/6/xen-c6-RC1/xen-c6-RC1.repo 2. Put it in /etc/yum.repos.d/ 3. Issue this command: yum --disablerepo=Xen4CentOS upgrade xen\* centos-release-xen (that should

Solved. For the archives: Noticed in xl info output that only 1 core was recognised, even though nr_cpus should show 16 on this box. Tried rebooting and selecting the old .34 kernel, console printed "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" and CentOS failed to boot. Powered down the box fully and started back up with the latest .44 kernel and everything is working fine

Hello ??? For the past months I've been testing upgrading my Xen hosts to CentOS 7 and I face an issue for which I need your help to solve. ??? The testing machines are IBM blades, model H21 and H21XM. Initial tests were performed on the H21 with 16 GB RAM; during the last 6=7 weeks I've been using the H21XM with 64 GB. In all cases the guests were fully updated CentOS 7 --

I just did a yum update on a CentOS 7 / Xen 4.6 server which took me from kernel-3.18.34-20.el7.x86_64 -> kernel-3.18.44-20.el7.x86_64 After rebooting, the following notice is printed immediately upon xl create'ing a domain: libxl: notice: libxl_numa.c:499:libxl__get_numa_candidate: NUMA placement failed, performance might be affected Indeed performance is significantly degraded. This

On 03/28/2017 04:55 PM, PJ Welsh wrote: > The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 > server doing the exact same thing of rebooting immediately after the Xen > kernel load. Just to note this is a second system and not just the first > system with an update. I hope I'm not introducing something odd. They > only "interesting" thing I have

On 03/28/2017 02:55 PM, PJ Welsh wrote: > The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 > server doing the exact same thing of rebooting immediately after the Xen > kernel load. Just to note this is a second system and not just the first > system with an update. I hope I'm not introducing something odd. They only > "interesting" thing I have

I've not gotten any bites from my posting on the xen-devel mailing list. Here is the only one to-date: https://lists.xen.org/archives/html/xen-devel/2017-04/msg01069.html >From that email, there needs to be some hypervisor messages. Does anyone know how to produce the hypervisor messages? I've already removed the rhgb and quiet options from the boot. Thanks PJ On Thu, Apr 6, 2017 at

The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 server doing the exact same thing of rebooting immediately after the Xen kernel load. Just to note this is a second system and not just the first system with an update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following

On Tue, Apr 4, 2017 at 11:13 AM, Johnny Hughes <johnny at centos.org> wrote: > On 03/28/2017 04:55 PM, PJ Welsh wrote: > > The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 > > server doing the exact same thing of rebooting immediately after the Xen > > kernel load. Just to note this is a second system and not just the first > > system with an

Installing xen on a fairly clean c7.2 system. I get a xen kernel panic. (XEN) Bad console= option 'tty' Xen 4.6.0-9.el7 (XEN) Xen version 4.6.0-9.el7 (mockbuild at centos.org) (gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)) debug=n Wed Jan 20 12:25:53 UTC 2016 (XEN) Latest ChangeSet: Thu Jan 14 15:35:35 2016 +0000 git:6e8597a-dirty (XEN) Bootloader: GRUB 2.02~beta2 (XEN) Command line:

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 >

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 I have a similar problem. Hardware configuration: - IBM x3850 server - 6GB DDR2 RAM - IBM ServeRAID 8i configured to RAID0 - 2x DualCore Xeon processors with HyperThreading. The following options available for CPU: - HyperThreading - Processor Adjacent Selector Prefetch - Processor Hardware Prefetcher - Processor Execute

First post to this list. I would appreciate some help on this issue. As background, I installed CentOS 7 on a Dell server, and then ran the following commands: yum update http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-11.el7.x86_64.rpm yum --enablerepo=centos-virt-xen-testing update yum --enablerepo=centos-virt-xen-testing install xen Doing that, I was able to

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