search for: virfilereadall

Displaying 6 results from an estimated 6 matches for "virfilereadall".

2018 Jan 18
3
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...in the log: >> >> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000: >> 20438: warning : qemuGetProcessInfo:1460 : cannot parse process status >> data >> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: >> 20441: error : virFileReadAll:1420 : Failed to open file >> '/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpuacct.usage': >> >> No such file or directory >> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: >> 20441: error : virCgroupGetV...
2018 Jan 17
4
Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...' process is present, and there is the next error in the log: Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000: 20438: warning : qemuGetProcessInfo:1460 : cannot parse process status data Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: 20441: error : virFileReadAll:1420 : Failed to open file '/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpuacct.usage': No such file or directory Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: 20441: error : virCgroupGetValueStr:844 : Unable to read from '/sys/f...
2012 Oct 15
1
cannot start domain with SR-IOV interface
...h this interface configuration. The error reported is: error: Failed to start domain exp85-1 error: An error occurred, but the cause is unknown When I look into /var/log/messages I see the following messages: Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.145+0000: 17713: error : virFileReadAll:457 : Failed to open file '/var/run/libvirt/qemu/p1p1_vf0': No such file or directory Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.146+0000: 17713: error : qemuRemoveCgroup:740 : internal error Unable to find cgroup for exp85-1 Oct 15 15:25:48 dcswitch85 libvirtd[17709]:...
2014 Oct 14
1
virsh list hangs / guests not starting automatically
I followed the wiki[1] to create a KVM virtual machine using bridged network on CentOS 6.5. It seemed to work fine on initial setup. (FWIW I'm trying to run a MythBuntu guest.) However, after a reboot, it doesn't auto-start the VMs. Shortly after boot, if I go into "virsh", then do a "list", it just hangs. Likewise, if I go into "virt manager", it just
2018 Jan 17
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...and there is the next error in the log: > > Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000: > 20438: warning : qemuGetProcessInfo:1460 : cannot parse process status data > Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: > 20441: error : virFileReadAll:1420 : Failed to open file > '/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpuacct.usage': > No such file or directory > Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: > 20441: error : virCgroupGetValueStr:844 : Unable to r...
2018 Jan 18
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
..., >and there is the next error in the log: > >Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000: >20438: warning : qemuGetProcessInfo:1460 : cannot parse process status data >Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: >20441: error : virFileReadAll:1420 : Failed to open file >'/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpuacct.usage': >No such file or directory >Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000: >20441: error : virCgroupGetValueStr:844 : Unable to read...