First I installed QEMU on F30:
dnf groupinstall "virtualization" dnf install qemu virt-manager libvirt systemctl enable libvirtd systemctl start libvirtd systemctl enable libvirt-guests systemctl start libvirt-guests
I backed up my fedora21.qcow2 from my old F28 system and then copied it to the new F30 system. The target directory on each system is:
/var/lib/libvirt/images
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.
This time, with F30, the migration failed and kept looping based on what I saw in the QEMU session via a <Alt-D>.
Anyone working with QEMU with EOL Fedora images?
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?
No copying of any xml file. Where is it located?
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? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
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:
Create a new virtual machine Import existing disk image click browse click the Fedora21 image file click on chose this image Choose operating system start typing fedora, then click on including EOL versions; select Fedora 21
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) Also 2 cpus, as I have 4. finish
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.
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.
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.
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.
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.
I will delete what I just did and try again. Stay tuned.
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.
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. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
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.
On 6/26/19 2:43 PM, Samuel Sieb wrote:
On 6/26/19 10:06 AM, Robert Moskowitz wrote:
# 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
Make sure you have qemu-kvm installed.
It is:
Package qemu-kvm-2:3.1.0-8.fc30.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete!
On 6/26/19 1:46 PM, Robert Moskowitz wrote:
On 6/26/19 2:43 PM, Samuel Sieb wrote:
On 6/26/19 10:06 AM, Robert Moskowitz wrote:
# 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
Make sure you have qemu-kvm installed.
It is:
What does "lsmod | grep kvm" show?
On 6/26/19 5:35 PM, Samuel Sieb wrote:
On 6/26/19 1:46 PM, Robert Moskowitz wrote:
On 6/26/19 2:43 PM, Samuel Sieb wrote:
On 6/26/19 10:06 AM, Robert Moskowitz wrote:
# 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
Make sure you have qemu-kvm installed.
It is:
What does "lsmod | grep kvm" show?
# lsmod | grep kvm kvm 741376 0 irqbypass 16384 1 kvm
On 6/26/19 2:52 PM, Robert Moskowitz wrote:
On 6/26/19 5:35 PM, Samuel Sieb wrote:
On 6/26/19 1:46 PM, Robert Moskowitz wrote:
On 6/26/19 2:43 PM, Samuel Sieb wrote:
On 6/26/19 10:06 AM, Robert Moskowitz wrote:
# 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
Make sure you have qemu-kvm installed.
It is:
What does "lsmod | grep kvm" show?
# lsmod | grep kvm kvm 741376 0 irqbypass 16384 1 kvm
You appear to be missing the architecture specific one for some reason. Depending on whether you have an AMD or Intel CPU, use one of the following: modprobe kvm-amd modprobe kvm-intel
On 6/26/19 6:41 PM, Samuel Sieb wrote:
On 6/26/19 2:52 PM, Robert Moskowitz wrote:
On 6/26/19 5:35 PM, Samuel Sieb wrote:
On 6/26/19 1:46 PM, Robert Moskowitz wrote:
On 6/26/19 2:43 PM, Samuel Sieb wrote:
On 6/26/19 10:06 AM, Robert Moskowitz wrote:
# 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
Make sure you have qemu-kvm installed.
It is:
What does "lsmod | grep kvm" show?
# lsmod | grep kvm kvm 741376 0 irqbypass 16384 1 kvm
You appear to be missing the architecture specific one for some reason. Depending on whether you have an AMD or Intel CPU, use one of the following: modprobe kvm-amd modprobe kvm-intel
It is an AMD:
cat /dev/cpu/0/cpuid AuthcAMDentip
# modprobe kvm-amd modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
On 6/26/19 3:55 PM, Robert Moskowitz wrote:
cat /dev/cpu/0/cpuid AuthcAMDentip
?
# modprobe kvm-amd modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
The journal should have some more info, but it looks like either this CPU is too old for kvm or, more likely, you have virtualization disabled in the BIOS.
On 6/26/19 7:09 PM, Samuel Sieb wrote:
On 6/26/19 3:55 PM, Robert Moskowitz wrote:
cat /dev/cpu/0/cpuid AuthcAMDentip
?
Just saying it is an AMD chip.
# modprobe kvm-amd modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
The journal should have some more info, but it looks like either this CPU is too old for kvm or, more likely, you have virtualization disabled in the BIOS.
It is newer than the x120e that I was using before. But the BIOS might be it. I will have to check. And maybe update the BIOS.
On 6/26/19 4:17 PM, Robert Moskowitz wrote:
On 6/26/19 7:09 PM, Samuel Sieb wrote:
On 6/26/19 3:55 PM, Robert Moskowitz wrote:
cat /dev/cpu/0/cpuid AuthcAMDentip
?
Just saying it is an AMD chip.
Yes, but the output was weird. That "file" provides some sort of binary information which is not good for outputting to the terminal. /proc/cpuinfo is much better or if you really want a lot of useful details, install the cpuinfo program.
FOLLOW @NewsHour
-----Original Message----- From: users@lists.fedoraproject.org Sent: Wed, 26 Jun 2019 16:30:40 -0700 To: 3603060030@txt.att.net Subject: Re: F30 QEMU migration of a F21 image failed to start
On 6/26/19 4:17 PM, Robert Moskowitz wrote:
On 6/26/19 7:09 PM, Samuel Sieb wrote:
On 6/26/19 3:55 PM, Robert Moskowitz wrote:
cat /dev/cpu/0/cpuid AuthcAMDentip
================================================================== This mobile text message is brought to you by AT&T
Turn on virtualization support in BIOS?
On Jun 26, 2019, at 18:55, Robert Moskowitz rgm@htt-consult.com wrote:
On 6/26/19 6:41 PM, Samuel Sieb wrote:
On 6/26/19 2:52 PM, Robert Moskowitz wrote:
On 6/26/19 5:35 PM, Samuel Sieb wrote:
On 6/26/19 1:46 PM, Robert Moskowitz wrote:
On 6/26/19 2:43 PM, Samuel Sieb wrote: > On 6/26/19 10:06 AM, Robert Moskowitz wrote: > # 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
Make sure you have qemu-kvm installed.
It is:
What does "lsmod | grep kvm" show?
# lsmod | grep kvm kvm 741376 0 irqbypass 16384 1 kvm
You appear to be missing the architecture specific one for some reason. Depending on whether you have an AMD or Intel CPU, use one of the following: modprobe kvm-amd modprobe kvm-intel
It is an AMD:
cat /dev/cpu/0/cpuid AuthcAMDentip
# modprobe kvm-amd modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Virtualization was disabled in the BIOS. This is the first system I have had it set that way. I just forgot to check that off.
I will add this to my install instructions notes!
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.
# virsh create /etc/libvirt/qemu/fedora21.xml Domain fedora21 created from /etc/libvirt/qemu/fedora21.xml
So my image is up and working and I can get back to work.
Only critical item left is the broadcom wifi. At least that I have found so far. Still a few more tests to run.
thanks all!
-
3603060030＠txt.att.net -
Ed Greshko -
Nate Pearlstein -
Robert Moskowitz -
Samuel Sieb