On Wed, May 11, 2016 at 07:30:45PM -0400, Emilien Macchi wrote:
:On Tue, May 3, 2016 at 11:43 AM, Matt Riedemann
: wrote:
:> Another thought is that deployment tools are just copying what devstack
:> does, or what shows up in the configs in our dsvm gate jobs, and
On Tue, May 3, 2016 at 11:43 AM, Matt Riedemann
wrote:
> On 5/3/2016 10:01 AM, Daniel P. Berrange wrote:
>>
>> Hello Operators,
>>
>> One of the things that constantly puzzles me when reading the user
>> survey results wrt hypervisor is the high number of respondants
On 11 May 2016 at 14:32, Maish Saidel-Keesing wrote:
>
> On 11/05/16 22:18, Chris Friesen wrote:
>
> On 05/11/2016 11:46 AM, Ronald Bradford wrote:
>
> I have been curious as to why as mentioned in the thread virt_type=kvm,
> but
> os-hypervisors API call states QEMU.
>
>
>
On 05/11/2016 01:29 PM, Robert Starmer wrote:
I don't disagree, what we're really getting at is that any lookup (ask the
system what it's using on a particular instance, look at the config, look at the
output of a nova CLI request, querry via Horizon), should all return the same
answer. So one
On 11/05/16 22:18, Chris Friesen wrote:
> On 05/11/2016 11:46 AM, Ronald Bradford wrote:
>> I have been curious as to why as mentioned in the thread
>> virt_type=kvm, but
>> os-hypervisors API call states QEMU.
>
> Arguably in both cases the hypervisor is qemu. When virt_type=kvm we
> simply
I don't disagree, what we're really getting at is that any lookup (ask the
system what it's using on a particular instance, look at the config, look
at the output of a nova CLI request, querry via Horizon), should all return
the same answer. So one is a bug (Horizon), the other requires looking
Or we could just fix the problem within OpenStack to report the correct
Hypervisor in the first place.
This kind of reminds me of a story.
Someone was trying to drive down a path on his bicycle, but there were
some tacks on the path.
So his wheel kept on getting full of holes. So they thought
On 05/11/2016 11:46 AM, Ronald Bradford wrote:
I have been curious as to why as mentioned in the thread virt_type=kvm, but
os-hypervisors API call states QEMU.
Arguably in both cases the hypervisor is qemu. When virt_type=kvm we simply
enable some additional acceleration.
So rather than
You could just ask for the value of virt_type parameter from a compute host
(or the output of something like grep 'virt_type' /etc/nova/nova*) if you
are using qemu or kvm. I believe that's how nova figures out what
parameters to use when launching an instance.
On Wed, May 11, 2016 at 8:39 AM,
In the next user survey - could we clarify that qemu == full software cpu
emulation and kvm (qemu/kvm) = hardware accelerated virtualization or some
similar phrasing. It's totally possible that people are like: I run both qemu
and kvm (thinking that’s qemu/kvm) - when in fact they only run kvm
Does anyone see a good way to fix this to report KVM or QEMU/KVM ?
I guess the worry is whether this would count as a bug fix or an incompatible
change.
Tim
On 11/05/16 17:51, "Kashyap Chamarthy" wrote:
>On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes
I have been curious as to why as mentioned in the thread virt_type=kvm, but
os-hypervisors API call states QEMU.
Interestingly this command mentioned (which works on Ubuntu) gives me a
FAIL and WARN on my home test setup that runs on physical H/W.
$ virt-host-validate
QEMU: Checking for
Which still brings me back to the original point.
Is this a bug - and should it be reported as such?
On 11/05/16 18:51, Kashyap Chamarthy wrote:
> On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote:
>
> [...]
>
>> I'm confused too about the use of KVM or QEMU In the computes
On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote:
[...]
> I'm confused too about the use of KVM or QEMU In the computes the
> file/etc/nova/nova-compute.conf has:
>
> virt_type=kvm
>
> The output of:
>
> nova hypervisor-show | grep hypervisor_type
>
> is:
>
>
On Tue, May 03, 2016 at 07:06:56PM +, Jared Wilkinson wrote:
> So forgive my lack of kvm/qemu knowledge but I couldn’t find anything
> on Google on this. If you deployed an instance of a different architecture
> than the physical CPU, wouldn’t qemu just emulate the processor (if you
> were in
On Tue, May 03, 2016 at 10:20:34PM +0300, Maish Saidel-Keesing wrote:
> I would think that the problem is that OpenStack does not really report
> back that you are using KVM - it reports that you are using QEMU.
>
> Even when in nova.conf I have configured virt_type=kvm, when I run nova
>
On 3 May 2016 at 10:01, Daniel P. Berrange wrote:
> Hello Operators,
>
> One of the things that constantly puzzles me when reading the user
> survey results wrt hypervisor is the high number of respondants
> claiming to be using QEMU (as distinct from KVM).
>
> As a
what you should be looking for is hvm.
On Tue, May 3, 2016 at 3:20 PM, Maish Saidel-Keesing
wrote:
> I would think that the problem is that OpenStack does not really report
> back that you are using KVM - it reports that you are using QEMU.
>
> Even when in nova.conf I have
I would think that the problem is that OpenStack does not really report
back that you are using KVM - it reports that you are using QEMU.
Even when in nova.conf I have configured virt_type=kvm, when I run nova
hypervisor-show XXX | grep hypervisor_type
I am presented with the following
|
So forgive my lack of kvm/qemu knowledge but I couldn’t find anything on Google
on this. If you deployed an instance of a different architecture than the
physical CPU, wouldn’t qemu just emulate the processor (if you were in
virt_type=kvm) mode, or would libvirt throw some error?
Thanks,
Jared
On 5/3/2016 10:01 AM, Daniel P. Berrange wrote:
Hello Operators,
One of the things that constantly puzzles me when reading the user
survey results wrt hypervisor is the high number of respondants
claiming to be using QEMU (as distinct from KVM).
As a reminder, in Nova saying virt_type=qemu
The only reason I can think of is that they are doing nested VMs and don't
have the right nesting flag enabled in their base flag.
On Tue, May 3, 2016 at 9:01 AM, Daniel P. Berrange
wrote:
> Hello Operators,
>
> One of the things that constantly puzzles me when reading the
Hello Operators,
One of the things that constantly puzzles me when reading the user
survey results wrt hypervisor is the high number of respondants
claiming to be using QEMU (as distinct from KVM).
As a reminder, in Nova saying virt_type=qemu causes Nova to use
plain QEMU with pure CPU emulation
23 matches
Mail list logo