Jump to content


Photo

XenServer 7.1 - Console blank/VM unresponsive

Started by David Reade , 14 March 2017 - 10:37 AM
7 replies to this topic

David Reade Members

David Reade
  • 313 posts

Posted 14 March 2017 - 10:37 AM

A few days ago I installed the XenServer 7.1 update. Everything worked including the PHD Virtual Backup 6.5 VM and that night a backup of VMs completed successfully.

 

The following day, the backup appliance had become unresponsive (CPU #0 @ 100%).

 

Rebooting the VM doesn't work and doing a forceful reboot of the VM just causes it to boot into the same unresponsive state. The console is also blank.

 

I have now tried reimporting the appliance from fresh, but upon booting it simply boots into the same unresponsive state. The console is also blank.

 

Assuming the problem lies with the PHD VBA, which is running Ubuntu 12.04.1 LTS, I have decided to trial the newest version of Unitrends Backup which runs CentOS 6.5. However upon booting this VM, the console is blank but the VM is responsive and I can access it via my web browser. But why no console?

 

What would cause the console to stop working and is there anything I can do to check? What about the PHD VBA? I haven't rebooted the host yet as I am afraid to do so in case it doesn't boot.

 

I don't know what to do and would appreciate any feedback.



Alan Lantz Members

Alan Lantz
  • 6,805 posts

Posted 14 March 2017 - 01:36 PM

You definitely want to use UEB over PHDVirtual since thats an old product not designed for XenServer 7.x. I currently have XenServer 7.1 running with the latest UEB. If your BIOS/Firmwares are up to date you might want to check BIOS settings to make sure you don't have any power management features interfering.

 

--Alan--



David Reade Members

David Reade
  • 313 posts

Posted 14 March 2017 - 02:33 PM

What sort of power management features? I'm only licensed for the virtual backup solution. I have just tried to load up UVB 8.0 instead of 9.0 and the exact same thing happens - the first boot the VM is unresponsive and there is no console. CPU #0 is 100% too. The main thing that PHD 6, UVB 8 and UB 9 have in common is they all run in PV mode. All my other VMs are running in HVM mode and they all work fine, no crashing and they reboot no problem. It's just weird how PHD worked immediately after the upgrade but now it doesn't. Surely that would suggest a problem with XenServer as opposed to the VM?

 

I have restarted the Xen Tools Stack but to no avail. Apart from a host reboot, is there anything else I can try?



David Reade Members

David Reade
  • 313 posts

Posted 14 March 2017 - 02:40 PM

Also, are there any logs I can check to see why the console is not available or why the VM is not responding at boot?



David Reade Members

David Reade
  • 313 posts

Posted 15 March 2017 - 09:28 AM

Last night I rebooted the host and this seemed to resolve the problem. I ran the backups and they started no problem. However after a few hours in the early hours, the backup appliance crashed and VM CPU #0 shot up to 100% usage. I have tried rebooting the backup appliance using the forceful option, reloading it from the XVA and even tried a different version, but they all do the same thing and crash as soon as they start.

 

I purposefully left the console running last night and when I got in this morning, the time on the console said "04:02:01", so whatever is happening at 04:02:01 is possibly causing the issue.

 

Doing a "ls -ls" on the /var/log folder, I can see a lot of files that were created at 04:02, so is it possible the process kicking off at this time is also causing XenServer to become unstable?

 

Mar 15 04:02:01 l1ps02xen CROND[29507]: (root) CMD ([ ! -f /etc/cron.hourly/0anacron ] && run-parts /etc/cron.daily)
Mar 15 04:02:01 l1ps02xen run-parts(/etc/cron.daily)[29508]: starting 0yum-daily.cron
Mar 15 04:02:01 l1ps02xen run-parts(/etc/cron.daily)[29515]: finished 0yum-daily.cron
Mar 15 04:02:01 l1ps02xen run-parts(/etc/cron.daily)[29508]: starting license-check
Mar 15 04:02:01 l1ps02xen run-parts(/etc/cron.daily)[29530]: finished license-check
Mar 15 04:02:01 l1ps02xen run-parts(/etc/cron.daily)[29508]: starting logrotate

Mar 15 04:02:02 l1ps02xen run-parts(/etc/cron.daily)[29581]: finished logrotate
Mar 15 04:02:02 l1ps02xen run-parts(/etc/cron.daily)[29508]: starting man-db.cron
Mar 15 04:02:03 l1ps02xen run-parts(/etc/cron.daily)[29592]: finished man-db.cron

 

I have disabled the cron.daily jobs and restarted the service. I will reboot the host again tonight and see what happens.



Alan Lantz Members

Alan Lantz
  • 6,805 posts

Posted 15 March 2017 - 01:38 PM

Did you use XSConsole to schedule metadata daily backups? Maybe that is what is going on. Shouldn't ever cause an issue, but 7.1 is bleeding edge.

 

--Alan--



David Reade Members

David Reade
  • 313 posts

Posted 15 March 2017 - 02:04 PM

XenServer 7.1 is bleeding edge?

 

I had metadata backups configured on the previous XS 7.0 installation but I have not configured them on the 7.1 install yet. In the XSConsole, it says metadata backups are disabled.



Alan Lantz Members

Alan Lantz
  • 6,805 posts

Posted 19 March 2017 - 12:34 AM

XenServer 7.1 has just recently been released and there have yet to be any hotfixes released for it.

 

--Alan--