On Wed, Aug 13, 2014 at 12:31:35PM -0400, Tom Horsley wrote:
I'm upgrading a prehistoric fedora13 machine that hosted
a gazillion virtual machines to centos 7.
I find that the old virtual machine xml files make
the new libvirt barf.
I can get a good idea of how to fix all the old xml
by installing a new file and comparing things, but
I wonder where this magic comes from:
Specifically, the "machine" definitions. Should that just
always be the string above since my host is centos 7?
Slightly OT, but if you guest is _not_ Windows then you can just drop
the machine=... attribute and libvirt will pick a suitable one next
time the guest starts.
For Windows, the machine type is needed to ensure stability of the
virtual hardware so that Windows doesn't try to reactivate itself.
Other OSes don't suffer from this problem.
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.