On 07/09/2012 03:38 PM, Todd And Margo Chester wrote:> On 07/09/2012 03:05 PM,
P. Larry Nelson wrote:
Hi Todd and/or Margo,
On 7/9/12 4:50 PM, Todd And Margo Chester wrote:
On 07/09/2012 02:33 PM, Connie Sieh wrote:
On Mon, 9 Jul 2012, Todd And Margo Chester wrote:
Hi All,
I am in trouble here. I would really appreciate any help
you guys can 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
What security errata and other rpms have been installed recently?
-Connie Sieh
Hi Connie,
Thank you for the quick response.
Two weeks ago, I installed "hexedit". Nothing since then, except
for downgrading my "flash-plugin"
-T
Yes, but what about any possible behind-the-scenes security upgrades?
Check /var/log/yum.log
(Just a thought...)
- Larry
Oh my. A lot of stuff goes on in the background. These
two look interesting:
Jul 09 11:18:50 Updated: libvirt-0.9.10-21.el6.x86_64
Jul 09 11:19:22 Updated: selinux-policy-targeted-3.7.19-155.el6_3.noarch
Hi Larry and Connie,
The both of you called it. It did not know I got
updated in the background. I should have been suspicious
when my stink' flash-plugin mysteriously got updated.
Larry's pointing me to /var/log/yum.log was a
light bulb moment.
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
Thank you both so much!
-T
p.s. bet you can't guess what my next post is going to be!
