Can you look if the system vm start in PV mode? We come up with a situation
with xs7.1 where the systemvm fail to start because it was in HVM.
On Mar 27, 2017 10:29 AM, "Fabiano A. Souza" wrote:
> Hi Rafael,
>
> I just want to thank you for your help.
>
> I tried to use
Hi Rafael,
I just want to thank you for your help.
I tried to use the hint of fixing state.db but it did not work. The XML
validator return the message that no errors was found on file. I had to
recreate the XenServer's Pool. As I had no-critical instances on this
pool the downtime impact was
The answer is in my previous email, last line:
> You can check if there is something wrong in state.db by passing the
> contents of it in an XML validator. There will probably be some broken XML
> tags there.
>
Last time I faced this problem, I put the host in maintenance, powered off
or migrate
Very thanks Rafael. I was already imagining that this would be the
problem. Do you know any way to fix this problem in XenServer?
By your experience do you believe that recreating the pool in XenServer
will correct this problem?
Again thanks so much for your help.
---
FABIANO A. SOUZA
Looking at the log from your XenServer, and as I said before the problem is
not in ACS.
This kind of log entries:
Db_exn.DBCache_NotFound("missing row", "VBD",
> "OpaqueRef:e1136dfc-cdbc-ba21-3eb8-94838cc75030")
>
or
> D:424e469aca54 failed with exception Db_exn.DBCache_NotFound("missing
>
I am not sure if this is a complete destroy and if ACS re-uses something
from the old VMs.
>From your logs,
> VIF.unplug
> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
>
This probably happened because when the VM was being created and the VIF
was not created in the
This is not an Apache CloudStack (ACS) problem per se.
"HOST_CANNOT_ATTACH_NETWOR"
Something is wrong with your hosts. Are all of the networks of yours hosts
working? is everything in place as ACS expects?
On Wed, Mar 15, 2017 at 10:26 AM, Fabiano A. Souza
wrote:
> After