All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Okken <James.Okken@dialogic.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-owner@vger.kernel.org" <kvm-owner@vger.kernel.org>
Subject: RE: CentOS 7.2 HVM, PVM and/or PVHVM
Date: Fri, 31 Mar 2017 21:20:01 +0000	[thread overview]
Message-ID: <MWHPR0101MB3072B3F86F4A27EF13E11FF58D370@MWHPR0101MB3072.prod.exchangelabs.com> (raw)
In-Reply-To: <90670d4a-2c68-0050-157a-2dba290bc41a@redhat.com>

Oh wow.!? Is that really the case?
I'm surprised because I see these things in my centos7 KVM VMs (aren't they signs of a PVM or at least a PVHVM?

dmesg | grep -i virtual
[    0.000000] Booting paravirtualized kernel on KVM
[    0.398931] systemd[1]: Detected virtualization 'kvm'.


lsmod | grep virt
virtio_balloon         13664  0
virtio_blk             18156  5
virtio_console         28114  0
virtio_net             28024  0
virtio_pci             22913  0
virtio_ring            21524  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon virtio_console
virtio                 15008  5 virtio_blk,virtio_net,virtio_pci,virtio_balloon virtio_console


lspci | grep -i virt
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:04.0 Communication controller: Red Hat, Inc Virtio console
00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device
00:07.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon
00:09.0 Ethernet controller: Red Hat, Inc Virtio network device

Not to doubt anyone, I am just wanting to understand this fully.,

Thanks

--Jim




-----Original Message-----
From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of Paolo Bonzini
Sent: Friday, March 31, 2017 7:14 AM
To: James Okken; kvm@vger.kernel.org; kvm-owner@vger.kernel.org
Subject: Re: CentOS 7.2 HVM, PVM and/or PVHVM



On 30/03/2017 17:44, James Okken wrote:
> Sorry I just hijacked that thread, I meant to change the subject before I sent!
> 
>>>>>>>
> hi all,
> 
> I have this nagging question I'm hoping someone could clear up for me. There is so much information and discussion out there regarding HVM, PVM and PVHVM it is hard to get any concrete understanding of what I'm actually using.
> 
> I thought I understood that my KVM deployment on CentOS 7.2 was creating PVM VMs.

KVM only has HVM.  PVM and PVHVM are Xen concepts.

Paolo

> Checking dmesg, lspci, lsmod of the running centos7 VMs all indications show the VMs are PVMs.
> 
> But when I look at the XML of the VMs I see: <type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>
> 
> Does that <type>hvm</type> mean I am mistaken?
> 
> Thanks
> <<<<<<
> 

  reply	other threads:[~2017-03-31 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 15:44 CentOS 7.2 HVM, PVM and/or PVHVM James Okken
2017-03-31 11:13 ` Paolo Bonzini
2017-03-31 21:20   ` James Okken [this message]
2017-04-02 19:39     ` Paolo Bonzini
2017-04-03 15:36       ` James Okken
2017-04-03 16:59         ` Paolo Bonzini
2017-04-03 17:22           ` James Okken
2017-04-03 17:26             ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR0101MB3072B3F86F4A27EF13E11FF58D370@MWHPR0101MB3072.prod.exchangelabs.com \
    --to=james.okken@dialogic.com \
    --cc=kvm-owner@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.