process id.
Regards
MATSUDA Daiki
(2012/02/04 2:07), Michael Roth wrote:
On 02/02/2012 10:25 PM, MATSUDA, Daiki wrote:
Hi, Michael!
Thank you for your working.
And I have a question the process id written in pid file.
If qemu-ga is ran as daemon, the parent process id not child is written
in pid file. So, id gotten by &#x
(2012/02/10 13:51), Michael Roth wrote:
On Fri, Feb 10, 2012 at 11:26:32AM +0900, MATSUDA, Daiki wrote:
(2012/02/04 2:07), Michael Roth wrote:
On 02/02/2012 10:25 PM, MATSUDA, Daiki wrote:
Hi, Michael!
Thank you for your working.
And I have a question the process id written in pid file.
If
(2012/02/14 6:37), Michael Roth wrote:
On Mon, Feb 13, 2012 at 11:14:03AM +0900, MATSUDA, Daiki wrote:
And in this week, I tried your Windows Guest Agent patches. It is a
little hard way.
At the first I wrote my work.
0. my node OS is RHEL 6.1.
1. build some mingw packages (mingw32-gcc, mingw
Hi, all.
I am trying QEMU Guest Agent and encountered a small bug. It is that the
PIDFILE remains when daemon start fails. And maybe forgotton to g_free().
MATSUDA, Daiki
diff -uNrp qemu/qemu-ga.c
qemu-c47f3223658119219bbe0b8d09da733d1c06e76f/qemu-ga.c
--- qemu/qemu-ga.c 2012-01-05 01:06
Hi, all.
I am trying QEMU Guest Agent and encountered a small bug. It is that the
PIDFILE remains when daemon start fails. And maybe forgotton to g_free().
MATSUDA, Daiki
diff -uNrp qemu/qemu-ga.c
qemu-c47f3223658119219bbe0b8d09da733d1c06e76f/qemu-ga.c
--- qemu/qemu-ga.c 2012-01-05 01:06
frozen filesystem.
I suggest to read the list from not frozen filesystem file or on-memory
data, e.g. /proc/mounts.
Regards
MATSUDA Daiki
--- qga/commands-posix.c.orig 2012-05-28 08:10:47.842332018 +0900
+++ qga/commands-posix.c2012-05-28 08:11:01.598340937 +0900
@@ -347,7 +347,7 @@ static
I tried qemu-1.1.0. But it says 1.1.50 and
$ echo VERSION
1.1.50
Is it correct ?
Regards
MATSUDA Daiki
thaw command to Guest, time error occurs on libvirt qemu
agent because of not catch Guest's answer.
In addition, its situation is worst because the Guest Filesystem is kept
as frozen.
The problem does not occur on RHEL 6.2 Guest OS and in about qemu-1.0 it
does not occur.
Regards
MATSUDA Daiki
