search for: red_hat_virtualization

...ols-2.11.2-5.18.1.x86_64 qemu-vgabios-1.11.0-5.18.1.noarch qemu-block-ssh-2.11.2-5.18.1.x86_64 qemu-kvm-2.11.2-5.18.1.x86_64 qemu-2.11.2-5.18.1.x86_64 libvirt-daemon-driver-qemu-4.0.0-8.15.2.x86_64 qemu-block-rbd-2.11.2-5.18.1.x86_64 I found a table on https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/cpu_hot_plug saying that hotplugging is possible but no hotunplugging. But i don't know how recent this information is and if RedHat uses libvirt/qemu. Bernd Helmholtz Zentrum München Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundh...

On Fri, Feb 14, 2020 at 4:54 PM Lentes, Bernd < bernd.lentes@helmholtz-muenchen.de> wrote: > > qemu-kvm-2.11.2-5.18.1.x86_64 > > [...] > I found a table on > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/cpu_hot_plug > saying that hotplugging is possible but no hotunplugging. > But i don't know how recent this information is and if RedHat uses > libvirt/qemu. > > RHV uses a special version of qemu-kvm named qemu-kvm-rhev. oVirt, the upstr...

...n support using a guest >>that was originally configured for virtio only. >> >>The problem with your solution is we already have teaming and bonding >>as you said. There is already a write-up from Red Hat on how to do it >>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>That is all well and good as long as you are willing to keep around >>two VM images, one for virtio, and one for SR-IOV with live migration. > > You don't need 2 images. You need only o...

...n support using a guest >>that was originally configured for virtio only. >> >>The problem with your solution is we already have teaming and bonding >>as you said. There is already a write-up from Red Hat on how to do it >>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>That is all well and good as long as you are willing to keep around >>two VM images, one for virtio, and one for SR-IOV with live migration. > > You don't need 2 images. You need only o...

...r as virtio - virtio-net notices new NIC and starts over at enslave step above Future ideas (brainstorming): - Optimize Fast east-west by having special rules to direct east-west traffic through virtio-net traffic path Thanks for reading! Jesse [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts

...r as virtio - virtio-net notices new NIC and starts over at enslave step above Future ideas (brainstorming): - Optimize Fast east-west by having special rules to direct east-west traffic through virtio-net traffic path Thanks for reading! Jesse [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts

...ow for multi-vendor SR-IOV live migration support using a guest that was originally configured for virtio only. The problem with your solution is we already have teaming and bonding as you said. There is already a write-up from Red Hat on how to do it (https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). That is all well and good as long as you are willing to keep around two VM images, one for virtio, and one for SR-IOV with live migration. The problem is nobody wants to do that. What they want is to maintain...

...ow for multi-vendor SR-IOV live migration support using a guest that was originally configured for virtio only. The problem with your solution is we already have teaming and bonding as you said. There is already a write-up from Red Hat on how to do it (https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). That is all well and good as long as you are willing to keep around two VM images, one for virtio, and one for SR-IOV with live migration. The problem is nobody wants to do that. What they want is to maintain...

...t.com> ??? Signed-off-by: David S. Miller <davem at davemloft.net> If my understanding is correct there's no need to for any extension of virtio spec. If this is true, maybe you can start to prepare the patch? Thanks > > [1] > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts > _______________________________________________ > Virtualization mailing list > Virtualization at lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/virtualization

Hi, i'm playing a bit around with vcpus. My guest is Windows 10 1903. This is the excerpt from the config: ... <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotpluggable='yes'/> <vcpu id='2'

...est >>>that was originally configured for virtio only. >>> >>>The problem with your solution is we already have teaming and bonding >>>as you said. There is already a write-up from Red Hat on how to do it >>>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>>That is all well and good as long as you are willing to keep around >>>two VM images, one for virtio, and one for SR-IOV with live migration. >> >> You don't need 2 images....

...a compatible guest OS (see link below). So, in my customer's mind, CentOS cannot be used as a guest OS in RHV cause it is not compatible, which I find it hard to believe considering the relationship between CentOs and RHEL. RHV supported guest OS https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/virtual_machine_management_guide/#Supported_virtual_machines VMware compatible guest OS https://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf So, my question is, technically, can CentOS run as a guest OS on RHV4? Is there anyone that has done extensiv...

...that was originally configured for virtio only. >>>> >>>>The problem with your solution is we already have teaming and bonding >>>>as you said. There is already a write-up from Red Hat on how to do it >>>>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>>>That is all well and good as long as you are willing to keep around >>>>two VM images, one for virtio, and one for SR-IOV with live migration. >>> >>> You don'...

...that was originally configured for virtio only. >>>> >>>>The problem with your solution is we already have teaming and bonding >>>>as you said. There is already a write-up from Red Hat on how to do it >>>>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>>>That is all well and good as long as you are willing to keep around >>>>two VM images, one for virtio, and one for SR-IOV with live migration. >>> >>> You don'...

...SR-IOV live migration support using a guest >that was originally configured for virtio only. > >The problem with your solution is we already have teaming and bonding >as you said. There is already a write-up from Red Hat on how to do it >(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >That is all well and good as long as you are willing to keep around >two VM images, one for virtio, and one for SR-IOV with live migration. You don't need 2 images. You need only one. The one with...

...lly configured for virtio only. >>>>> >>>>>The problem with your solution is we already have teaming and bonding >>>>>as you said. There is already a write-up from Red Hat on how to do it >>>>>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>>>>That is all well and good as long as you are willing to keep around >>>>>two VM images, one for virtio, and one for SR-IOV with live migration. >>>> >>>&...

...or virtio only. >>>>>> >>>>>>The problem with your solution is we already have teaming and bonding >>>>>>as you said. There is already a write-up from Red Hat on how to do it >>>>>>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>>>>>That is all well and good as long as you are willing to keep around >>>>>>two VM images, one for virtio, and one for SR-IOV with live migration. >>>>> &...

...or virtio only. >>>>>> >>>>>>The problem with your solution is we already have teaming and bonding >>>>>>as you said. There is already a write-up from Red Hat on how to do it >>>>>>(https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts). >>>>>>That is all well and good as long as you are willing to keep around >>>>>>two VM images, one for virtio, and one for SR-IOV with live migration. >>>>> &...

...lt;davem at davemloft.net> > > If my understanding is correct there's no need to for any extension of > virtio spec. If this is true, maybe you can start to prepare the patch? > > Thanks > >> >> [1] >> >> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts >> _______________________________________________ >> Virtualization mailing list >> Virtualization at lists.linux-foundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/vir...

...lt;davem at davemloft.net> > > If my understanding is correct there's no need to for any extension of > virtio spec. If this is true, maybe you can start to prepare the patch? > > Thanks > >> >> [1] >> >> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts >> _______________________________________________ >> Virtualization mailing list >> Virtualization at lists.linux-foundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/vir...