On Tue, Jul 31, 2012 at 02:15:12PM +0200, Martin Kletzander wrote:
It looks like this exactly could be the problem. I don't know how the
node installation works, but when you install normal system it shouldn't
start any services until you specify that. Of course this is another
story when
I have 6 node , they all installed by ovirt-node-image-2.2.2-2.2.fc16.iso
some of them had been added from engine web , the others added via admin@node UI
I confirm that they both have the problem .
Since it's reproducible , I'll open a case later.
On 1 Aug, 2012, at 7:00 PM, Dan Kenigsberg
yeah, everything went ok after restart libvirtd
I have do a test :
Install a new node, the problem always there (any possible that
dynamic_ownership=0 # by vdsm has done after libvirtd starting??)
On 30 Jul, 2012, at 10:46 PM, Martin Kletzander wrote:
OK, so it is done by libvirt. However,
Dear everyone:
Description
When i create a vm , the vm owner is vdsm:kvm(36:36)
when i start a vm , the vm owner change to qemu:qemu(107:107)
-rw-rw. 1 qemu qemu 107374182400 Jul 25 2012
d1e6b671-6b48-4964-9c56-22847e9b83df
-rw-r--r--. 1 vdsm kvm 269 Jul 25 2012
On 07/25/2012 10:36 AM, T-Sinjon wrote:
Dear everyone:
Description
When i create a vm , the vm owner is vdsm:kvm(36:36)
when i start a vm , the vm owner change to qemu:qemu(107:107)
-rw-rw. 1 qemu qemu 107374182400 Jul 25 2012
d1e6b671-6b48-4964-9c56-22847e9b83df
-rw-r--r--. 1
both engine and node dynamic_ownership are 0
On 25 Jul, 2012, at 5:56 PM, Martin Kletzander wrote:
On 07/25/2012 10:36 AM, T-Sinjon wrote:
Dear everyone:
Description
When i create a vm , the vm owner is vdsm:kvm(36:36)
when i start a vm , the vm owner change to qemu:qemu(107:107)
6 matches
Mail list logo