[sles-beta] SLES12 RC1 KVM client Productname
urs.frey at post.ch
urs.frey at post.ch
Wed Aug 20 04:07:22 MDT 2014
Hi Antoine
Thank you very much for your information and steps how to change the HW type in the clients xml profile
>> So it is not Qemu, which has changed its behavior, but dmidecode which now does obviously show the real qemu standard value.
>> And because dmidecode has changed, facter does also show the "real" qemu default value.
>i don't know how your machine type ihas changed, but
>but something has changed the value in the libvirt xml configuration,
>so the VM guest machine type reported by dmidecode was altered.
No, I disagree: NOTHING and NOBODY has changed the libvirt xml configuration so far on Dom0.
See here on SLES11-SP3
================
h05bug:/etc/libvirt/qemu # cat h039uc.xml
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
virsh edit h039uc
or other application using the libvirt API.
-->
<domain type='kvm'>
<name>h039uc</name>
<uuid>55647a92-2d6d-a557-99f1-20acfe3db7aa</uuid>
<memory unit='KiB'>2097152</memory>
<currentMemory unit='KiB'>2097152</currentMemory>
<vcpu placement='static'>2</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type>
<boot dev='hd'/>
</os>
===================
And on the KVM client under SLES11-SP3 the client reports with dmidecode
h039uc:~ # dmidecode | grep Product
Product Name: Bochs
h039uc:~ # uname -a
Linux h039uc 3.0.101-0.31-default #1 SMP Wed Jun 4 08:59:53 UTC 2014 (87c5279) x86_64 x86_64 x86_64 GNU/Linux
h039uc:~ #
h039uc:~ # lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 6
Model: 2
Stepping: 3
CPU MHz: 2099.998
BogoMIPS: 4199.99
Virtualization: AMD-V
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
NUMA node0 CPU(s): 0,1
h039uc:~ #
========================
Now here on SLES12 RC1
h05cni:/etc/libvirt/qemu # uname -a
Linux h05cni 3.12.25-2-default #1 SMP Mon Jul 28 12:18:48 UTC 2014 (1b84426) x86_64 x86_64 x86_64 GNU/Linux
h05cni:/etc/libvirt/qemu # cat h05cnh.xml
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
virsh edit h05cnh
or other application using the libvirt API.
-->
<domain type='kvm'>
<name>h05cnh</name>
<uuid>9b291448-befe-2d7e-2eda-20bde0715fae</uuid>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>4</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-2.0'>hvm</type>
<boot dev='hd'/>
</os>
<features>
===================
And on the KVM client under SLES12-RC1 the client reports with dmidecode
h05cnh:~ # dmidecode | grep Product
Product Name: Standard PC (i440FX + PIIX, 1996)
h05cnh:~ # lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 4
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 6
Model name: QEMU Virtual CPU version 2.0.0
Stepping: 3
CPU MHz: 2199.998
BogoMIPS: 4399.99
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0-3
h05cnh:~ #
==================================
So you can see that on the client the output of dmidecode has changed.
There is no change on Dom0 in the libvirt xml so far.
All set up using vm-install, the graphical utility.
Best regards
Urs Frey
Post CH AG
Informationstechnologie
IT Betrieb
Webergutstrasse 12
3030 Bern (Zollikofen)
Telefon : ++41 (0)58 338 58 70
FAX : ++41 (0)58 667 30 07
E-Mail: urs.frey at post.ch
-----Ursprüngliche Nachricht-----
Von: Antoine Ginies [mailto:aginies at suse.com]
Gesendet: Tuesday, August 19, 2014 7:49 PM
An: Frey Urs, IT222
Cc: sles-beta at lists.suse.com
Betreff: Re: AW: [sles-beta] SLES12 RC1 KVM client Productname
urs.frey at post.ch:
> >Antoine Ginies
> Hi Antoine
>
> Thank you very much for your answer, I have read with very high interest.
>
> >By default machine type for Qemu is pc-i440fx:
> >under SLES12 host:
> >linux-x61s:~ # qemu-system-x86_64 -M ? | grep default
> >pc-i440fx-2.0 Standard PC (i440FX + PIIX, 1996) (default)
> >
> >and under SLE11SP3 host:
> >pc-i440fx-1.4 Standard PC (i440FX + PIIX, 1996) (default)
>
> >Machine type can be changed. So it's not a bug if the machine type was
> >specified to launch the VM guest.
>
> ON my KVM Dom0 (Hypervisor) I can see what the supported values with qemu-system-x86_64 are.
> What I miss is some KVM related value in the list below.
>
> SLES12-RC1
> ==========
> h05cni:~ # uname -a
> Linux h05cni 3.12.25-2-default #1 SMP Mon Jul 28 12:18:48 UTC 2014 (1b84426) x86_64 x86_64 x86_64 GNU/Linux
> h05cni:~ #
> h05cni:~ # qemu-system-x86_64 -M ?
> h05cni:~ # qemu-system-x86_64 -machine help
> Supported machines are:
> pc-0.13 Standard PC (i440FX + PIIX, 1996)
> pc Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-2.0)
> pc-i440fx-2.0 Standard PC (i440FX + PIIX, 1996) (default)
> pc-1.0 Standard PC (i440FX + PIIX, 1996)
> pc-q35-1.7 Standard PC (Q35 + ICH9, 2009)
> pc-1.1 Standard PC (i440FX + PIIX, 1996)
> q35 Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-2.0)
> pc-q35-2.0 Standard PC (Q35 + ICH9, 2009)
> pc-i440fx-1.4 Standard PC (i440FX + PIIX, 1996)
> pc-i440fx-1.5 Standard PC (i440FX + PIIX, 1996)
> pc-0.14 Standard PC (i440FX + PIIX, 1996)
> pc-0.15 Standard PC (i440FX + PIIX, 1996)
> xenfv Xen Fully-virtualized PC
> pc-q35-1.4 Standard PC (Q35 + ICH9, 2009)
> isapc ISA-only PC
> pc-0.10 Standard PC (i440FX + PIIX, 1996)
> pc-1.2 Standard PC (i440FX + PIIX, 1996)
> pc-0.11 Standard PC (i440FX + PIIX, 1996)
> pc-i440fx-1.7 Standard PC (i440FX + PIIX, 1996)
> pc-i440fx-1.6 Standard PC (i440FX + PIIX, 1996)
> none empty machine
> xenpv Xen Para-virtualized PC
> pc-q35-1.5 Standard PC (Q35 + ICH9, 2009)
> pc-q35-1.6 Standard PC (Q35 + ICH9, 2009)
> pc-0.12 Standard PC (i440FX + PIIX, 1996)
> pc-1.3 Standard PC (i440FX + PIIX, 1996)
> h05cni:~ #
>
> SLES11-SP3
> ===========
> h062rm:~ # uname -a
> Linux h062rm 3.0.101-0.31-default #1 SMP Wed Jun 4 08:59:53 UTC 2014 (87c5279) x86_64 x86_64 x86_64 GNU/Linux
> h062rm:~ # qemu-kvm -machine help
> Supported machines are:
> q35 Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-1.4)
> pc-q35-1.4 Standard PC (Q35 + ICH9, 2009)
> pc Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-1.4)
> pc-i440fx-1.4 Standard PC (i440FX + PIIX, 1996) (default)
> pc-1.3 Standard PC
> pc-1.2 Standard PC
> pc-1.1 Standard PC
> pc-1.0 Standard PC
> pc-0.15 Standard PC
> pc-0.14 Standard PC
> pc-0.13 Standard PC
> pc-0.12 Standard PC
> pc-0.11 Standard PC, qemu 0.11
> pc-0.10 Standard PC, qemu 0.10
> isapc ISA-only PC
> none empty machine
> h062rm:~ #
>
> -machine [type=]name[,prop[=value][,...]]
> selects emulated machine ('-machine help' for list)
> property accel=accel1[:accel2[:...]] selects accelerator
> supported accelerators are kvm, xen, tcg (default: tcg)
> kernel_irqchip=on|off controls accelerated irqchip support
> kvm_shadow_mem=size of KVM shadow MMU
> dump-guest-core=on|off include guest memory in a core dump (default=on)
> mem-merge=on|off controls memory merge support (default: on)
>
> Maybe you misunderstood:
> I did set up this KVM client with the graphical virt-install and also using vm-install.
> But there setting of HW type I could not find yet
> So obviously the graphical tools do detect by their own setting the default value.
Yes the graphical tool should use the default value, and it should be
"pc-i440fx" by default.
> What I noted is that obviously dmidecode does show a different result from SLES11-SP3 & SLES12 Beta9 towards SLES12 RC1
I didn't done any test under BETA9. Lets focus on SLE11SP3 and SLE12RC1
by default (with any changes).
Default Machine type for VM guest must be "pc-i440fx" if you have done
the installation using "virt-install" or "vm-install" tool.
Once the installation is done, the libvirt configuration will be in:
/etc/libvirt/qemu
if you grep "machine" in the xml file:
linux-x61s:/etc/libvirt/qemu # grep machine sles11.xml
<type arch='x86_64' machine='pc-i440fx-2.0'>hvm</type>
of course you can change this value using virsh (VM guest should be off):
********************
1) virsh -c qemu:///system
2) virsh # list --inactive
Id Name State
----------------------------------------------------
- sles11 shut off
3) virsh # edit sles11
********************
4) change the value between <os> </os> tag, in our example
we change the value to "pc-q35-2.0":
<os>
<type arch='x86_64' machine='pc-q35-2.0'>hvm</type>
<boot dev='hd'/>
</os>
********************
Domain sles11 XML configuration not changed.
5) virsh # start sles11
********************
log on the guest and check machine/Product:
********************
6) linux-ed3a:~ # dmidecode | grep Prod
Product Name: Standard PC (Q35 + ICH9, 2009)
********************
> So it is not Qemu, which has changed its behavior, but dmidecode which now does obviously show the real qemu standard value.
> And because dmidecode has changed, facter does also show the "real" qemu default value.
i don't know how your machine type ihas changed, but
but something has changed the value in the libvirt xml configuration,
so the VM guest machine type reported by dmidecode was altered.
regards.
> -----Ursprüngliche Nachricht-----
> Von: Antoine Ginies [mailto:aginies at suse.com]
> Gesendet: Tuesday, August 19, 2014 4:37 PM
> An: Frey Urs, IT222
> Cc: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] SLES12 RC1 KVM client Productname
>
> urs.frey at post.ch:
> > Hi
>
> Hello,
>
> >
> > When set up a SLES12 RC1 as KVM client, the productname looks quite strange now
> >
> > h05cnh:~ # facter | grep product
> > productname => Standard PC (i440FX + PIIX, 1996)
> > h05cnh:~ # uname -a
> > Linux h05cnh 3.12.25-2-default #1 SMP Mon Jul 28 12:18:48 UTC 2014 (1b84426) x86_64 x86_64 x86_64 GNU/Linux
> > h05cnh:~ # facter | grep product
> > productname => Standard PC (i440FX + PIIX, 1996)
> > h05cnh:~ # dmidecode | grep Product
> > Product Name: Standard PC (i440FX + PIIX, 1996)
> > h05cnh:~ # facter | grep virtual
> > is_virtual => true
> > virtual => kvm
> > h05cnh:~ #
>
> By default machine type for Qemu is pc-i440fx:
> under SLES12 host:
> linux-x61s:~ # qemu-system-x86_64 -M ? | grep default
> pc-i440fx-2.0 Standard PC (i440FX + PIIX, 1996) (default)
>
> and under SLE11SP3 host:
> pc-i440fx-1.4 Standard PC (i440FX + PIIX, 1996) (default)
>
>
> > Until Beta9 the output was different and more readable, as it was under SLES11-SP3
> > h039ua:~ # uname -a
> > Linux h039ua 3.12.22-2-default #1 SMP Fri Jun 13 13:46:18 UTC 2014 (ee1c2a2) x86_64 x86_64 x86_64 GNU/Linux
> > h039ua:~ # facter | grep product
> > productname => Bochs
> > h039ua:~ # dmidecode | grep Product
> > Product Name: Bochs
> > h039ua:~ # facter | grep virtual
> > is_virtual => true
> > virtual => kvm
> > h039ua:~ #
> >
> > Could this new unusual product name coming with SLES12-RC1 be considered as I bug?
>
> Machine type can be changed. So it's not a bug if the machine type was
> specified to launch the VM guest.
>
>
> regards.
>
> > I was searching also in SUSEConnect to see how KVM gets recognized and will be treated to be registered as virtual client
> >
> > I'll appreciate to get more information about this new product naming of a KVM client
> >
> > And also of course to get a hint where about to search in the code of suse connect to get an idea about hovKVM gets treated please
> > Thank you very much
> >
> > Best regards
> >
> > Urs Frey
> > Post CH AG
> > Informationstechnologie
> > IT Betrieb
> > Webergutstrasse 12
> > 3030 Bern (Zollikofen)
> > Telefon : ++41 (0)58 338 58 70
> > FAX : ++41 (0)58 667 30 07
> > E-Mail: urs.frey at post.ch<mailto:urs.frey at post.ch>
> >
> >
> >
>
> > _______________________________________________
> > sles-beta mailing list
> > sles-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sles-beta
>
>
> --
> Antoine Ginies <aginies at suse.com>
> Project Manager
> SUSE France
--
Antoine Ginies <aginies at suse.com>
Project Manager
SUSE France
More information about the sles-beta
mailing list