Re: How to create a multiple GPU passthrough offering
I see, thanks Suresh for this information. So just so I understand it correctly, at the moment, there is no support for specifying the no. of GPU that will be used by a compute offering, correct? Will this be supported in the future releases? Thanks, Irvin > On Aug 13, 2021, at 2:37 PM, Suresh Anaparti > wrote: > > There is no provision to specify GPU count through service offering. > > Regards, > Suresh > > On 13/08/21, 11:52 AM, "SVI" wrote: > >Sorry, I’m not sure I follow. So right now, my XCP-NG hypervisor detects 8 > GPU cards (Tesla K80). I added a compute offering with passthrough as > vgpuType and I was able to successfully create an instance and passthrough 1 > gpu. I was able to validate this as well in the guest VM. I was actually > hoping that in the createServiceOffering API that there’s a GPU count (just > like cpu count) so whenever I use that compute offering it will passthrough > that no. of GPU count in the guest VM. > >Thanks, >Irvin > > > > >> On Aug 13, 2021, at 1:48 PM, Suresh Anaparti >> wrote: >> >> May be, you can try this out-of-band. Check / test with the following - stop >> VM, add GPUs and start VM from the hypervisor. >> >> Regards, >> Suresh >> >> On 13/08/21, 10:31 AM, "SVI" wrote: >> >> Hi Suresh, >> >> I’m using Cloudstack 4.15.1 and XCP-NG 8.2.0 as the hypervisor host. Does >> this means that multiple GPU passthrough to 1 guest VM is not supported at >> the moment? What could be my other options here? I have a requirement for >> multiple GPUs in 1 VM that’s why I’m looking for this solution. >> >> >> Thanks, >> Irvin >> >> >> >> >>> On Aug 13, 2021, at 12:31 PM, Suresh Anaparti >>> wrote: >>> >>> Hi Irvin, >>> >>> The compute service offering in CloudStack currently supports 1 GPU >>> specification (using createServiceOffering API through >>> 'serviceofferingdetails' parameters, with the keys pciDevice and vgpuType >>> for GPU card and vGPU type respectively), and so 1 card is created for a VM. >>> >>> You can find some documentation here: >>> >>> - >>> http://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#assigning-gpu-vgpu-to-guest-vms >>> >>> - >>> http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering >>> >>> May I know the CloudStack release and Hypervisor version you are testing. >>> >>> Regards, >>> Suresh >>> >>> On 13/08/21, 7:03 AM, "SVI" wrote: >>> >>> Hi, >>> >>> I was able to create a GPU passthrough offering but at the moment it’s 1 >>> VM = 1 GPU passthrough. I have 8 GPUs in my hypervisor and technically I >>> can create 8 instance with 1 GPU passthrough each. What I want to do now is >>> to create at least 2 GPU to be passthrough 1 guest VM. I can’t see any >>> configuration or document to do that as of the moment, is there a hidden >>> API (I checked already the service offering API and doesn’t say much) that >>> is out there to do this? >>> >>> Thanks, >>> Irvin >>> >>> >>> >>> >>> >> >> > >
Re: How to create a multiple GPU passthrough offering
Correct, right now I'm not sure of the support in future releases. Regards, Suresh On 13/08/21, 12:36 PM, "SVI" wrote: I see, thanks Suresh for this information. So just so I understand it correctly, at the moment, there is no support for specifying the no. of GPU that will be used by a compute offering, correct? Will this be supported in the future releases? Thanks, Irvin > On Aug 13, 2021, at 2:37 PM, Suresh Anaparti > wrote: > > There is no provision to specify GPU count through service offering. > > Regards, > Suresh > > On 13/08/21, 11:52 AM, "SVI" wrote: > >Sorry, I’m not sure I follow. So right now, my XCP-NG hypervisor detects 8 GPU cards (Tesla K80). I added a compute offering with passthrough as vgpuType and I was able to successfully create an instance and passthrough 1 gpu. I was able to validate this as well in the guest VM. I was actually hoping that in the createServiceOffering API that there’s a GPU count (just like cpu count) so whenever I use that compute offering it will passthrough that no. of GPU count in the guest VM. > >Thanks, >Irvin > > > > >> On Aug 13, 2021, at 1:48 PM, Suresh Anaparti wrote: >> >> May be, you can try this out-of-band. Check / test with the following - stop VM, add GPUs and start VM from the hypervisor. >> >> Regards, >> Suresh >> >> On 13/08/21, 10:31 AM, "SVI" wrote: >> >> Hi Suresh, >> >> I’m using Cloudstack 4.15.1 and XCP-NG 8.2.0 as the hypervisor host. Does this means that multiple GPU passthrough to 1 guest VM is not supported at the moment? What could be my other options here? I have a requirement for multiple GPUs in 1 VM that’s why I’m looking for this solution. >> >> >> Thanks, >> Irvin >> >> >> >> >>> On Aug 13, 2021, at 12:31 PM, Suresh Anaparti wrote: >>> >>> Hi Irvin, >>> >>> The compute service offering in CloudStack currently supports 1 GPU specification (using createServiceOffering API through 'serviceofferingdetails' parameters, with the keys pciDevice and vgpuType for GPU card and vGPU type respectively), and so 1 card is created for a VM. >>> >>> You can find some documentation here: >>> >>> - http://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#assigning-gpu-vgpu-to-guest-vms >>> >>> - http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering >>> >>> May I know the CloudStack release and Hypervisor version you are testing. >>> >>> Regards, >>> Suresh >>> >>> On 13/08/21, 7:03 AM, "SVI" wrote: >>> >>> Hi, >>> >>> I was able to create a GPU passthrough offering but at the moment it’s 1 VM = 1 GPU passthrough. I have 8 GPUs in my hypervisor and technically I can create 8 instance with 1 GPU passthrough each. What I want to do now is to create at least 2 GPU to be passthrough 1 guest VM. I can’t see any configuration or document to do that as of the moment, is there a hidden API (I checked already the service offering API and doesn’t say much) that is out there to do this? >>> >>> Thanks, >>> Irvin >>> >>> >>> >>> >>> >> >> > >
Re: Not able to see Public IP Range
Hey Guys, Any help on this will be highly appreciated.! Please help if anyone ever came across the below issue. Vivek Kumar Sr. Manager - Cloud & DevOps IndiQus Technologies M +91 7503460090 www.indiqus.com > On 13-Aug-2021, at 12:26 AM, Vivek Kumar wrote: > > Hello Guys, > > So I have ACS 4.11.2 with KVM and VMware Zone. I am facing a weird issue > while clicking on public IP range - It’s showing blank. So if I go deeper and > found that some how the API - “listVlanIpRange” is not executing. It’s giving > below Error - > > > 2021-08-12 11:34:37,456 DEBUG [c.c.a.ApiServlet] > (qtp510113906-42840:ctx-40b971e9) (logid:b327c8d2) ===START=== 198.18.4.50 > -- GET > command=listVlanIpRanges&zoneid=1e830804-3d18-4cf7-b371-9cfc4574b877&networkId=a1e43fdf-3cd7-46d5-8dcc-244789ce478f&response=json&_=1628778877473 > 2021-08-12 11:34:37,458 DEBUG [c.c.c.CapacityManagerImpl] > (CapacityChecker:ctx-589c2cf2) (logid:4b339585) Found 2 VM, not running on > host 131 > 2021-08-12 11:34:37,466 DEBUG [c.c.c.CapacityManagerImpl] > (CapacityChecker:ctx-589c2cf2) (logid:4b339585) No need to calibrate cpu > capacity, host:131 usedCpuCore: 0 reservedCpuCore: 0 > 2021-08-12 11:34:37,467 DEBUG [c.c.c.CapacityManagerImpl] > (CapacityChecker:ctx-589c2cf2) (logid:4b339585) No need to calibrate cpu > capacity, host:131 usedCpu: 0 reservedCpu: 0 > 2021-08-12 11:34:37,467 DEBUG [c.c.c.CapacityManagerImpl] > (CapacityChecker:ctx-589c2cf2) (logid:4b339585) No need to calibrate memory > capacity, host:131 usedMem: 0 reservedMem: 0 > 2021-08-12 11:34:37,467 DEBUG [c.c.a.ApiServer] > (qtp510113906-42840:ctx-40b971e9 ctx-fb92ca90) (logid:b327c8d2) CIDRs from > which account 'Acct[c76bb5dd-90f1-11e8-8be7-000c29372a8b-admin]' is allowed > to perform API calls: 0.0.0.0/0,::/0 > 2021-08-12 11:34:37,500 DEBUG [c.c.c.CapacityManagerImpl] (Thread-25:null) > (logid:) Found 23 VMs on host 160 > 2021-08-12 11:34:37,525 DEBUG [c.c.c.CapacityManagerImpl] > (CapacityChecker:ctx-589c2cf2) (logid:4b339585) Found 28 VMs on host 156 > 2021-08-12 11:34:37,529 ERROR [c.c.a.ApiServer] > (qtp510113906-42840:ctx-40b971e9 ctx-fb92ca90) (logid:b327c8d2) unhandled > exception executing api command: [Ljava.lang.String;@5d1ade57 > java.lang.NullPointerException > at > com.cloud.api.ApiResponseHelper.isForSystemVms(ApiResponseHelper.java:772) > at > com.cloud.api.ApiResponseHelper.createVlanIpRangeResponse(ApiResponseHelper.java:753) > at > com.cloud.api.ApiResponseHelper.createVlanIpRangeResponse(ApiResponseHelper.java:672) > at > org.apache.cloudstack.api.command.admin.vlan.ListVlanIpRangesCmd.execute(ListVlanIpRangesCmd.java:149) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:732) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:556) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:310) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:130) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:127) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:89) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:686) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:852) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) > at > org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:190) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) > at > org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1253) > at > org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) > at > org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166) > at > org.eclipse.jetty.server.hand
Re: IPv6 dhcp problem
Op 11-08-2021 om 01:00 schreef Mustafa KALIR: Hello there, I installed Cloudstack System with Advanced Zone. And I defined IPv6. However, the centos 7 template I prepared does not pull the ipv6 information. How can i solve this problem. The below document does not work. Have you made sure your routers are sending out IPv6 Router Advertisements where they advertise the correct IPv6 /64 prefix? Wido https://docs.cloudstack.apache.org/en/latest/plugins/ipv6.html
CloudMonkey v6.2.0 Test Binaries
Hi All, The test binaries for the potential CloudMonkey v6.2.0 have been placed at https://download.cloudstack.org/testing/cmk/. It would be helpful if you'll could help in a round of testing for any issues / regression. On a high-level, some of the major changes include: * Validation of arguments while setting CloudMonkey configuration * Verifying user access to CloudMonkey configuration file * Allowing sync command to be used as a verb for CloudStack API calls * Printing response with newlines if output format chosen is "text" * Providing an option to turn-off autocompletion Please do help in testing, so that if there are any issues, we can work towards getting them fixed and releasing CloudMonkey 6.2.0. I'll cut rc1 sometime next week. Thanks for the support. Thanks & Regards, Pearl Dsilva
