search for: thaw

...t; nouveau [ DRM] resuming display... >> nouveau 0000:02:00.0: no hotplug settings from platform >> nouveau 0000:02:00.0: no hotplug settings from platform >> >> Logs(dmesg) are literally identical. >> >> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >> ALL Kernels - vesa(fb) resume & thaw BROKEN. >> >> > > Excusez-moi, > BROKEN == The display remains OFF. > More precisely stated...

This patch adds freeze_fs()/unfreeze_fs() for ocfs2 so that it supports freeze/thaw. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> --- fs/ocfs2/dlmglue.c | 115 ++++++++++++++++++++++++++++++++++++++++++++++- fs/ocfs2/dlmglue.h | 2 + fs/ocfs2/journal.c | 1 + fs/ocfs2/ocfs2.h | 12 +++++ fs/ocfs2/super.c | 129 ++++++++++++++++++++++++++++++++++++...

...resuming display... >>> nouveau 0000:02:00.0: no hotplug settings from platform >>> nouveau 0000:02:00.0: no hotplug settings from platform >>> >>> Logs(dmesg) are literally identical. >>> >>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>> >>> >> >> Excusez-moi, >> BROKEN == The display remains OFF. &gt...

...u 0000:02:00.0: no hotplug settings from platform >>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>> >>>>> Logs(dmesg) are literally identical. >>>>> >>>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>>> >>>>> >>>> >>>> Excusez-moi,...

Hello list, I've put CentOS 6.3 x86_64 on my desktop, replacing Fedora 17 x86_64. This is the first time I'm using CentOS on a desktop, so far only on the servers. The problem is with thawing from hibernation. Time from turning on the hibernated machine to reaching the login prompt is not that of an issue, although sometimes it can take a while (significantly more than with Fedora). The problem is after I log in. It appears that none of the running programs will have thawed until...

...0000:02:00.0: no hotplug settings from platform >>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>> >>>>> Logs(dmesg) are literally identical. >>>>> >>>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>>> >>>>> >>>> Excusez-moi, >>>&g...

...is up to you to > manually pause all the guests before taking the snapshot in each of > them. Taking an external disk snapshot works while a guest is paused. > I need take live snapshot for multiple VMs at the same time > > > > > Is there only way that I turn to freeze/thaw functions? > > Guest freeze/thaw (virDomainFSFreeze) only works on a live guest. So > what you will have to do is: > > virDomainFSFreeze(vm1, ...) > virDomainFSFreeze(vm2, ...) > virDomainSuspend(vm1) > virDomainSuspend(vm2) > virDomainSnapshotCreateXML(vm1, ...) > vi...

...ync upon resume. We handle the S4 case with exactly the same scenario, so just point the suspend/resume routines to the freeze/restore ones. Once that is done, we also use the PM API's macro to initialise the sleep functions. A couple of cleanups are included: there's no need for special thaw processing in the balloon driver, so that's addressed in patches 1 and 2. Testing: both S3 and S4 support have been tested using these patches using a similar method used earlier during S4 patch development: a guest is started with virtio-blk as the only disk, a virtio network card, a virtio-s...

...ync upon resume. We handle the S4 case with exactly the same scenario, so just point the suspend/resume routines to the freeze/restore ones. Once that is done, we also use the PM API's macro to initialise the sleep functions. A couple of cleanups are included: there's no need for special thaw processing in the balloon driver, so that's addressed in patches 1 and 2. Testing: both S3 and S4 support have been tested using these patches using a similar method used earlier during S4 patch development: a guest is started with virtio-blk as the only disk, a virtio network card, a virtio-s...

yes, I got your point, thanks very much Eric. If I want to take a distributed snapshot, which need pause all the VMs and then take snapshot, how can I control the pause for all the VMs? Is there only way that I turn to freeze/thaw functions? and freeze/thaw only for file systems, not for the whole guest, am I right? Thanks a lot! Best, Yuanzhen On Wed, Aug 6, 2014 at 11:35 AM, Eric Blake <eblake@redhat.com> wrote: > On 08/06/2014 08:36 AM, Yuanzhen Gu wrote: > > [please don't top-post on technical...

Hi Peter, Should I assume that the virsh domfsfreeze, does not require the qemu-agent service in the guest? PS. I couldn't find the result. Afaik it looks like it is returning the amount of frozen/thawed filesystem's -----Original Message----- Cc: libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices On Fri, Feb 14, 2020 at 22:14:55 +0100, Marc Roos wrote: > > I wondered if anyone here can confirm that > > virsh qemu-agent-command domain '{&quo...

...eze priority 2 2014/08/27 03:00:14.587089 [ 4411]: Freeze priority 3 2014/08/27 03:00:14.589524 [ 4411]: server/ctdb_recover.c:988 startrecovery eventscript has been invoked 2014/08/27 03:00:14.845167 [ 4411]: server/ctdb_recover.c:612 Recovery mode set to NORMAL 2014/08/27 03:00:14.845236 [ 4411]: Thawing priority 1 2014/08/27 03:00:14.845254 [ 4411]: Release freeze handler for prio 1 2014/08/27 03:00:14.845295 [ 4411]: Thawing priority 2 2014/08/27 03:00:14.845311 [ 4411]: Release freeze handler for prio 2 2014/08/27 03:00:14.845342 [ 4411]: Thawing priority 3 2014/08/27 03:00:14.845357 [ 4411]:...

Use PM_FREEZE, PM_THAW and PM_RESTORE power events for suspend/resume/checkpoint functionality, instead of PM_SUSPEND and PM_RESUME. Use of these pm events fixes the Xen Guest hangup when taking checkpoints. When a suspend event is cancelled (while taking checkpoints once/continuously), we use PM_THAW instead of PM_RESUM...

...; 6) umount and remove the snapshot >> >> >> I think that this could be fine (if not please correct me) > > > That doesn't look right.? It should look more like 1) stop or freeze all > of the services (httpd and database), 2) make the snapshot, 3) start or > thaw all of the services, 4) mount the snapshot, 5) back up the data, 6) > remove the snapshot. > About database setup I perform backups via pg_dump so how the snapshot affects pgsql database? What your suggestion I must perform database backup copying only filesystem file and not pgsql.sql d...

...o: > On 9/17/18 11:38 PM, Alessandro Baggi wrote: >> Il 17/09/2018 22:12, Gordon Messmer ha scritto: >>> That doesn't look right.? It should look more like 1) stop or freeze >>> all of the services (httpd and database), 2) make the snapshot, 3) >>> start or thaw all of the services, 4) mount the snapshot, 5) back up >>> the data, 6) remove the snapshot. >> >> About database setup I perform backups via pg_dump so how the snapshot >> affects pgsql database? What your suggestion I must perform database >> backup copying onl...

https://bugs.freedesktop.org/show_bug.cgi?id=94324 Bug ID: 94324 Summary: Nouveau driver breaks thaw (resume form hibernation) Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.or...

changes from v1 1): fs locking prototol version up 0.1 instead of change in dlm protocol version. 2): fixes the racing with umount. yet relies on cancelable cluster lock. 3): timeout the joinning in a cluster when it's frozen instead of waiting until thaw. yet relies on cancelable cluster lock. 4): fix deadlock(with super lock) when joining in a frozen cluster. Move freeze lock out of super lock. 5): takes care of a node crash when cluster is frozen(recvery related). Flush journal in ocfs2_sync_fs() when cluster is in progress of frozen. so...

...ble replicating this because it is not working out for me, so I'm unsure I can provide an solid working example (apologies). I would like to subset my matrix where the values are greater than zero. I can do this easily using the following command to generate a matrix of TRUE/FALSE conditions. thaw.index <- subset(cdem.mat.yr > 0) However, every time I then try to run apply, or rowSums to sum the matrix rows using this index, I get back errors messages or the wrong answer. There is a lot of values that meet this condition, so I know this issue is with my formatting of the argument. i....

...>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>> >>>> Logs(dmesg) are literally identical. >>>> >>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>> >>>> >>> >>> Excusez-moi, >>> BROKEN ==...

hi... i intend to develop a backup application for linux platform... the workflow is as follows: - freeze the file-system(ext2 or ext3) - take the bckup - release the file system. i am not able to find the relevant ioctl or api for freezing & releasing the file system... so... i need some help... thanks... Satish Singhal __________________________________________________ Do You Yahoo!?