Hi Nicolas,
The problem is that I can set the network card to e1000 this way, but for vmxnet3 I have something like this: Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: qemu-kvm: -device vmxnet3,netdev=hostnet0,id=net0,mac=02:00:39:99:00:03,bus=pci.0,addr=0x3: 'vmxnet3' is not a valid device model name","wait":"0"}}] } qemu-kvm-ev-2.12.0-33.1.el7_7.4 CS 4.15 Regards, Piotr From: Nicolas Vazquez <[email protected]> Sent: Monday, May 10, 2021 2:36 PM To: [email protected]; [email protected] Subject: Re: vm os profile - e1000 Hi Piotr, I have had the same issue with ESX 7 vms and needed to set the NIC device model to: vmxnet3. Let me know if that helps Regards, Nicolas Vazquez _____ From: Piotr Pisz <[email protected] <mailto:[email protected]> > Sent: Monday, May 10, 2021 8:53 AM To: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > Subject: vm os profile - e1000 Hi, I'm trying to run a nested ESXi in Cloudstack. Generally there is no problem with this with one exception, I don't know what Os profile to use to get the e1000 NIC in the VM. ESXi claims that no network is connected. I am using KVM under CentOS 7 control. Does anyone have any experience in this topic? Regards, Piotr
