xlmnxp commented on PR #5012:
URL: https://github.com/apache/cloudstack/pull/5012#issuecomment-1129767043

   > @xlmnxp, can you share the libvirt/qemu versions and the OS? Also, do you 
use advanced virtualization? I had the same problem on Rocky with the advanced 
virtualization, and there is a fix which will be included in CS versions - 
4.16.2.0 and 4.17. [Reported 
issue](https://github.com/apache/cloudstack/issues/6252)
   
   > I indeed think this is due to the OS. Without knowing the OS and Qemu 
version we can't tell the root cause.
   
   OS: `Rocky Linux 8.6 (Green Obsidian)`
   Libvirt: `libvirtd (libvirt) 8.0.0`
   
   
   ----
   
   > as @slavkap said, https://github.com/apache/cloudstack/pull/6253 
introduced a new config enable.io.uring in agent.properties.
   it will be included in upcoming 4.17.0.0.
   if you use latest libvirt, https://github.com/apache/cloudstack/pull/6244 is 
also required which will be included in 4.17.0.0 as well.
   
   I already disabled it in agent config but the router didn't start because of 
is_uring which I disabled
   
   `/etc/cloudstack/agent/agent.properties`: 
   ```
   #Storage
   #Wed May 18 05:08:47 EDT 2022
   cluster=1
   pod=1
   resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
   private.network.device=cloudbr0
   domr.scripts.dir=scripts/network/domr/kvm
   guest.cpu.mode=host-passthrough
   router.aggregation.command.each.timeout=600
   guest.network.device=cloudbr0
   enable.io.uring=false
   keystore.passphrase=EaPsawRuTKRF7km3
   hypervisor.type=kvm
   port=8250
   zone=1
   public.network.device=cloudbr0
   local.storage.uuid=ca0e32d1-a818-49fb-bf4d-9e73aef1f19e
   host=192.168.8.4@static
   guid=28e45ca9-ac69-3278-8703-3e81566b0575
   LibvirtComputingResource.id=1
   workers=5
   iscsi.session.cleanup.enabled=false
   vm.migrate.wait=3600
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to