Re: [ACS4.4, XenServer] Problem starting system VMs

2014-05-01 Thread Jon Ludlam
On 01/05/14 11:35, Dave Scott wrote: > Hi, > > I think I’ve tracked this down. I believe it’s a bug in the XenServer’s event > mechanism, specifically a bug where some shared state causes parallel calls > to event.from to interfere with each other. From CloudStack’s point of view > this manifest

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-05-01 Thread Dave Scott
Hi, I think I’ve tracked this down. I believe it’s a bug in the XenServer’s event mechanism, specifically a bug where some shared state causes parallel calls to event.from to interfere with each other. From CloudStack’s point of view this manifests as * spurious SESSION_INVALID exceptions in w

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-28 Thread Mike Tutkowski
Actually, the only issue I'm noticing now is the SSVM being automatically paused shortly after being created (while creating a new cloud). If I go to XenCenter and forcefully shut the VM down, CloudStack restarts it OK. On Mon, Apr 28, 2014 at 7:34 PM, Mike Tutkowski < mike.tutkow...@solidfire.c

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-28 Thread Mike Tutkowski
Figured I'd CC Anthony and Edison to see if they have any input on this (it looks like most of the changes on the relevant file (Xenserver625StorageProcessor.java) were performed by one or the other). On Mon, Apr 28, 2014 at 12:40 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Thank

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-28 Thread Mike Tutkowski
Thanks for the reply, guys. Just wanted to point out that this is on 4.4 for me (although the issue may also be present on master). I have a sufficient number of IP addresses for both system and user VMs, so that should be OK (but good thought, Punith). I plan to continue debugging this later th

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-28 Thread Dave Scott
Hi, (sorry to reply to my own email!) On 28 Apr 2014, at 11:42, Dave Scott wrote: > > Hi Mike, > > On 28 Apr 2014, at 04:44, Mike Tutkowski wrote: > >> Hi, >> >> I recently installed 6.2 with XS62ESP1 and XS62ESP1004 (so that >> Xenserver625StorageProcessor would be utilized). >> >> When

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-28 Thread Dave Scott
Hi Mike, On 28 Apr 2014, at 04:44, Mike Tutkowski wrote: > Hi, > > I recently installed 6.2 with XS62ESP1 and XS62ESP1004 (so that > Xenserver625StorageProcessor would be utilized). > > When I create a cloud from scratch, my SSVM starts up fine, but CPVM ends > up in the Paused state. I have

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-27 Thread Punith S
hi mike, it seems you may be running out of management ip addresses but i'm not sure of this error ! try these global settings , router.extra.public.nics = 5 router.version.check = false. thanks. On Mon, Apr 28, 2014 at 10:23 AM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > I did

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-27 Thread Mike Tutkowski
I didn't mention this, but I'm using a Basic Zone. The problem is in the VirtualRouterElement, but I'm having a little trouble with my debugger at the moment, so haven't traced it any deeper than VirtualRouterElement.deployVirtualRouterInGuestNetwork. On Sun, Apr 27, 2014 at 10:10 PM, Mike Tutko

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-27 Thread Mike Tutkowski
It is actually a networking problem (although the exception is vague): "Unable to create a deployment for VM[DomainRouter|r-10-VM]" Inside of NetworkOrchestrator.prepareNic, prepareElement fails for the Virtual Router. Is there some network setting I might be missing for this patched version of

[ACS4.4, XenServer] Problem starting system VMs

2014-04-27 Thread Mike Tutkowski
Hi, I recently installed 6.2 with XS62ESP1 and XS62ESP1004 (so that Xenserver625StorageProcessor would be utilized). When I create a cloud from scratch, my SSVM starts up fine, but CPVM ends up in the Paused state. I have to force a shutdown of that VM and then CloudStack restarts it and it works