On Tue, 2021-02-09 at 08:03 +0200, Tzvetomir Stoyanov wrote: > Hi Dario, > Hi! > On Tue, Feb 9, 2021 at 7:32 AM Dario Faggioli <dfaggioli@xxxxxxxx> > wrote: > > > > If necessary, I can provide more info about my setup, or do more > > tests. > > There are a few limitations that we are working to address: > 1. Ensure that vhost_vsock module is loaded on the host. > 2. You should add a vsock device manually to your VM config, I use > "virsh edit <vm name>" to add: > <vsock model='virtio'> > <cid auto='yes'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x09' > function='0x0'/> > </vsock> > somewhere in the <devices> </devices> section. > Yep, these are both fine. In fact, I tested host<-->guest communication via vsock independently, and it works, so it does not seem a vsock issue... I also try without the series applied (but keeping patch 2) and it still fails in the same way. FTR, in the past, I've used trace-cmd from git with an earlier version of this series applied (the "KVM clock" wasn't there yet) on the same environment I'm using now, and it worked. Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
Attachment:
signature.asc
Description: This is a digitally signed message part
|