public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: ToddAndMargo <ToddAndMargo@zoho.com>
To: kvm@vger.kernel.org
Subject: KVM VM's disappeared
Date: Mon, 09 Jul 2012 16:07:54 -0700	[thread overview]
Message-ID: <4FFB644A.9080101@zoho.com> (raw)

>>> Hi All,
>>>
>>> I am in trouble here.  I would really appreciate any help
>>> you guys an spare.
>>>
>>> Scientific Linux 6.2, 64 bit.  (Red Hat Enterprise Linux 6.2 clone)
>>>
>>> $ rpm -qa \*qemu\*
>>> qemu-kvm-0.12.1.2-2.209.el6_2.4.x86_64
>>> qemu-img-0.12.1.2-2.209.el6_2.4.x86_64
>>> gpxe-roms-qemu-0.9.7-6.9.el6.noarch
>>>
>>> $ uname -r
>>> 2.6.32-220.23.1.el6.x86_64
>>>
>>> When I fired up my KVM Virtual Machine Manager (virt-manager)
>>> this morning, four of my seven virtual machines disappeared,
>>> including the one is desperately need.
>>>
>>> Checking /etc/libvirt/qemu and they are all there.  Same
>>> attributes too.  Checking where I put the virtual hard
>>> drives and they are all there too.
>>>
>>> Okay, so I try firing up the three that remain, I get the
>>> following error message:
>>>
>>>      Error starting domain: unsupported configuration: spice
>>>      TLS port set in XML configuration, but TLS is disabled
>>>      in qemu.conf
>>>
>>> Yes, each VM has a different spice port set so I can tell them
>>> apart.  This has always worked smoothly.
>>>
>>> Huh? qemu.conf is the default.  The one with everything
>>> commented out.  I even checked my backup: no change in
>>> qemu.conf.
>>>
>>> Checking /var/log/libvirt/libvirtd.log gives:
>>>
>>> 2012-07-09 19:36:41.957+0000: 2821: info : libvirt version: 0.9.10,
> package: 21.el6 (Scientific Linux, 2012-06-22-02:34:35, sl6.fnal.gov)
>>> 2012-07-09 19:36:41.957+0000: 2821: error :
> virDomainDefParseXML:8871 : Maximum CPUs greater than topology limit
>>> 2012-07-09 19:36:41.959+0000: 2821: error :
> virDomainDefParseXML:8871 : Maximum CPUs greater than topology limit
>>> 2012-07-09 19:36:41.959+0000: 2821: error :
> virDomainDefParseXML:8871 : Maximum CPUs greater than topology limit
>>> 2012-07-09 19:36:41.960+0000: 2821: error :
> virDomainDefParseXML:8871 : Maximum CPUs greater than topology limit
>>> 2012-07-09 19:47:59.089+0000: 2811: error :
> qemuBuildCommandLine:5526 : unsupported configuration: spice TLS port set in XML configuration, but TLS is disabled in qemu.conf
>>>
>>> Again with the spice port error.
>>>
>>> The only thing I did to my system between working yesterday and
>>> not working today was downgrade my flash-plugin.
>>>
>>> I tried setting "spice_tls = 1" in qemu.conf, but the other
>>> four VM still do not show up.  Spice lays an egg on the ones
>>> that do show up, so I set spice_tls back to commented out.
>>>
>>> I removed qemu-kvm-0.12.1.2-2.209.el6_2.4.x86_64,
>>> rebooted, reinstalled, rebooted.  No symptom change.
>>>
>>> What is the world?  I can not find anything wrong!
>>>
>>> Many thanks,
>>> -T
>>
>>
>> Another symptom.  I can not edit ANY of the VMs:
>>
>> # virsh edit KVM-W8.xml
>> error: failed to get domain 'KVM-W8.xml'
>> error: Domain not found: no domain with matching name 'KVM-W8.xml'
>
> Same thing when I dropped the .xml from the name.  The three that
> show up work, the other four do not
>


Figured it out.  A bad update for libvirt.  Looking at
/var/log/yum.log, I found:
     Jul 09 11:18:50 Updated: libvirt-0.9.10-21.el6.x86_64

I did not ask for this update.  Somehow it went on in
the background.


The following fixed my problem:

# yum downgrade libvirt  libvirt-client  libvirt-python
Loaded plugins: priorities, refresh-packagekit, security
Setting up Downgrade Process
18 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package libvirt.x86_64 0:0.9.4-23.el6 will be a downgrade
---> Package libvirt.x86_64 0:0.9.10-21.el6 will be erased
---> Package libvirt-client.x86_64 0:0.9.4-23.el6 will be a downgrade
---> Package libvirt-client.x86_64 0:0.9.10-21.el6 will be erased
---> Package libvirt-python.x86_64 0:0.9.4-23.el6 will be a downgrade
---> Package libvirt-python.x86_64 0:0.9.10-21.el6 will be erased
--> Finished Dependency Resolution

Next step, Red Hat's bugzilla.

-T


             reply	other threads:[~2012-07-09 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 23:07 ToddAndMargo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-09 22:16 KVM VM's disappeared ToddAndMargo
2012-07-09 22:15 ToddAndMargo
2012-07-09 22:04 ToddAndMargo
2012-07-09 21:27 ToddAndMargo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FFB644A.9080101@zoho.com \
    --to=toddandmargo@zoho.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox