Failed to start domain due to internal error with sanlock
This is a multi-part message in MIME format. ------_=_NextPart_001_01D10BDD.D1221AD9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a = cluster setup). After running for a long while (months), it has run into = an issue where it current cannot start a new VM. An internal error happens due to feature (0x01) from = libvirt...SanLock...New. If there are request for specific log files for analysis, please let me = know and I will include these. Does anyone recognize this issue or know a resolution? Best regards, - Joris Dobbelsteen ------_=_NextPart_001_01D10BDD.D1221AD9 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7654.12"> <TITLE>Failed to start domain due to internal error with sanlock</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT SIZE=3D2>Hi all,<BR> <BR> I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a = cluster setup). After running for a long while (months), it has run into = an issue where it current cannot start a new VM.<BR> An internal error happens due to feature (0x01) from = libvirt...SanLock...New.<BR> <BR> If there are request for specific log files for analysis, please let me = know and I will include these.<BR> <BR> Does anyone recognize this issue or know a resolution?<BR> <BR> Best regards,<BR> <BR> - Joris Dobbelsteen<BR> </FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01D10BDD.D1221AD9--
Hi Joris, Please attach the engine, VDSM and sanlock logs (/var/log/sanlock.log). Which Storage Domains does this setup contains? Can you create a disk? Thanks, Maor ----- Original Message -----
From: "Joris Dobbelsteen" <Joris@familiedobbelsteen.nl> To: users@ovirt.org Sent: Wednesday, October 21, 2015 11:52:29 AM Subject: [ovirt-users] Failed to start domain due to internal error with sanlock
Failed to start domain due to internal error with sanlock
Hi all,
I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a cluster setup). After running for a long while (months), it has run into an issue where it current cannot start a new VM. An internal error happens due to feature (0x01) from libvirt...SanLock...New.
If there are request for specific log files for analysis, please let me know and I will include these.
Does anyone recognize this issue or know a resolution?
Best regards,
- Joris Dobbelsteen
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Maor Lipchuk" <mlipchuk@redhat.com> To: "Joris Dobbelsteen" <Joris@familiedobbelsteen.nl> Cc: users@ovirt.org Sent: Wednesday, October 21, 2015 2:49:35 PM Subject: Re: [ovirt-users] Failed to start domain due to internal error with sanlock
Hi Joris,
Please attach the engine, VDSM and sanlock logs (/var/log/sanlock.log). Which Storage Domains does this setup contains? Can you create a disk?
I got confused here, you wrote that you can't start a domain in the mail subject, but you mentioned that you have tried to run a VM. did you try also to reconstruct your DC?
Thanks, Maor
----- Original Message -----
From: "Joris Dobbelsteen" <Joris@familiedobbelsteen.nl> To: users@ovirt.org Sent: Wednesday, October 21, 2015 11:52:29 AM Subject: [ovirt-users] Failed to start domain due to internal error with sanlock
Failed to start domain due to internal error with sanlock
Hi all,
I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a cluster setup). After running for a long while (months), it has run into an issue where it current cannot start a new VM. An internal error happens due to feature (0x01) from libvirt...SanLock...New.
If there are request for specific log files for analysis, please let me know and I will include these.
Does anyone recognize this issue or know a resolution?
Best regards,
- Joris Dobbelsteen
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-----Original Message----- From: Maor Lipchuk [mailto:mlipchuk@redhat.com] Sent: Wednesday, October 21, 2015 13:51 To: Joris Dobbelsteen Cc: users@ovirt.org Subject: Re: [ovirt-users] Failed to start domain due to internal error withsanlock [snip]
Please attach the engine, VDSM and sanlock logs (/var/log/sanlock.log). Which Storage Domains does this setup contains? Can you create a disk?
Hi Maor, Thanks for your help. Please find the logs attached. I cut them a bit, so I hope they contain everything you need. The server was started about 6 months ago. There are 2 DCs: "default", which is empty and "Tilburg" with 1 cluster and 1 host. There are 4 storage domains. 1 ISO (NFS) and 3 "Local on Host". It's a bit of a too-lite setup for oVirt, but the interface is great.
I got confused here, you wrote that you can't start a domain in the mail subject, but you mentioned that you have tried to run a VM. did you try also to reconstruct your DC?
It was morning in Europe. And I was sloppy with terms. Sorry for the confusion. Domain is supposed to be "Virtual Machine". I created it fresh, and allocated a thinly provisioned disk on one of the "Local on Host" storage domains. Pressing "Run" or "RunOnce" for the virtual machine consistently results in: " VM build-arm-mcu is down with error. Exit message: internal error unsupported flags (0x1) in function virLockManagerSanlockNew. " [snip]
----- Original Message -----
From: "Joris Dobbelsteen" <Joris@familiedobbelsteen.nl> To: users@ovirt.org Sent: Wednesday, October 21, 2015 11:52:29 AM Subject: [ovirt-users] Failed to start domain due to internal error
with
sanlock
Failed to start domain due to internal error with sanlock
Hi all,
I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a cluster setup). After running for a long while (months), it has run into an issue where it current cannot start a new VM. An internal error happens due to feature (0x01) from libvirt...SanLock...New.
If there are request for specific log files for analysis, please let me know and I will include these.
Does anyone recognize this issue or know a resolution?
Best regards,
- Joris Dobbelsteen
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Joris Dobbelsteen -
Maor Lipchuk