Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread PJ Welsh
Sure thing. I will need to wait until AM Tuesday USA time to test now. Thanks PJ On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis wrote: > El Lunes 20/03/2017, PJ Welsh escribió: > > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > > Thanks

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread Ricardo J. Barberis
El Lunes 20/03/2017, PJ Welsh escribió: > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it. > On Mon, Mar 20, 2017 at

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread PJ Welsh
Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. Thanks PJ On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes wrote: > On 03/20/2017 01:20 PM, PJ Welsh wrote: > > No warning, but still just reboots with no notice. > > Is there any other system info you

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread Johnny Hughes
On 03/20/2017 01:20 PM, PJ Welsh wrote: > No warning, but still just reboots with no notice. > Is there any other system info you need? > Thanks > PJ > Try the new 4.9.16-24 packages there now. (reworked the config based on a fedora kernel) > On Mon, Mar 20, 2017 at 11:47 AM, Johnny

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread PJ Welsh
No warning, but still just reboots with no notice. Is there any other system info you need? Thanks PJ On Mon, Mar 20, 2017 at 11:47 AM, Johnny Hughes wrote: > On 03/20/2017 11:21 AM, Johnny Hughes wrote: > > On 03/20/2017 08:35 AM, PJ Welsh wrote: > >> Updating my CentOS 6.8

[CentOS-virt] grub-bootxen.sh

2017-03-20 Thread Alvin Starr
This is not abit issue just a minor annoyance. I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo. I would argue that the

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread Johnny Hughes
On 03/20/2017 11:21 AM, Johnny Hughes wrote: > On 03/20/2017 08:35 AM, PJ Welsh wrote: >> Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel >> boot message of a few like "APIC ID MISMATCH" and the system reboots >> immediately without any other bits of info. This is on a

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread Johnny Hughes
On 03/20/2017 08:35 AM, PJ Welsh wrote: > Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel > boot message of a few like "APIC ID MISMATCH" and the system reboots > immediately without any other bits of info. This is on a Dell R710 with > 64GB RAM and 2x 6-core Intel CPU's.

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread Johnny Hughes
On 03/20/2017 08:35 AM, PJ Welsh wrote: > Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel > boot message of a few like "APIC ID MISMATCH" and the system reboots > immediately without any other bits of info. This is on a Dell R710 with > 64GB RAM and 2x 6-core Intel CPU's.

[CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

2017-03-20 Thread PJ Welsh
Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted

Re: [CentOS-virt] unable to execute QEMU command 'migrate': this feature or command is not currently supported

2017-03-20 Thread Valentin Guggiana
Dear Xlord Please check if the VM guest has vm-tools installed else the “virsh migrate --live” parameter requirement is not fulfilled else you has to turn off the VM guest and do the offline “virsh migrate” without “--live” options. Hope that helps. As far as I know (and it definitely worked