Re: [Openstack] [Nova] Got 'qemu-img: error while writing sector 634880: Input/output error' in _create_image

2012-09-25 Thread Boris Filippov
ve the bug Boris found may occur in NOT shared storage circumstance > as mine, and my issue may be resloved by this patch which adds a lock to > cache image method. > Thanks again. > > 2012-09-25 > -- > Wangpan > -- >

Re: [Openstack] [Nova] Got 'qemu-img: error while writing sector 634880: Input/output error' in _create_image

2012-09-24 Thread Boris Filippov
Your instance directory is shared between compute nodes? Similar issue was fixed for folsom-rc1 https://review.openstack.org/#/c/12024/ https://bugs.launchpad.net/nova/+bug/1014227 2012/9/24 Razique Mahroua > Here is what I found > http://comments.gmane.org/gmane.comp.emulators.qemu/153254 > ht

Re: [Openstack] snapshot-temp-directory

2012-08-13 Thread Boris Filippov
This actually was fixed in upstream ( https://github.com/openstack/nova/commit/70129ed19db187cc90f74abd5c93c86098d29c27 ). Which OpenStack version you use? Maybe this patch can be backported there. There is workaround for this problem, but it's (not a bit) ugly: http://www.mail-archive.com/opensta

Re: [Openstack] Support for snapshot of LVM backend image

2012-07-16 Thread Boris Filippov
>> But qemu can also write the vm state outside of the backend image, which >> should be usable with all image backends. Use that instead managedSave? This should suffice. Save VM state, suspend domain - do snapshot - restore VM with previous state? ___

Re: [Openstack] Support for snapshot of LVM backend image

2012-07-16 Thread Boris Filippov
Well, according to http://libvirt.org/html/libvirt-libvirt.html#virDomainManagedSave domain will be suspended. After snapshotting there is new _create_domain call: if state == power_state.RUNNING: virt_dom.managedSave(0) ... snapshotting... finally:

Re: [Openstack] Support for snapshot of LVM backend image

2012-07-16 Thread Boris Filippov
Current snapshot implementation for libvirt driver doesn't support snapshotting for everything except qcow2 (as i remember, because virDomainManagedSave will fail on everything except qcow2). So, maybe we can discuss it here. This for sure can be implemented for lvm using lvm snapshots but it will

Re: [Openstack] How do I stop image-create from using /tmp?

2012-07-03 Thread Boris Filippov
2012/7/3 John Garbutt : >> From: Daniel P. Berrange [mailto:berra...@redhat.com] >> Sent: 03 July 2012 11:09 >> This would suggest there's a potential use case for a new config parameter >> FLAGS.local_scratch_path, whose default value matches >> FLAGS.instances_path if not set. > > +1 > > Cheers,

Re: [Openstack] How do I stop image-create from using /tmp?

2012-07-02 Thread Boris Filippov
2012/7/2 Daniel P. Berrange : > On Mon, Jul 02, 2012 at 10:24:02AM -0700, Matt Joyce wrote: >> I like the idea of making this a flagfile option. > > In the particular case of the qemu-img command described > in earlier in this thread, I'm not convinced we need a > new option. Instead of using /tmp

Re: [Openstack] How do I stop image-create from using /tmp?

2012-07-02 Thread Boris Filippov
2012/7/1 Lars Kellogg-Stedman : >> So, maybe setting any of this environment variables for nova-compute >> to desired value sholuld help. > > Yeah, I was expecting that. > > Given that this could easily take out a compute host I'd like to see > it get an explicit configuration value (or default to

Re: [Openstack] How do I stop image-create from using /tmp?

2012-06-30 Thread Boris Filippov
As I remember, destination directory for snapshot is created by mkdtemp. What module documantation says about default temp directory: tempfile.tempdir When set to a value other than None, this variable defines the default value for the dir argument to all the functions defined in this module. If t