similar to: CPU feature 'svm' not reported inside guest without 'host-passthrough'

Running a 3.14.4 x86-64 SMP guest kernel on qemu-2.0, with kvm enabled and -cpu host on a 3.14.4 AMD Opteron host, I'm seeing a reliable kernel panic from the guest shortly after boot. I think is happening in kvm_unlock_kick() in the paravirt_ops code: divide error: 0000 [#1] PREEMPT SMP Modules linked in: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.14.4-guest #16 Hardware name: QEMU

Running a 3.14.4 x86-64 SMP guest kernel on qemu-2.0, with kvm enabled and -cpu host on a 3.14.4 AMD Opteron host, I'm seeing a reliable kernel panic from the guest shortly after boot. I think is happening in kvm_unlock_kick() in the paravirt_ops code: divide error: 0000 [#1] PREEMPT SMP Modules linked in: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.14.4-guest #16 Hardware name: QEMU

Chris Webb <chris at arachsys.com> wrote: > My CPU flags inside the crashing guest look like this: > > fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush > mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl > extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave > avx f16c hypervisor lahf_lm

Chris Webb <chris at arachsys.com> wrote: > My CPU flags inside the crashing guest look like this: > > fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush > mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl > extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave > avx f16c hypervisor lahf_lm

On 2/17/23 12:44, Richard W.M. Jones wrote: > As with the prior commit, prefer -cpu host for all guests (except when > we have more information from the source hypervisor). Although there > is the disadvantage that -cpu host is non-migratable, in practice it > would be very difficult to live migrate a host launched using direct > qemu commands. > > Note that after this

Hi, i'm playing a bit around with vcpus. My guest is Windows 10 1903. This is the excerpt from the config: ... <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotpluggable='yes'/> <vcpu id='2'

Hello everybody, I am a new user discovering libvirt with KVM software. During my first VM creation, I saw an issue with virsh that I can't understand. I wanted to emulate another CPU than the classical qemu32 using virsh. So I used the virsh capabilites command to detect how is detected my CPU host which is an Intel Xeon E5410 and my problem is that this CPU is detected only with the

Il 29/05/2014 19:45, Chris Webb ha scritto: > Chris Webb <chris at arachsys.com> wrote: > >> My CPU flags inside the crashing guest look like this: >> >> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >> mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl >> extd_apicid pni pclmulqdq ssse3 fma cx16

On Fri, Feb 14, 2020 at 16:05:00 +0100, Lentes, Bernd wrote: > Hi, > > i'm playing a bit around with vcpus. > My guest is Windows 10 1903. > This is the excerpt from the config: > ... > <vcpu placement='static' current='2'>4</vcpu> > <vcpus> > <vcpu id='0' enabled='yes' hotpluggable='no'/> >

Hi, I have a fedora22 host and trying to use virt-install to install a fedora22 guest. The host is configured with bridge networking, using eth0 as its local interface. It appears the guest is communicating on vnet0 instead of eth0, so it can never reach the outside to download the install files. Where is vnet0 configured? Is it set by default when a bridge is created? I have one other guest on

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

On 08/03/2015 01:43 PM, Ryan Barry wrote: > Using: > > edk2.git-0-20150803.b1141.ga0973dc.x86_64 > edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch > > On Fedora 22. > > Provisioning a i440FX system in virt-manager and attempting to boot > results in successful EFI initialization, but the VM exits ungracefully > after the bootloader (with F22 and CentOS 7

Sorry to blow up everyone's email on this but I tried something new and found a different problem. I uninstalled all the debian package (libvirt, kvm, qemu, virt-manager, etc.) and then remade all the packages and installed them. Haswell again shows up in virt-manager, but now any CPU I choose including kvm64 and qemu64 give the same error: root@mal:~# virsh create

Hi, About half a year ago I installed a stock CentOS 6.0/64bit onto an Intel server to virtualize our Linux fileserver and four WinXP boxes with rdp each. Since recent times I didn't do any upgrades of the server's OS. Now I have CentOS 6.2. After an upgrade I noticed that all virtual cpu name changed to QEMU Virtual CPU version (cpu64-rhel6) The new features were 1) The ability to

On 08/03/2015 10:47 PM, Martin Kletzander wrote: > On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>> Using: >>> >>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >>> >>> On Fedora 22. >>> >>> Provisioning

Hello, All: The vignette with the sos package used "upquote.sty", required for R Journal when it was published in 2009. Current CRAN policy disallows "upquote.sty", and I've so far not found a way to pass "R CMD check" with sos without upquote.sty. I changed sos.Rnw per an email exchange with Prof. Ripley without solving the problem; see below. The

On 08/06/2015 08:08 AM, Martin Kletzander wrote: > On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >> On 08/03/2015 10:47 PM, Martin Kletzander wrote: >>> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>>> Using: >>>>> >>>>>

1. I created a virtual machine and add channel: <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/r-22-VM.agent'/> <target type='virtio' name='r-22-VM.vport'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> 2. Use

Hello, I have a domain on a host that makes it to get on a overload, i.g. host stops responding. The host is a Fedora 22 with follow packages: QEMU emulator version 2.3.0 libvirtd (libvirt) 1.2.13.1 VM is a MS Windows environment... I followed some info on libvirtd wiki but cannot get the idea to limit guest resources into libvirt or get guest limits to enforce host has priority. Must