Re: CloudStack Logging

Paul, Your classification of levels seems right. I wouldn't say WARN means it isn't good but just that it might be given an objective the user might have. There is also FATAL, ERROR would be recoverable while FATAL means the system can no longer be trusted to do it's job right. The INFO examples

RE: CloudStack Logging

Hi, I don't think that it's a question of importance. INFO vs DEBUG should be telling you different things. ERROR and WARN are also quite different. In general I'm targeting the cloud operational admins, the people who need to know the health of their cloud and deal with issues as they're

Re: Unable to start a HVM VM with more than 2 volumes attached using XenServer 6.5 and ACS 4.7.1

After more investigation, I can confirm that the problem is only for HVM. I tried with a PV vm and everything is fine. For some reason, performing the call: VM.get_allowed_VBD_devices on a HVM while the VM is still in starting state only returns a subset of device Ids: [1, 2] instead of

RE: Bug in Snapshot Retention?

Hi all, Any insight in why some snapshots could be stuck in "allocated" state? Thanks Sean -Original Message- From: Sean Lair Sent: Wednesday, April 20, 2016 9:31 AM To: users@cloudstack.apache.org Subject: RE: Bug in Snapshot Retention? Thanks for the responses all. The "Removed

RE: Bug in Snapshot Retention?

Thanks for the responses all. The "Removed Field" for the snapshots with the status of "BackedUp" is NULL. I combed the logs and found the exception below. It was successfully deleting snapshots before that log entry, then errored on the "Allocated" snapshot and stopped any further

Re: CloudStack European User Group, Berlin, June 2016

Hi Steve Nice! I plan to be there. Regards René On 04/18/2016 05:05 PM, Steve Roles wrote: > Hi all, > > > We're very excited to announce the summer 2016 meeting of the CloudStack > European User group, this time kindly hosted by BIT.Group GmbH, at the Grand > Hotel, Berlin. As well as

Unable to start a HVM VM with more than 2 volumes attached using XenServer 6.5 and ACS 4.7.1

Hi, We are getting a weird error when trying to start a VM (based on a HVM template) when attaching more than 2 volumes. We are using XenServer 6.5 and CloudStack 4.7.1. Here are the logs: ACS Unable to start i-152-612-VM due to The device name is invalid at

RE: problem with vm volume resize

The root disk resize isn't supported with vmware, but the disk I'm attempting to resize isn't a root disk. Based on what I've seen in the logs, the GUI, and in the vcenter properties for this instance, it appears the disk I'm attempting this on is identified correctly. Disk 0:0 is the root,

RE: CloudStack Logging

Hello, I have a question what is the criteria that you are going to follow to decide the log record importance. Who is the user that you will design the logging process for. Is it for finding issues with the installation or is it for security breaches or auditing. These questions are good to

RE: CloudStack Logging

Hi Simon, My gut says that it's probably not worth going back before 4.3. There have been large changes since then but I think that it's better to get as much data as possible, limiting to 4.6+ might not give a particularly large install base. Kind regards, Paul Angus Regards, Paul Angus

Re: problem with vm volume resize

Chris - out of interest - has this VM been through a storage vMotion? We have come across an issue recently where a similar thing happened, the wrong disk was resized and our investigation so far shows this to potentially be caused by disks having been renamed during svMotion. Dag Sonstebo

RE: problem with vm volume resize

I think Root disk resize is supported only on KVM as per the FS https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support -Original Message- From: ilya [mailto:ilya.mailing.li...@gmail.com] Sent: Wednesday, April 20, 2016 11:23 AM To: users@cloudstack.apache.org