On Fri, 2011-06-24 at 00:47 +, Qiao Liyong wrote:
Hello James
I have tried it on Red Hat :
if you run libvirtd manually , it can also get correct status with
'service libvirtd status', and you can not run two processes of libvirtd .
I don't have a Redhat system to test
Hi James :
What does a separate process mean?
How can I know which libvirtd servicing qemu:///system or qemu:///session?
Run libvirtd manually and run libvirtd by service libvirt-bin start ,
they use the same pid file :
root@qiaoliyong-ThinkPad-T410:~# libvirtd -d
On Fri, 2011-06-24 at 08:00 +, Qiao Liyong wrote:
Hi James :
What does a separate process mean?
How can I know which libvirtd servicing qemu:///system or qemu:///session?
The one servicing qemu:///session runs with the uid of the account
accessing the session.
[...]
I don't
@Qaio, Thanks for the bug and following it up. To allow us to better
understand the issue, can you provide a use case for why you would need
to invoke the libvirtd manually?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
On Fri, 2011-06-24 at 00:47 +, Qiao Liyong wrote:
Hello James
I have tried it on Red Hat :
if you run libvirtd manually , it can also get correct status with
'service libvirtd status', and you can not run two processes of libvirtd .
I don't have a Redhat system to test
Hi James :
What does a separate process mean?
How can I know which libvirtd servicing qemu:///system or qemu:///session?
Run libvirtd manually and run libvirtd by service libvirt-bin start ,
they use the same pid file :
root@qiaoliyong-ThinkPad-T410:~# libvirtd -d
On Fri, 2011-06-24 at 08:00 +, Qiao Liyong wrote:
Hi James :
What does a separate process mean?
How can I know which libvirtd servicing qemu:///system or qemu:///session?
The one servicing qemu:///session runs with the uid of the account
accessing the session.
[...]
I don't
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801038
Title:
@Qaio, Thanks for the bug and following it up. To allow us to better
understand the issue, can you provide a use case for why you would need
to invoke the libvirtd manually?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Qiao
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The different between your two test cases is that you are not using the
init system to start libvirtd in case 1. This means that the init
system (upstart) does not track the libvirtd instance in any way
Hello James
I have tried it on Red Hat :
if you run libvirtd manually , it can also get correct status with 'service
libvirtd status', and you can not run two processes of libvirtd .
And I also confused about that : why can I run two Daemon processes
(libvirtd) at the same
Hi Qiao
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The different between your two test cases is that you are not using the
init system to start libvirtd in case 1. This means that the init
system (upstart) does not track the libvirtd instance in any way
Hello James
I have tried it on Red Hat :
if you run libvirtd manually , it can also get correct status with 'service
libvirtd status', and you can not run two processes of libvirtd .
And I also confused about that : why can I run two Daemon processes
(libvirtd) at the same
13 matches
Mail list logo
