[Pkg-libvirt-commits] [Git][libvirt-team/virt-what][upstream/latest] 6 commits: alibaba-cloud: Make the test more robust

[Jeremy Bicha (@jbicha)]

Jeremy Bicha pushed to branch upstream/latest at Libvirt Packaging Team / virt-what


Commits:
26b2c9c5 by Richard W.M. Jones at 2022-08-03T18:43:02+01:00
alibaba-cloud: Make the test more robust

This test worked by trying to make an HTTP connection to a path under
100.100.100.200, which if successful would indicate that it's an
Alibaba cloud instance.  We only try the connection if SM-BIOS
information indicates the hardware OEM is Alibaba.

However 'make check' would hang if 100.100.100.200 doesn't immediately
reject the connection.  I found that GCE is such an environment where
connecting to this address would hang rather than reject.  GCE does
not have Alibaba hardware of course, but when doing 'make check' we
fake dmidecode data.

Make the test more robust by only trying to connect when we know we're
not in 'make check'.

Fixes: commit b7cc3d93a613ef6d0ac5ccd6e32cc3d66e057243

- - - - -
54b726fa by Richard W.M. Jones at 2022-08-03T17:55:22+00:00
tests: Add test for Google Cloud Engine

This was actually a GCE aarch64 instance, but I believe the
architecture makes no difference as all we're looking for is the
characteristic string in dmidecode output.

Thanks: Craig Donnelly
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2114997
Updates: commit 8363fa9f0e2cbd970f34ffb7c7b23ed0ac2c374a

- - - - -
da3568b2 by Richard W.M. Jones at 2022-08-08T12:17:29-04:00
google-cloud: Print "kvm" fact on aarch64 instances

GCE instances are KVM with a non-QEMU userspace.  On x86-64 we should
recognize this from the CPUID information, but aarch64 has no
equivalent to this.  /proc/device-tree/hypervisor/compatible contains
something but RHEL does not use device tree.  However the SMBIOS
tables exported by GCE do contain:

  Manufacturer: KVM

so we can use that.

  # uname -m
  aarch64
  # virt-what
  google_cloud
  kvm

This commit also updates the test.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2114997
Updates: commit 54b726fa7c9687b692162488e8934a426f9fa6c3
Thanks: Eric Auger, Yongkui Guo

- - - - -
39001e7c by Xiao Liang at 2022-08-09T08:54:59+01:00
detect AWS arm virtual instance as kvm

AWS arm virtual instance is KVM based hypervisor.
With this patch:
$ sudo virt-what
kvm
aws
$ cat /sys/devices/virtual/dmi/id/product_name
t4g.small

Without it:
$ sudo virt-what
aws

Signed-off-by: Xiao Liang <xiliang at redhat.com>

- - - - -
1bd3ea52 by Richard W.M. Jones at 2022-08-17T10:57:19+01:00
Version 1.25.

- - - - -
98a4bb6a by Jeremy Bicha at 2022-10-12T14:27:48-04:00
New upstream version 1.25
- - - - -


5 changed files:

- Makefile.in
- aclocal.m4
- compile
- config.guess
- config.sub


The diff was not included because it is too large.


View it on GitLab: https://salsa.debian.org/libvirt-team/virt-what/-/compare/475330fe7bc7f911235acf975c2f157967bacaa0...98a4bb6a3b07b7cb88e382e4edb61aaa2d13778e

-- 
View it on GitLab: https://salsa.debian.org/libvirt-team/virt-what/-/compare/475330fe7bc7f911235acf975c2f157967bacaa0...98a4bb6a3b07b7cb88e382e4edb61aaa2d13778e
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-commits/attachments/20221012/9fbf70f3/attachment-0001.htm>