On 6/26/19 12:17 PM, Samuel Sieb wrote:
On 6/26/19 9:03 AM, Robert Moskowitz wrote:
> On 6/26/19 2:00 AM, Samuel Sieb wrote:
>> On 6/25/19 6:13 PM, Robert Moskowitz wrote:
>>> I started QEMU, then went through the steps of migrating an image.
>>> This worked with this F21 image from F21 to F24 and again to F28.
>>> This image has some restricted content data that I work with in
>>> this manner.
>>
>> What are your "steps of migrating an image"? Do you copy the xml
>> definition file for the VM as well?
>
> Adding the xml file was not enough. So here are the steps:
If you copy the xml file over, you will need to "systemctl restart
libvirtd" to pick it up. The better way would be to run "virsh create
/path/to/old.xml". See if that works.
Deleted image file from last attempt. Got image from backup. Rebooted.
# virsh create /etc/libvirt/qemu/fedora21.xml
error: Failed to create domain from /etc/libvirt/qemu/fedora21.xml
error: invalid argument: could not find capabilities for arch=x86_64
domaintype=kvm
> This time I am using 2MB memory (last was 1MB; I can't figure out how
> to tell what I assigned back on the F28 system)
I hope you really mean 2GB. The info is in that xml file.
Yes. 2GB.
> After the kernel select menu, it moves on to a blank screen with a
> flashing kernel. Finally I am seeing messages on the screen. Top is
> reporting 200% cpu utilization.
>
> It too over 2 hours until it got to the login dialog!
>
> I am checking things out, but I am see terrible performance.
>
> 4493 qemu 20 0 4541024 1.7g 19780 S 105.0 54.5 55:46.00
> qemu-syst+
>
> Often 200% on my x140e. I am trying to start firefox right now, and
> that is taking long as well.
>
> So something is wrong with qemu at least in regards to F21 support.
Do you have any other VMs on that system? I suspect you don't have
the kvm support loaded or the VM is not configured to use it.
No it is the only one. I have been using this as a private work area
since F21 and since I have tools built for it, I have just kept that
image as is.