Hi Viktor,
that's a very interesting problem. Let's check if it's related to the
bridge. Start the vm and execute 'brctl show' on one host. Migrate it
to another host and execute 'brctl show' on that second host. Compare
those outputs and check if libvirt/kvm is correctly attaching the
network
Dear Szekelyi,
You could consider to contribute the new driver to our ecosystem
and/or write a post in our blog describing your customization.
Thanks!
On Fri, Sep 3, 2010 at 1:07 AM, Andreas Ntaflos d...@pseudoterminal.org wrote:
On Friday 03 September 2010 00:28:23 Székelyi Szabolcs wrote:
On Friday 03 September 2010 14.54.06 Ignacio M. Llorente wrote:
You could consider to contribute the new driver to our ecosystem
and/or write a post in our blog describing your customization.
Our development is sponsored by the state, thus everything we develop will be
open sourced, and so,
We are using GlusterFS and it works great :) With some tweaking we were able
to average around 90-120 megabits per second on reads and 25-35 megabits per
second on writes. Configuration is as follows:
2 file servers:
- Supermicro server motherboard with Intel Atom D510
- 4GB DDR2 RAM
- 6 x
Hi,
The other thing we may want to look at is to detect that the VM is
stopped in libvirt and move the VM to shutdown-epilog-done. There is
a ticket for this http://dev.opennebula.org/issues/335
Cheers
Ruben
On Fri, Sep 3, 2010 at 8:13 PM, Shi Jin jinzish...@yahoo.com wrote:
Hi, there,
I
