We'll charge you for excessive bandwidth.
--
Jerry Feldman
Boston Linux and Unix http://www.blu.org
PGP key id: 6F6BB6E7
PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6
B B6E7
On Mon, Jun 1, 2020, 5:51 PM Lloyd Kvam wrote:
> Well the solution was ridiculously easy.
>1. bo
Well the solution was ridiculously easy.
1. boot the normal kernel and make sure libvirtd is running
2. run virt-manager; create a new virthost specifying the old .img file
So all my concerns about converting the image file and salvaging details were
unnecessary. The
magic just works.
I ho
On Mon, 2020-06-01 at 13:51 -0400, Tom Buskey wrote:
> On my Fedora 31, I only have 2 xen rpms:
> xen-licenses-4.12.2-3.fc31.x86_64
> xen-libs-4.12.2-3.fc31.x86_64
I have started trying to migrate. Unfortunately, virt-v2v requires a working
libvirtd to move
things along. qemu-img is trying to con
On my Fedora 31, I only have 2 xen rpms:
xen-licenses-4.12.2-3.fc31.x86_64
xen-libs-4.12.2-3.fc31.x86_64
If you don't need xen specifically, you shouldn't use a xen kernel.
Everything is using KVM nowadays
On Mon, Jun 1, 2020 at 9:17 AM Lloyd Kvam wrote:
> On Sun, 2020-05-31 at 20:10 -0400, Jer
On Sun, 2020-05-31 at 20:10 -0400, Jerry Feldman wrote:
> Why are you using the xen kernel.
I had set this up years ago (2012??) using Xen and haven't tried to change it.
Other than a
brief problem a few years back, it has worked smoothly.
I am reading up on the libvirt image handling now so tha
