Hi Vitaly, On Mon, Jan 28, 2019 at 12:02 PM Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> wrote: > > Diego Viola <diego.viola@xxxxxxxxx> writes: > > > Hi Vitaly, > > > > On Fri, Jan 25, 2019 at 12:32 PM Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> wrote: > >> > >> Diego Viola <diego.viola@xxxxxxxxx> writes: > >> > >> > Hello, > >> > > >> > I am trying to do nested KVM on a Ryzen 5 2400G, my use case is the following: > >> > > >> > - Arch Linux as the host OS. > >> > - Ubuntu 18.04.1 as the guest OS. > >> > > >> > I am using qemu 3.1.0-1 (from the extra repository) on Arch Linux. > >> > > >> > This is the command I am using to start the VM: > >> > > >> > qemu-system-x86_64 -enable-kvm -hda ubuntu.qcow2 -m 4G -smp 4 -vga > >> > virtio -cpu host > >> > >> Could you please try if the following patch helps? > >> > >> https://www.spinics.net/lists/kvm/msg179946.html > >> > >> (actually, this looks more like > >> https://www.spinics.net/lists/kvm/msg179297.html but your 4.20.3 should > >> have it already) > > > > Yes, I checked and 4.20.3 already has the second patch. > > > > Do you have another patch you want me to test? > > > > You can still try the first one I mentioned (or, better, just try > upstream 5.0-rc4). Other than that I can suggest trying to disabling > different CPU features on the host (e.g. '-cpu host,-npt,-nrip_save') to > see if the issue goes away. I am still getting the same issue with kernel 5.0.0-rc4. Here's the dmesg with kernel 5.0.0-rc4 after I run the VM and run snapcraft: https://ptpb.pw/_RKJ The command I am using: qemu-system-x86_64 -enable-kvm -hda ubuntu.qcow2 -m 4G -cpu host -smp 4 -vga virtio I tried -cpu host,-npt,-nrip_save with kernel 4.20.4 and 5.0.0-rc4 and it results in snapcraft timing out but no stacktrace on the host's dmesg. > > -- > Vitaly Thanks, Diego
