Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Michael Still
I don't know why this is happening, but it sure seems like something you should file a bug for. https://bugs.launchpad.net/nova/+filebug Thanks, Michael On Saturday, September 13, 2014, Stephen Cousins wrote: > Just confirmed that it isn't happening with 4-core VM's either. Just 8. I > haven'

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Stephen Cousins
Just confirmed that it isn't happening with 4-core VM's either. Just 8. I haven't tried a 16-core VM but I can guess. The flavors are matched with 1 GB per core so an 8-core VM has 8 GB of RAM. Does that lead to any ideas? On Fri, Sep 12, 2014 at 3:10 PM, Stephen Cousins wrote: > Thanks for the

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Stephen Cousins
Thanks for the information. I just tried doing it with a VM with only 2 cores and it has been working fine. So it seems that it may be specific to the number of cores that are involved. I'll try with 4 to see if that works ok. Thankfully we don't have many 8-core machines but we still have the nee

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Jonathan Proulx
On Fri, Sep 12, 2014 at 1:44 PM, Stephen Cousins wrote: > Does anyone live-migrate VM's successfully when volumes are attached? My setup is significantly different so probably not terribly helpful, but to answer the question I did do live migrations with Volumes attached on my Grizzly cloud (sin

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Stephen Cousins
​Hi Abel, Yes, it is the instance load. The console.log seems to get truncated to 0 bytes whenever I do live-migration. All machines (including the nfs server) are using ntp. I just checked visually and all of their times match, at least to the second. Probably it is closer. I can't find much in

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Abel Lopez
That’s pretty interesting. I haven’t seen that before, tbh, I had been using gridcentric for live migrations in grizzly, but that’s just because we didn’t have shared storage. So, the instance is what is generating the load, right? anything interesting on the console log? I wonder if there is so

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Stephen Cousins
Hi Abel, I just tried and it did the same thing. Load went up to 800 and the VM is unreachable. Any ideas? Thanks, Steve On Fri, Sep 12, 2014 at 12:59 PM, Abel Lopez wrote: > Does it work if you first detach the volume and then migrate? > > > On Friday, September 12, 2014, Stephen Cousins >

Re: [Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Abel Lopez
Does it work if you first detach the volume and then migrate? On Friday, September 12, 2014, Stephen Cousins wrote: > I am fairly new to Openstack having just inherited a Grizzly system with > NFS storage. "nova live-migration" is working unless the VM has an attached > volume. When it doesn't w

[Openstack-operators] Grizzly: live-migration with attached volume?

2014-09-12 Thread Stephen Cousins
I am fairly new to Openstack having just inherited a Grizzly system with NFS storage. "nova live-migration" is working unless the VM has an attached volume. When it doesn't work, the VM does move but it is not possible to connect to it and the CPU load on that VM goes up to the number of cores assi