We've found out that if libvirtd got restarted then VMs with disabled
memory balloon device are wrongly reported as being in the paused state.
It's a bug and we're working on a fix.
___
Users mailing list
Users@ovirt.org
Bill James writes:
> .recovery setting before removing:
> p298
> sS'status'
> p299
> S'Paused'
> p300
>
> After removing .recovery file and shutdown and restart:
> V0
> sS'status'
> p51
> S'Up'
> p52
Thank you for the information. I was able to reproduce the problem with
.recovery setting before removing:
p298
sS'status'
p299
S'Paused'
p300
After removing .recovery file and shutdown and restart:
V0
sS'status'
p51
S'Up'
p52
So far looks good, GUI show's VM as Up.
another host was:
p318
sS'status'
p319
S'Paused'
p320
after moving .recovery file and
/run/vdsm/.recovery
On Fri, Apr 29, 2016 at 10:59 PM, Bill James wrote:
> where do I find the recovery files?
>
> [root@ovirt1 test vdsm]# pwd
> /var/lib/vdsm
> [root@ovirt1 test vdsm]# ls -la
> total 16
> drwxr-xr-x 6 vdsm kvm100 Mar 17 16:33 .
> drwxr-xr-x. 45 root
where do I find the recovery files?
[root@ovirt1 test vdsm]# pwd
/var/lib/vdsm
[root@ovirt1 test vdsm]# ls -la
total 16
drwxr-xr-x 6 vdsm kvm100 Mar 17 16:33 .
drwxr-xr-x. 45 root root 4096 Apr 29 12:01 ..
-rw-r--r-- 1 vdsm kvm 10170 Jan 19 05:04 bonding-defaults.json
drwxr-xr-x 2
> On 29 Apr 2016, at 18:26, Bill James wrote:
>
> yes they are still saying "paused" state.
> No, bouncing libvirt didn't help.
Then my suspicion of vm recovery gets closer to a certainty:)
Can you get one of the paused vm's .recovery file from /var/lib/vdsm and check
it
yes they are still saying "paused" state.
No, bouncing libvirt didn't help.
I noticed the errors about the ISO domain. Didn't think that was related.
I have been migrating a lot of VMs to ovirt lately, and recently added
another node.
Also had some problems with /etc/exports for a while, but I
> On 28 Apr 2016, at 19:40, Bill James wrote:
>
> thank you for response.
> I bold-ed the ones that are listed as "paused".
>
>
> [root@ovirt1 test vdsm]# virsh -r list --all
> IdName State
>
> On 27 Apr 2016, at 19:16, Bill James wrote:
>
> virsh # list --all
> error: failed to connect to the hypervisor
> error: no valid connection
> error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such
> file or directory
>
you need to run virsh in
> On 27 Apr 2016, at 02:04, Nir Soffer wrote:
>
> jjOn Wed, Apr 27, 2016 at 2:03 AM, Bill James wrote:
>> I have a hardware node that has 26 VMs.
>> 9 are listed as "running", 17 are listed as "paused".
>>
>> In truth all VMs are up and running fine.
>>
jjOn Wed, Apr 27, 2016 at 2:03 AM, Bill James wrote:
> I have a hardware node that has 26 VMs.
> 9 are listed as "running", 17 are listed as "paused".
>
> In truth all VMs are up and running fine.
>
> I tried telling the db they are up:
>
> engine=> update vm_dynamic set status
11 matches
Mail list logo