You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Piotr Pisz <pi...@piszki.pl> on 2021/05/10 11:53:03 UTC
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
Re: vm os profile - e1000
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi Piotr,
vSphere7 (ESXi7) does not work on qemu yet, the vmxnet3 nic controller is buggy. If you're on Ubuntu 20.04 or equivalent distro, you can try using https://github.com/shapeblue/mbx or its host templates manually.
In my Ubuntu 20.04 I'm able to deploy VMware 6.5, 6.7, and other KVM/XenSever/XCP-ng hypervisors using mbx. My virsh/qemu/libvirt versions are:
# virsh version
Compiled against library: libvirt 6.0.0
Using library: libvirt 6.0.0
Using API: QEMU 6.0.0
Running hypervisor: QEMU 4.2.1
Regards.
________________________________
From: Piotr Pisz <pi...@piszki.pl>
Sent: Monday, May 10, 2021 18:44
To: Nicolas Vazquez <Ni...@shapeblue.com>; users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: vm os profile - e1000
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 <Ni...@shapeblue.com>
Sent: Monday, May 10, 2021 2:36 PM
To: users@cloudstack.apache.org; piotr@piszki.pl
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 <piotr@piszki.pl <ma...@piszki.pl> >
Sent: Monday, May 10, 2021 8:53 AM
To: users@cloudstack.apache.org <ma...@cloudstack.apache.org>
<users@cloudstack.apache.org <ma...@cloudstack.apache.org> >
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
RE: vm os profile - e1000
Posted by Piotr Pisz <pi...@piszki.pl>.
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 <Ni...@shapeblue.com>
Sent: Monday, May 10, 2021 2:36 PM
To: users@cloudstack.apache.org; piotr@piszki.pl
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 <piotr@piszki.pl <ma...@piszki.pl> >
Sent: Monday, May 10, 2021 8:53 AM
To: users@cloudstack.apache.org <ma...@cloudstack.apache.org>
<users@cloudstack.apache.org <ma...@cloudstack.apache.org> >
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
Re: vm os profile - e1000
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
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 <pi...@piszki.pl>
Sent: Monday, May 10, 2021 8:53 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
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