On Mon, Mar 24, 2008 at 02:12:25PM +0900, Saori Fukuta wrote:
Hello,
Thanks for applying the first patch (about adding read-only connections).
http://git.et.redhat.com/?p=libvirt.git;a=commit;h=4faeb0d567976377b2661fb5ebd0f1dca7763f80
How about the second one ? We can make some
On Mon, 24 Mar 2008 05:27:04 -0400 Daniel Veillard wrote:
On Mon, Mar 24, 2008 at 02:12:25PM +0900, Saori Fukuta wrote:
How about the second one ? We can make some improvements for virsh
schedinfo command with the patch, so I want the patch to be committed
if it is OK.
I had
On Mon, Mar 24, 2008 at 07:37:51PM +0900, Saori Fukuta wrote:
Thank you for applying it. I will try syntax-check next time.
thanks :-)
However, i don't see why it is needed, basically when running with Xen
as root, the hypervisor access should be used, not xend, so this seems to
Hello,
Thanks for applying the first patch (about adding read-only connections).
http://git.et.redhat.com/?p=libvirt.git;a=commit;h=4faeb0d567976377b2661fb5ebd0f1dca7763f80
How about the second one ? We can make some improvements for virsh
schedinfo command with the patch, so I want the patch
Hi,
I add the Xen Scheduler APIs to xenDaemonDriver.
- xenDaemonGetSchedulerType
- xenDaemonGetSchedulerParameters
- xenDaemonSetSchedulerParameters
We will have the following improvements by this patch:
1) xenDaemonDriver of Schedulr is usable
when xenHypervisorDriver failed.
On Thu, Mar 13, 2008 at 05:30:57PM +0900, Saori Fukuta wrote:
Hi,
I add the Xen Scheduler APIs to xenDaemonDriver.
I just applied the first patch about forbidding scheduler operations
on read-only connections, that's simple and uncontroversial. I have not
yet looked at the second patch,
