Re: [Users] Missing CPU features [CPU Name] [Wrong cpu identification]

On 12/13/2012 01:14 PM, Pere G. Soria wrote: > I added Host[gondor] to the oVirt Engine 3.1, after installing all > packages. > Host gondor moved to Non-Operational state as host does not meet the > cluster's minimum CPU level. Missing CPU features : model_Nehalem > > This Box is a Intel(R) Xeon(

Re: [Users] Missing CPU features [CPU Name] [Wrong cpu identification]

On 12/13/2012 03:27 PM, Itamar Heim wrote: > On 12/13/2012 02:55 PM, Martin Kletzander wrote: >> On 12/13/2012 01:14 PM, Pere G. Soria wrote: >>> I added Host[gondor] to the oVirt Engine 3.1, after installing all >>> packages. >>> Host gondor moved to Non-Ope

Re: [Users] VM migrations failing

On 01/30/2013 08:40 PM, Dead Horse wrote: > The nodes are EL6.3 based. > > Currently installed libvirt packages: > > libvirt-lock-sanlock-0.9.10-21.el6_3.8.x86_64 > libvirt-cim-0.6.1-3.el6.x86_64 > libvirt-0.9.10-21.el6_3.8.x86_64 > libvirt-python-0.9.10-21.el6_3.8.x86_64 > libvirt-client-0.9.10-

Re: [Users] VM migrations failing

On 01/31/2013 10:25 AM, Dan Kenigsberg wrote: > On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote: >> On 01/30/2013 08:40 PM, Dead Horse wrote: >>> The nodes are EL6.3 based. >>> >>> Currently installed libvirt packages: >>> >

Re: [Users] VM migrations failing

On 01/31/2013 11:56 AM, Dan Kenigsberg wrote: > On Thu, Jan 31, 2013 at 11:08:58AM +0100, Martin Kletzander wrote: >> On 01/31/2013 10:25 AM, Dan Kenigsberg wrote: >>> On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote: >>>> On 01/30/2013 08:40 PM, Dea

Re: [Users] VM migrations failing

;>> I reverted VDSM on my two test nodes to an earlier build of VDSM >>>> (commit: >>>> c343e1833f7b6e5428dd90f14f7807dca1baa0b4) >>>> VDSM after the above commit is broken due to commit: >>>> fc3a44f71d2ef202cff18d7203b9e4165b546621 however

Re: [Users] VM migrations failing

On 02/01/2013 09:29 PM, Dead Horse wrote: > To test further I loaded up two more identical servers with EL 6.3 and the > same package versions originally indicated. The difference here is that I > did not turn these into ovirt nodes. EG: installing VDSM. > > - All configurations were left at defau

Re: [Users] VM migrations failing

On 02/03/2013 08:40 AM, Dan Kenigsberg wrote: > On Fri, Feb 01, 2013 at 11:44:08PM +0100, Martin Kletzander wrote: >> On 02/01/2013 09:29 PM, Dead Horse wrote: >>> To test further I loaded up two more identical servers with EL 6.3 and the >>> same package version

Re: [Users] ovirt reporting wrong cpu family

On 02/16/2013 10:02 PM, Itamar Heim wrote: > On 16/02/2013 22:46, Adrian Gibanel wrote: >> Yes, I know. I meant a workaround where the processor is detected as >> SandyBridge. > > Adrian - please provide libvirt version. > Martin - can you please take a look? I'm not sure what kind of help I can

Re: [Users] ovirt reporting wrong cpu family (2nd server)

re almost always is, I remember only one CPU without a chance and that was because the HW itself really didn't know the function. Unfortunately, sometimes (HW-dependant) it really has to be set in BIOS/UEFI. For some changes there are utilities, so you don't have to have physical acces

Re: [Users] ovirt reporting wrong cpu family

On 03/02/2013 05:07 PM, Adrian Gibanel wrote: > Sorry for the late answer. I was kind of busy. I reply inline below. > > - Mensaje original - > >> De: "Martin Kletzander" >> Para: "Itamar Heim" >> CC: "Adrian Gibanel" , u

Re: [Users] ovirt 3.2 all-in-one setup always fails

On 03/12/2013 06:39 PM, Alex Lourie wrote: > Hi Alex > > On Sun, Mar 10, 2013 at 4:26 PM, Alex Leonhardt > wrote: >> Hi Alex, >> >> Regarding the dependencies - libvirtd would not start w/o having >> messagebus / avahi-daemon installed & running, however, it doesnt seem >> to come up as an depend

Re: [Users] save to restart libvirtd ?

On 04/15/2013 03:39 PM, Alex Leonhardt wrote: > Hi, > > I believe it's save, but just wanted to re-check, is it save to restart > libvirtd on a HV running ~40 VMs ? > Hi, for libvirt questions, I'd rather use libvirt-us...@redhat.com, but for this particular one, I can confirm that libvirt is w

Re: [Users] save to restart libvirtd ?

o the other mailing list to find out why / how it could > have grown this big :\ > There might be some memleaks, especially in older version. For this kind of stuff, I'd maybe use the libvir-list [1] Martin [1] http://www.redhat.com/mailman/listinfo/libvir-list > Thanks > Alex &g

Re: [Users] too much debugging in ovirt-node

On 06/26/2013 07:47 PM, Winfried de Heiden wrote: > Hi all, > > Using ovirt-node-iso-2.6.1-20120228.fc18.iso (2012 seems to be a typo, > must be 2013?) is logging with too much debugging. > > Changing all the"DEBUG" to "WARNOMG" in /etc/vdsm/logger.conf and > "persist /etc/vdsm/logger.conf" solve

Re: [Users] too much debugging in ovirt-node

at may be another point of failure. Martin [1] https://bugzilla.redhat.com/920614 [2] http://gerrit.ovirt.org/#/c/13642/ > > 2013/6/28 Martin Kletzander > >> On 06/26/2013 07:47 PM, Winfried de Heiden wrote: >>> Hi all, >>> >>> Using ovirt-node-iso-2.6

Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr

On 07/27/2013 09:50 PM, Dan Kenigsberg wrote: > On Fri, Jul 26, 2013 at 02:03:28PM -0400, Nicholas Kesick wrote: >>> Date: Fri, 26 Jul 2013 05:52:44 +0300 >>> From: ih...@redhat.com >>> To: cybertimber2...@hotmail.com >>> CC: dan...@redhat.com; users@ovirt.org >>> Subject: Re: [Users] oVirt 3.2 - M

Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr

On 07/29/2013 06:06 PM, Nicholas Kesick wrote: > > >> Date: Mon, 29 Jul 2013 09:56:30 +0200 >> From: mklet...@redhat.com >> To: dan...@redhat.com >> CC: cybertimber2...@hotmail.com; users@ovirt.org >> Subject: Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr >> >> On 07/27/2013

Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr

On 07/29/2013 06:06 PM, Nicholas Kesick wrote: > > >> Date: Mon, 29 Jul 2013 09:56:30 +0200 >> From: mklet...@redhat.com >> To: dan...@redhat.com >> CC: cybertimber2...@hotmail.com; users@ovirt.org >> Subject: Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr >> >> On 07/27/2013

Re: [Users] [libvirt] Host local_host running without virtualization hardware acceleration

On Tue, Nov 05, 2013 at 09:08:33AM +0100, Sandro Bonazzola wrote: > Hi, > I had to reinstall ovirt yesterday and now it seems that it doesn't work > anymore. > I'm running nightly on Fedora 18. > kernel-3.11.4-101.fc18.x86_64 > sanlock-2.8-1.fc18.x86_64 > libvirt-1.1.4-1.fc18.x86_64 > qemu-1.5

Re: [Users] json parsing error when live migrating

On 07/02/2012 05:03 PM, Nathanaël Blanchet wrote: > hello, > > I have this error very often when live migrating from host A -> host B > > libvirtError: erreur interne Unexpected JSON reply '{"error": {"class": > "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}}' > > > I'm using stable

Re: [Users] json parsing error when live migrating

g default cirrus xorg driver, while ovirt > creates qxl one as default. I've changed this on each concerned vms. Now > live migration successes everytime. > Hope it will be useful for people who will be in the same case. > > Le 03/07/2012 10:36, Martin Kletzander a écri

[Users] Setting up test nodes

Hi everyone, TL;DR: how do I setup a software node (faqemu) with apps from source? I'm new to the oVirt world and coming from the lower layer, I must admin I feel kind of confused. I'm trying to create a "lab" with ovirt-engine (up and running), some ovirt-node (with sw qemu) and ovirt-node with

Re: [Users] Unable to run VM with "Unable to create cgroup" error message

Hi, the only problem I could imagine is that there is really some directory missing, but you said it is there. Fromt his point I see two things you can try: 1) run libvirt with debugging output enabled [1] 2) try to create the directories manually Hopefully it'll give us more information on wha

Re: [Users] Unable to run VM with "Unable to create cgroup" error message

Sorry, I almost always forget the links :) [1] http://libvirt.org/logging.html Martin P.S.: don't hesitate to send other info and ask, I'd be happy to help, although I'm going away for week and a half. On 07/04/2012 10:12 AM, Martin Kletzander wrote: > Hi, > >

Re: [Users] Setting up test nodes

On 07/04/2012 10:46 AM, Doron Fediuck wrote: > On 03/07/12 21:27, Itamar Heim wrote: >> On 07/03/2012 03:48 PM, Martin Kletzander wrote: >>> Hi everyone, >>> >>> TL;DR: how do I setup a software node (faqemu) with apps from source? >> >> - do you w

Re: [Users] Unable to run VM with "Unable to create cgroup" error message

On 07/04/2012 02:36 PM, Andrew Cathrow wrote: > > > - Original Message - >> From: "Martin Kletzander" >> To: "xuejie chen" >> Cc: users@ovirt.org >> Sent: Wednesday, July 4, 2012 4:12:07 AM >> Subject: Re: [Users] Unable

Re: [Users] Unable to run VM with ”opening backend ‘pyt’ failed”

On 07/17/2012 02:41 AM, Mark Wu wrote: > On 07/16/2012 09:46 AM, xuejie chen wrote: >> > file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259 > Please upgrade vdsm to 4.10.0 as Dan suggeste

Re: [Users] Unable to run VM with ”opening backend ‘pyt’ failed”

On 07/20/2012 10:20 AM, xuejie chen wrote: > 2012/7/17 Martin Kletzander : >> On 07/17/2012 02:41 AM, Mark Wu wrote: >>> On 07/16/2012 09:46 AM, xuejie chen wrote: >>>> >>> file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25

Re: [Users] [User] why VM image owner change to root after stop the vm

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-

Re: [Users] [User] why VM image owner change to root after stop the vm

Thanks, I just wanted to make sure it's not libvirt that does this. On 07/25/2012 04:44 PM, T-Sinjon wrote: > 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

Re: [Users] [User] why VM image owner change to root after stop the vm

On 07/26/2012 02:30 PM, Dan Kenigsberg wrote: > On Thu, Jul 26, 2012 at 11:05:21AM +0800, T-Sinjon wrote: >> maybe it's a libvirt problem , since my nodes have used oVirt Node >> Hypervisor 2.2.2-2.2.fc16 >> >> engine: >> libvirt-0.9.11.4-3.fc17.x86_64 > This one is unused. > >> >> node: >> libv

Re: [Users] [User] why VM image owner change to root after stop the vm

522 root 20 0 909m 17m 7164 S 0.0 0.1 0:01.37 libvirtd > > 1523 root 20 0 909m 17m 7164 S 0.0 0.1 0:01.34 libvirtd > > 1524 root 20 0 909m 17m 7164 S 0.0 0.1 0:01.30 libvirtd > > On 26 Jul, 2012, at 8:51 PM, Martin Kl

Re: [Users] [User] why VM image owner change to root after stop the vm

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 installing one-purpose system, so I won't be able to tell you exactly, but v

Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification

Oh, sorry to hear that, that doesn't sound good. What did change on the server with reboot? I wonder how this is possible. Martin On 08/01/2012 06:32 PM, Ricardo Esteves wrote: > And now, after reboot of the node, i get this: > > [root@blade4 ~]# virsh capabilities > Segmen

Re: [Users] Failure to migrate from one host out of four

Hi, Thanks for reporting this, I've found now where the problem is and it is in libvirt. However this issue is not easy to fix as it reveals more than just this one problem. The format for outputting floating point numbers into JSON string seems to be locale-dependent. Could you send me what local

Re: [Users] Failure to migrate from one host out of four

On 08/02/2012 03:10 PM, Karli Sjöberg wrote: > > 2 aug 2012 kl. 15.05 skrev Martin Kletzander: > >> Hi, >> >> Thanks for reporting this, I've found now where the problem is and it is >> in libvirt. However this issue is not easy to fix as it reveals more >