Exalogic Virtual: Guest vServer Not Accessible With "Repaired Filesystem" Shell Prompt Due to FileSystem Corruption Even Though It Is UP & RUNNING From EMOC
Last updated on JULY 29, 2016
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.0 and later
Oracle Virtual Server x86-64
In Exalogic Virtual racks issue of corruption with Guest vServers is noticed after the restart.
Guest vServers are not accessible after restart via EoIB, IPoIB networks. Guest vServer Status is shown as running from EMOC and OVMM console.
When we try to login to Guest vServer via xm console, it directly prompts for the password instead of prompting for the username first.
After we enter the password we get into guest vServer in "Repaired Filesystem" shell prompt with following errors shown on the xm console.
When logged into guest vServer from xm console, we notice that none of the networks are up when running "service network status" command. Once we type "exit" command to exit out of the xm console of the guest vServer we notice that the guest vServer goes to reboot. Guest vServer again comes back up after reboot in same corrupt status.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms