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 Si
Turn on virtualization support in BIOS?
> On Jun 26, 2019, at 18:55, Robert Moskowitz 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
FOLLOW @NewsHour
-Original Message-
From:
Sent: Wed, 26 Jun 2019 16:30:40 -0700
To: 3603060...@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:
>>&g
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
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 i
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 vi
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/fedora2
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
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: inval
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 f
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
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.
_
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
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
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 con
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.
Got it. Thanks.
Doing a proper shutdown instead of force off on the F28 system and will
do a complete resetup.
On 6/26/19 6:06 AM, Ed Greshko wrote:
On 6/26/19 5:35 PM, Robert Moskowitz wrote:
No copying of any xml file. Where is it located?
Usually under /etc/libvirt/qemu/
__
On 6/26/19 5:35 PM, Robert Moskowitz wrote:
> No copying of any xml file. Where is it located?
Usually under /etc/libvirt/qemu/
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
color scheme
___
users mailing list --
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 restrict
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 ima
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 th
21 matches
Mail list logo
