Re: [Qemu-discuss] Issue with fsfreeze with qemu agent.

Thank you very much in favor of the version of the patch Good idea to make the option: 1. Ignore the mount points for custom filters (command line options or config file) 2. Catch errors in case of failure for other cases: EBUSY,EOPNOTSUPP Stanislav -- View this message in context:

Re: [Qemu-discuss] Issue with fsfreeze with qemu agent.

-- View this message in context: http://qemu.11.n7.nabble.com/Issue-with-fsfreeze-with-qemu-agent-tp408459p435946.html Sent from the Discuss mailing list archive at Nabble.com.

Re: [Qemu-discuss] Issue with fsfreeze with qemu agent.

Van: Christian Theune [mailto:c...@flyingcircus.io] Verzonden: maandag 30 mei 2016 15:29 Aan: Dominique Ramaekers CC: qemu-discuss@nongnu.org Onderwerp: Re: [Qemu-discuss] Issue with fsfreeze with qemu agent. On 30 May 2016, at 15:25, Dominique Ramaekers <dominique.ramaek...@cometal

Re: [Qemu-discuss] Issue with fsfreeze with qemu agent.

> On 30 May 2016, at 15:25, Dominique Ramaekers > wrote: > > Ok, that seems to be it. > > I’ve got the ‘/’ and ‘/home’ on the same device formatted as btrfs on two > separate sub volumes. Sounds right. > Is there a workaround to deal with btrfs? I had a

Re: [Qemu-discuss] Issue with fsfreeze with qemu agent.

@nongnu.org Onderwerp: Re: [Qemu-discuss] Issue with fsfreeze with qemu agent. Hi, I have encountered this before. Some operating systems may have bind-mounts that let a device appear multiple times in the mount list. Unfortunately the guest agent is not smart enough to consider a device that has

Re: [Qemu-discuss] Issue with fsfreeze with qemu agent.

Hi, I have encountered this before. Some operating systems may have bind-mounts that let a device appear multiple times in the mount list. Unfortunately the guest agent is not smart enough to consider a device that has been frozen as succesfull and keep going. This causes this specific error.

[Qemu-discuss] Issue with fsfreeze with qemu agent.

Hi, I use external snapshots to backup my guests. I use the 'quiesce' option to flush and frees the guest file system with the qemu guest agent. With the exeption of one guest, this procedure works fine. On the 'unwilling' guest, I get this error message: "ERROR 2016-05-25 00:51:19 |