I actually found out the problem was somewhere else. By deleting the file, which seems to
be the lockfile in the data domain called "__DIRECT_IO_TEST__". The VM can now
start again without crashing.
Anyway, datacenter is in "non responsive" mode and data domain are now
"inavtive" and "unknown"
Any ideas ?
----- Mail original -----
De: "Alexis HAUSER" <alexis.hauser(a)telecom-bretagne.eu>
À: "Martin Polednik" <mpolednik(a)redhat.com>
Cc: "users" <users(a)ovirt.org>
Envoyé: Mercredi 8 Juin 2016 23:20:51
Objet: Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config
Wouldn't there be another way to access console from the
hypervisor to the hosted-engine (without X) ?
Not really if you don't have network afaik. Have you done the virsh
command with root permissions?
sudo virsh list
sudo virsh console vm
If list even under root permissions doesn't show anything, make sure
that the qemu process is running.
I can't see it with "virsh list" but I can see it with vdsClient -s 0 list
However the status id "Down" with "exitMessage = Failed to acquire lock: No
space left on device"
I can't actually run the VM anymore since I changed the VLAN of ovirtmgmt...
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users