I was planning to test this on different qcow images on an s390x host:
$ file *
CentOS-7-x86_64-GenericCloud-1907.qcow2: QEMU QCOW2 Image (v2),
8589934592 bytes
focal-s390x-cloudimage.qcow2: QEMU QCOW2 Image (v3),
2361393152 bytes
ubuntu-16.04-server-cloudimg-amd64-disk1.qcow2: QEMU QCOW2 Image (v2),
2361393152 bytes
But already on the first image (s390x to stay native):
$ sudo virt-customize -a focal-s390x-cloudimage.qcow2 --run-command 'touch
virt-hello.txt'
[ 0.0] Examining the guest ...
[ 31.6] Setting a random seed
virt-customize: warning: random seed could not be set for this type of
guest
[ 31.6] Setting the machine ID in /etc/machine-id
[ 31.6] Running: touch virt-hello.txt
virt-customize: error: host cpu (x86_64) and guest arch (s390x) are not
compatible, so you cannot use command line options that involve running
commands in the guest. Use --firstboot scripts instead.
If reporting bugs, run virt-customize with debugging enabled and include
the complete output:
virt-customize -v -x [...]
With that, for now, I can confirm the bug as reported
** Changed in: libguestfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864164
Title:
virt-customize fails with "host cpu (x86_64) and guest arch (s390x)
are not compatible" when running on s390x host
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1864164/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
