[vdsm] hosted-engine rebooting in the middle of setup (was: [Users] [ANN] oVirt 3.4.0 Release Candidate is now available)
- Original Message - From: Darrell Budic darrell.bu...@zenfire.com To: Sandro Bonazzola sbona...@redhat.com Cc: annou...@ovirt.org, engine-devel engine-de...@ovirt.org, arch a...@ovirt.org, us...@ovirt.org, VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Saturday, March 1, 2014 1:56:23 AM Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available Started testing this on two self-hosted clusters, with mixed results. There were updates from 3.4.0 beta 3. On both, got informed the system was going to reboot in 2 minutes while it was still installing yum updates. On the faster system, the whole update process finished before the 2 minutes were up, the VM restarted, and all appears normal. On the other, slower cluster, the 2 minutes hit while the yum updates were still being installed, and the system rebooted. It continued rebooting every 3 minutes or so, and the engine console web pages are not available because the engine doesn’t start. it did this at least 3 times before I went ahead and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn’t reveal what requested the reboot. That was rather impolite of something to do that without warning :) At least it was recoverable. Seems like scheduling the reboot while the yum updates were still running seems like a poor idea as well. Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/* You can of course open a bug on bugzilla and attach there logs if you want. Thanks, and thanks for the report! -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] ovirt-guest-agent on debian
Hi, - Original Message - From: Sven Kieske svenkie...@gmail.com To: vdsm-devel@lists.fedorahosted.org Sent: Tuesday, January 21, 2014 10:41:10 PM Subject: [vdsm] ovirt-guest-agent on debian -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, here are my results so far. I did: install debian 7 x64 into a vm as root: mkdir code cd code git clone git://gerrit.ovirt.org/ovirt-guest-agent cd ovirt-guest-agent ./autogen.sh ./autogen.sh: 3: ./autogen.sh: autoreconf: not found apt-get install dh-autoreconf ./autogen.sh ./configure configure: error: no suitable Python interpreter found apt-get install python ./configure ./configure: line 15790: --variable=systemdsystemunitdir: command not found checking for pep8... no configure: WARNING: python-pep8 not found ./configure: line 15868: syntax error near unexpected token 'GDM_PLUGIN, ' ./configure: line 15868: ' PKG_CHECK_MODULES(GDM_PLUGIN; ' apt-get install pep8 I found this: http://lists.ovirt.org/pipermail/users/2013-August/015773.html so I tried: ./configure --with-gdm=no --with-sso=no but I get the same errors again. Doing less configure shows however that this options should be recognized and supported? Any help will be appreciated. Did you try as a start the packages pointed at from [1]? I will try to maintain some manual and get patches in so we can get a stable build for Debian. Thanks! [1] http://www.ovirt.org/How_to_install_the_guest_agent_in_Ubuntu Best regards, -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Engine-devel] Gerrit NEW Change Screen
- Original Message - From: Vinzenz Feenstra vfeen...@redhat.com To: Itamar Heim ih...@redhat.com, vdsm-devel@lists.fedorahosted.org, engine-devel engine-de...@ovirt.org Sent: Thursday, January 16, 2014 11:40:01 AM Subject: Re: [Engine-devel] Gerrit NEW Change Screen On 01/16/2014 10:38 AM, Vinzenz Feenstra wrote: On 01/15/2014 11:08 PM, Itamar Heim wrote: with gerrit 2.8, there is a new change screen. its not enabled by default (yet), please use and see what you think. to enable, go to settings (click the top-right arrow next to your name, and choose settings). select preferences and set Change View: to New Screen. Well I had this enabled for some time today but I had to switch back, since I don't see how I am able to apply code review +/- or anything like this. Correction, I just found it. It's hidden under the Reply... button And if you hover on it you see that you can also press 'a'. In 2.6 'r' did this, not sure why they had to change that. And if you press 'r' inside a diff you get to the old review/reply page... On the other hand, it is way faster on the diff view even for vdsm's vm.py which has a whopping 5k lines. I like that :-) This new change screen is something one really needs to get used to. Indeed. One thing I like in it is that in History it shows also all the inline comments. And one thing I miss is a solution to [1] - am I the only one bugged by it? [1] http://code.google.com/p/gerrit/issues/detail?id=217 -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] source code
From: aditya mamidwar aditya.mamid...@gmail.com To: dougsl...@redhat.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Tuesday, December 24, 2013 9:47:19 AM Subject: Re: [vdsm] source code hw do i obtain source code of ovirt from development community. I suggest that you start in this page: http://www.ovirt.org/Develop As explained there, oVirt is comprised of several sub-projects. I guess that as a minimum, you'll need to look at vdsm (about which you already asked) and the engine - to get the code for it, do $ git clone git://gerrit.ovirt.org/ovirt-engine Best regards, -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] addNetwork to use existing nic conf
Hi all, While looking at [1], and reading the source of bridge.py of ovirt-hosted-engine-setup and of ovirt-host-deploy, I think the correct thing will be for addNetwork to not require either bootproto=dhcp or ipaddr/netmask/etc., but to take this from the existing conf of the nics to be put inside the bridge. Does this make sense? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1013666 Thanks! -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] addNetwork to use existing nic conf
- Original Message - From: Antoni Segura Puimedon asegu...@redhat.com To: Yedidyah Bar David d...@redhat.com Cc: vdsm-devel vdsm-de...@fedorahosted.org, Alon Bar-Lev alo...@redhat.com, Sandro Bonazzola sbona...@redhat.com Sent: Wednesday, November 27, 2013 11:52:51 AM Subject: Re: addNetwork to use existing nic conf - Original Message - From: Yedidyah Bar David d...@redhat.com To: vdsm-devel vdsm-de...@fedorahosted.org Cc: Alon Bar-Lev alo...@redhat.com, Sandro Bonazzola sbona...@redhat.com, Antoni Segura Puimedon asegu...@redhat.com Sent: Wednesday, November 27, 2013 10:38:54 AM Subject: addNetwork to use existing nic conf Hi all, While looking at [1], and reading the source of bridge.py of ovirt-hosted-engine-setup and of ovirt-host-deploy, I think the correct thing will be for addNetwork to not require either bootproto=dhcp or ipaddr/netmask/etc., but to take this from the existing conf of the nics to be put inside the bridge. You mean the addNetwork in vdsm/vdsm/configNetwork.py? We currently use vdsClient - 'vdsClient addNetwork'. If that is the case I would very much prefer not to make such change, since that would make addNetwork even farther from referential transparency. What I propose is that the calling code will use the new getBootProto introduced in: http://gerrit.ovirt.org/18484 (already merged). Does vdsClient support that? -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] [libvirt] Host local_host running without virtualization hardware acceleration
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Kletzander mklet...@redhat.com Cc: libvir-l...@redhat.com, vdsm-devel vdsm-de...@fedorahosted.org, users us...@ovirt.org Sent: Tuesday, November 5, 2013 11:56:24 AM Subject: Re: [Users] [libvirt] Host local_host running without virtualization hardware acceleration Il 05/11/2013 10:49, Martin Kletzander ha scritto: 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.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it) Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore. I've found that: # modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license:GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool) This is good, but AFAIK this module is not what provides /dev/kvm. Depending on the processor you're using, try checking 'kvm_intel' or 'kvm_amd'. Also make sure both are loaded. I've found that, missing kvm_intel. # /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory looking at strace: open(/dev/kvm, O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory) What does ls -lZ /dev/kvm tell you? it doesn't existed, now it's working again after modprobe kvm_intel Any clue on what may be happened? No idea, but I'm basing everything on the fact that it worked before the re-install, am I right? right. something was loading that module automatically before reinstall and now I needed to create a conf file for having it loaded. Perhaps it was libvirtd, and in your new setup it's not started automatically on boot? -- Didi ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
