Closed talcoh2x closed 2 years ago
Hi, could you please share the VMI manifest you used on both versions?
"spec": {
"domain": {
"cpu": {
"cores": 26,
"dedicatedCpuPlacement": true,
"model": "host-passthrough",
"numa": {
"guestMappingPassthrough": {}
},
"sockets": 2,
"threads": 2
},
"devices": {
"blockMultiQueue": true,
"disks": [
{
"dedicatedIOThread": true,
"disk": {
"bus": "virtio"
},
"name": "localdisk"
},
{
"disk": {
"bus": "virtio"
},
"name": "cloud-init"
}
],
"filesystems": [
{
"name": "disk0",
"virtiofs": {}
}
],
"gpus": [
{
"deviceName": "habana.ai/gaudi",
"name": "gpu0"
},
{
"deviceName": "habana.ai/gaudi",
"name": "gpu1"
},
{
"deviceName": "habana.ai/gaudi",
"name": "gpu2"
},
{
"deviceName": "habana.ai/gaudi",
"name": "gpu3"
}
],
"interfaces": [
{
"name": "sriov-net",
"sriov": {}
}
],
"networkInterfaceMultiqueue": true
},
"features": {
"acpi": {
"enabled": true
}
},
"firmware": {
"uuid": "5df412aa-4bc4-5676-8e19-b8bf6fc5606e"
},
"ioThreadsPolicy": "auto",
"machine": {
"type": "q35"
},
"memory": {
"guest": "630Gi",
"hugepages": {
"pageSize": "2Mi"
}
},
"resources": {
"requests": {
"memory": "660Gi"
}
}
},
"networks": [
{
"multus": {
"networkName": "habana/sriov-net"
},
"name": "sriov-net"
}
],
"nodeSelector": {
"habana.ai/qa.nightly": "false",
"habana.ai/schedulable": "true"
},
"terminationGracePeriodSeconds": 0,
"volumes": [
{
"name": "localdisk",
"persistentVolumeClaim": {
"claimName": "dpitossi-habana-i3uw-pvc"
}
},
{
"name": "disk0",
"persistentVolumeClaim": {
"claimName": "ccache-volume-pvc"
}
},
{
"cloudInitNoCloud": {
"userData": "#cloud-config\nhostname: i-habana-i3uw-vm\nruncmd:\n- [sudo, mount, -a]\n- [wget, -O, \"/etc/auto.home\" ,\"https://atofs/auto.home\"]\n- [sudo, systemctl, restart, autofs.service]"
},
"name": "cloud-init"
}
]
},
@ormergi
@talcoh2x I am not sure why it doesnt appear on the system you work with, could you please try with kubectl get vmi <name> -o yaml
?
@talcoh2x I think that the problem you are seeing originates from the fact that the guest-agent is not active in the guest (or there is a problem with communicating to it).
Currently, SR-IOV interfaces are reported only by the guest-agent. But work is undergoing to resolve this. See #7050 for more information.
Try to confirm the guest-agent is active and let us know if it got resolved.
/assign EdDev
@talcoh2x , we are closing this issue. You are welcome to re-open it when you have more info.
/close
@EdDev: Closing this issue.
on Kubevirt 0.46 status.interface does not appear and show me only "name": sriov i can tell you that on release version 0.43 and 0.45.1 all is working fine.
BUG REPORT:
What happened: status.interface is missing and include only "name"
What you expected to happen: I expect to see status.interface info
How to reproduce it (as minimally and precisely as possible): install Kubevirt 0.46 create VMI + SRIOV network interface and run "describe vmi"
0.46
0.45.1
Anything else we need to know?:
Environment:
virtctl version
):kubectl version
):uname -a
):