1:43 p.m.
I used to run many VMs on my Ubuntu 10.04 box. However, after upgrading to
Ubuntu 12.10 (and thus, libvirt 0.9.13), The VMs can't be recognized anymore.
Nothing appears in the output of 'virsh list --all', nor in virt-manager.
When I created a new VM based on a disk image of one of the
not-recognized-any-more VMs, a new schema file has been auto-generated, and the
new VM now is recognized.
So, if this is caused by incompatibility with the old schemas, would the
solution be to manually recreate all the VMs by importing their disk images to
the newly created VMs, or is there a more intelligent approach?
Thanks for your time.
Marwan
10:34 a.m.
On Sat, Feb 23, 2013 at 11:43 PM, Marwan Tanager <marwan.tngr(a)gmail.com> wrote:
I used to run many VMs on my Ubuntu 10.04 box. However, after
upgrading to
Ubuntu 12.10 (and thus, libvirt 0.9.13), The VMs can't be recognized anymore.
Nothing appears in the output of 'virsh list --all', nor in virt-manager.
When I created a new VM based on a disk image of one of the
not-recognized-any-more VMs, a new schema file has been auto-generated, and the
new VM now is recognized.
So, if this is caused by incompatibility with the old schemas, would the
solution be to manually recreate all the VMs by importing their disk images to
the newly created VMs, or is there a more intelligent approach?
Thanks for your time.
Marwan
capabilities detection for qemu/kvm bits likely failed. Do you have
kvm and kvm_amd or kvm_intel loaded? Best place to start is checking
/var/log/libvirt/libvirtd.log
--
Doug Goldstein
3:41 p.m.
New subject: [libvirt-users] VMs XML definitions can't be recognized after upgrading to libvirt 0.9.13
On Tue, Feb 26, 2013 at 08:34:08PM -0600, Doug Goldstein wrote:
On Sat, Feb 23, 2013 at 11:43 PM, Marwan Tanager
<marwan.tngr(a)gmail.com> wrote:
> I used to run many VMs on my Ubuntu 10.04 box. However, after upgrading to
> Ubuntu 12.10 (and thus, libvirt 0.9.13), The VMs can't be recognized anymore.
> Nothing appears in the output of 'virsh list --all', nor in virt-manager.
>
> When I created a new VM based on a disk image of one of the
> not-recognized-any-more VMs, a new schema file has been auto-generated, and the
> new VM now is recognized.
>
> So, if this is caused by incompatibility with the old schemas, would the
> solution be to manually recreate all the VMs by importing their disk images to
> the newly created VMs, or is there a more intelligent approach?
capabilities detection for qemu/kvm bits likely failed. Do you have
kvm and kvm_amd or kvm_intel loaded? Best place to start is checking
/var/log/libvirt/libvirtd.log
Yes, I have the kvm modules loaded and working, but only with new VMs, like I
said above.
Here's what I've found in the logs:
-----------------------------------------------------------------------------------------
2013-02-24 04:55:01.818+0000: 14242: info : libvirt version: 0.9.13
2013-02-24 04:55:01.818+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:01.857+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:01.857+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:01.858+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:01.858+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:01.859+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:01.859+0000: 14242: error : virDomainDefParseXML:8817 : unsupported
configuration: Only the first console can be a serial port
2013-02-24 04:55:11.398+0000: 14232: error : interfaceNumOfInterfaces:195 : internal error
failed to get number of interfaces on host: unspecified error - errors in loading some
config files
2013-02-24 04:55:11.432+0000: 14233: error : interfaceNumOfInterfaces:195 : internal error
failed to get number of interfaces on host: unspecified error - errors in loading some
config files
2013-02-24 04:55:11.467+0000: 14237: error : interfaceNumOfDefinedInterfaces:237 :
internal error failed to get number of defined interfaces on host: unspecified error -
errors in loading some config files
-----------------------------------------------------------------------------------------
I also noticed that the last two error messages are filling the entire log
file. Any suggestions?
Marwan
4267
days inactive
4270
days old
2 comments
2 participants
participants (2)
-
Doug Goldstein -
Marwan Tanager