On 06/14/2013 06:55 PM, Kevin Maziere Aubry wrote:
Hi
I add a similar issue on fedora18, I fixed it :
yum update --enablerepo=updates-testing systemd-197-1.fc18.2
Do know if it can help.
while requires all hosts in the cluster to be the same, please check if
reproduces with an updated
Nicolas Ecarnot nicolas@... writes:
Le 20/04/2013 22:55, Itamar Heim a écrit :
On 03/27/2013 10:38 AM, Nicolas Ecarnot wrote:
Le 26/03/2013 12:17, Nicolas Ecarnot a écrit :
Le 25/03/2013 12:10, Nicolas Ecarnot a écrit :
Le 24/03/2013 09:53, Dafna Ron a écrit :
is the vm preallocated
Hi
I add a similar issue on fedora18, I fixed it :
yum update --enablerepo=updates-testing systemd-197-1.fc18.2
Do know if it can help.
Kevin
2013/6/14 Cuongds cuongds@gmail.com
Nicolas Ecarnot nicolas@... writes:
Le 20/04/2013 22:55, Itamar Heim a écrit :
On 03/27/2013 10:38
Le 20/04/2013 22:55, Itamar Heim a écrit :
On 03/27/2013 10:38 AM, Nicolas Ecarnot wrote:
Le 26/03/2013 12:17, Nicolas Ecarnot a écrit :
Le 25/03/2013 12:10, Nicolas Ecarnot a écrit :
Le 24/03/2013 09:53, Dafna Ron a écrit :
is the vm preallocated or thin provision disk type?
This VM has 3
On 03/27/2013 10:38 AM, Nicolas Ecarnot wrote:
Le 26/03/2013 12:17, Nicolas Ecarnot a écrit :
Le 25/03/2013 12:10, Nicolas Ecarnot a écrit :
Le 24/03/2013 09:53, Dafna Ron a écrit :
is the vm preallocated or thin provision disk type?
This VM has 3 disks :
- first disk to host the windows
Le 26/03/2013 12:17, Nicolas Ecarnot a écrit :
Le 25/03/2013 12:10, Nicolas Ecarnot a écrit :
Le 24/03/2013 09:53, Dafna Ron a écrit :
is the vm preallocated or thin provision disk type?
This VM has 3 disks :
- first disk to host the windows system : Thin provision
- second disk to store
Le 25/03/2013 12:10, Nicolas Ecarnot a écrit :
Le 24/03/2013 09:53, Dafna Ron a écrit :
is the vm preallocated or thin provision disk type?
This VM has 3 disks :
- first disk to host the windows system : Thin provision
- second disk to store some data : Preallocated
- third disk to store some
is the vm preallocated or thin provision disk type?
also, can you please attach engine, vdsm, libvirt and the vm's qemu logs?
On 03/22/2013 11:59 AM, Nicolas Ecarnot wrote:
Hi,
After two months of stable usage of this 3.1 oVirt setup, here comes
the first blocking issue for which I've no
Hi,
After two months of stable usage of this 3.1 oVirt setup, here comes the
first blocking issue for which I've no other mean to ask some hint.
When I'm starting a VM, the start process is running fine. Being fast
enough, we can ssh-connect to it, but 5 seconds later, the VM is paused.
In
I got hit up with the same issue - I think it had something to do with
latency or timeout to my NAS/SAN, despite an isolated prioritised
storage network.
I'm guessing the VDSM puts VM's in a paused state whenever it hits a
slight panic or speed-wobble.
I've, for the time-being, moved to a
Le 22/03/2013 11:29, Jaco a écrit :
I got hit up with the same issue - I think it had something to do with
latency or timeout to my NAS/SAN, despite an isolated prioritised
storage network.
I'm guessing the VDSM puts VM's in a paused state whenever it hits a
slight panic or speed-wobble.
OK,
11 matches
Mail list logo