Re: [ovirt-users] Failed to migrate a VMware through virt-v2v included in oVirt 3.6
Can you please provide us the VDSM log which includes the v2v error message? According to your information, it's hard to know where the issue begins: 1. Add external provider: are you using "Any data center" or specific data center in the "data center" dropbox? There is a bug related to it when using "any data center" (https://bugzilla.redhat.com/show_bug.cgi?id=1293591 - v2v: external provider "test" button failed when using "any data center" value.) 2. vSphere Client Version 5.1.0: We have tested VMware migrate from vSphere 5.5 and above. 3. can´t parse the Cluster data: there are also some known bugs on this issue, so either you can upgrade your libvirt and libguestfs build (fixed from libvirt-1.3.1-1.el7 and libguestfs-1.32.2-2.el7) or move VMware source VM to be directly under the data center. Bugs related to this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1263574 - vpx: Include dcpath output in libvirt XML https://bugzilla.redhat.com/show_bug.cgi?id=1292437 - Backport virt-v2v pull dcpath from libvirt Thanks Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 - Original Message - | From: "Julián Tete" <danteconra...@gmail.com> | To: "Nisim Simsolo" <nsims...@redhat.com> | Cc: users@ovirt.org | Sent: Wednesday, March 30, 2016 11:13:04 PM | Subject: Re: [ovirt-users] Failed to migrate a VMware through virt-v2v included in oVirt 3.6 | | *VMware:*srvesx01 VMware ESXi 5.1.0, 2191751 | | vSphere Client Version 5.1.0 | | VMware vCenter Server Version 5.1.0 | | | *My oVirt DataCenter:* | | Version 3.6.1.3-1.el7.centos | | *Cluster:* | | Compatibility Version: 3.6 | | Cluster CPU Type: Intel SandyBridge Family | | Emulated Machine: pc-i440fx-rhel7.2.0 | | *Host:* | | SELinux mode: Permissive | | OS Version: RHEL - 7 - 2.1511.el7.centos.2.10 | | Kernel Version: 4.3.0 - 1.el7.elrepo.x86_64 | | KVM Version: 2.3.0 - 31.el7_2.3.1 | | LIBVIRT Version: libvirt-1.2.17-13.el7_2.2 | | VDSM Version: vdsm-4.17.13-0.el7.centos | | SPICE Version: 0.12.4 - 15.el7 | | CEPH Version: librbd1-0.80.7-3.el7 | | Manufacturer: HP | | CPU Model: Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz | | CPU Cores per Socket: 8 | | Family: ProLiant | | CPU Type: Intel SandyBridge Family | | CPU Threads per Core: 2 (SMT Enabled) | | Product Name: ProLiant BL460c Gen8 | | CPU Sockets: 2 | | rpm -qa | grep virt-v2v | | virt-v2v-1.28.1-1.55.el7.centos.x86_64 | | rpm -qa | grep libguestfs-winsupport | | libguestfs-winsupport-7.2-1.el7.x86_64 | | # | | R// | | Yes, I installed virt-v2v in all hosts of the Cluster and in the Engine :P | | The S.O of the machine to migrate is CentOS 6.6 | | When I try to use the GUI to add a External Provider (VMware) I get the | error message: | | *Failed to retrieve VMs information from external server | vpx://192.168.0.129/CNSCDatacenter/srvesx01?no_verify=1 | <http://192.168.0.129/CNSCDatacenter/srvesx01?no_verify=1>* | | But when I use the command: | | virsh -c vpx:// | Administrator@192.168.0.129/CNSCDatacenter/Cluster_CNSC/srvesx01?no_verify=1 | | I can connect to VMware. | | I can´t parse the Cluster data (Cluster_CNSC) in the GUI to add a External | Provider (VMware) | | :/ | | Thanks in advance | | | 2016-03-30 3:23 GMT-05:00 Nisim Simsolo <nsims...@redhat.com>: | | > Hi | > | > Can you please give more details: | > Did you install virt-v2v on the host? | > What kind of VM OS did you try to migrate? | > What is the failure you see? | > | > Thanks | > | > | > Nisim Simsolo | > QE -Testing Engineer | > IRC: nsimsolo | > int phone - 8272305 | > mobile - 054-4779934 | > | > - Original Message - | > | From: "Julián Tete" <danteconra...@gmail.com> | > | To: users@ovirt.org | > | Sent: Wednesday, March 30, 2016 2:10:32 AM | > | Subject: [ovirt-users] Failed to migrate a VMware through virt-v2v | > included in oVirt 3.6 | > | | > | My oVirt DataCenter | > | | > | Cluster CPU Type: Intel SandyBridge Family | > | | > | Emulated Machine: pc-i440fx-rhel7.2.0 | > | | > | | > | | > | | > | ___ | > | Users mailing list | > | Users@ovirt.org | > | http://lists.ovirt.org/mailman/listinfo/users | > | | > | ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Problems With VMWare Import
Hi Can you please try do delete source VMware VM snapshot and then try to import it? There is known issue for importing VMware VM with snapshot: https://bugzilla.redhat.com/show_bug.cgi?id=1172425 - [RFE]virt-v2v failed to convert VMware ESX VM with snapshot Thanks Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 - Original Message - | From: "Charles Tassell" <ctass...@gmail.com> | To: "users" <users@ovirt.org> | Sent: Wednesday, March 30, 2016 9:53:10 PM | Subject: [ovirt-users] Problems With VMWare Import | | Hi Everyone, | |This doesn't seem to be a bug in oVirt so much as in the | libvirt/virt-v2v tool it uses for importing, but I figured someone here | might have run into this issue before. I'm trying to import some VMs | from my VMWare cluster and it's failing with a "file not found" when | trying to download the disk images. I have files in the datastore like: | | systest-55-01-delta.vmdk4G | systest-55-01.vmdk 1K | systest-55-Snapshot1.vmsn4G | systest-55-flat.vmdk 40G | systest-55.vmdk 1K | ... bunch more small .vm?? files | | For some reason virt-v2v is trying to download a file called | systest-55-01-flat.vmdk which doesn't exist. I'm assuming this has | something to do with the snapshots stored in the folder... Does anyone | know a way to deal with that? Can I just delete the snapshots or is | that going to delete data stored on the VM since the last snapshot? I'm | using virt-v2v 1.28.1 if that makes a difference. | | ___ | Users mailing list | Users@ovirt.org | http://lists.ovirt.org/mailman/listinfo/users | ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Failed to migrate a VMware through virt-v2v included in oVirt 3.6
Hi Can you please give more details: Did you install virt-v2v on the host? What kind of VM OS did you try to migrate? What is the failure you see? Thanks Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 - Original Message - | From: "Julián Tete" <danteconra...@gmail.com> | To: users@ovirt.org | Sent: Wednesday, March 30, 2016 2:10:32 AM | Subject: [ovirt-users] Failed to migrate a VMware through virt-v2v included in oVirt 3.6 | | My oVirt DataCenter | | Cluster CPU Type: Intel SandyBridge Family | | Emulated Machine: pc-i440fx-rhel7.2.0 | | | | | ___ | Users mailing list | Users@ovirt.org | http://lists.ovirt.org/mailman/listinfo/users | ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] USB
Hi You can attach host device directly from virtual machines tab -> select VM -> host devices sub tab -> "add device" button. But first you need to verify your BIOS is supporting intel VT-d or AMD vi. And you also need to activate it in the kernel. The next link describes how to do it: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/chap-Guest_virtual_machine_device_configuration.html#sect-Guest_virtual_machine_device_configuration-PCI_devices note: Instead of adding "intel_iommu=pt" in the grub cmdline, add "intel_iommu=on" or "amd_iommu=on". Another thing worth mentioning, USB hotplug is not supported yet, so if your programmable device is resetting the USB connection each time you program it, the USB will be detached from the VM and you will have to attach it again in order to see it. On Sun, May 15, 2016 at 8:34 AM, Brett I. Holcomb <biholc...@l1049h.com> wrote: > How do I get a VM to see USB devices? If I understand it correctly I > have to go to Edit VM -> Console and enable USB native. I have the > console options set to use usb. However, I'm finding conflicting > information. Supposedly libvirt will allow sharing of a USB device > over a network but to start with I'd be happy just being able to > connect a usb device to the host and having it detected. I have some > programmable devices I'd like to program in Linux using my VM. > > Has anyone uses usbip and if so how well does it work? > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Re: vender_id syntax UserDefinedVMProperties
Hi
Vendor ID of Nvidia is usually 10de.
You can locate 'vendor ID:product ID' by running lspci command, for example:
[root@intel-vfio ~]# lspci -Dnn | grep -i nvidia
:03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL
[Quadro K4200] [10de:11b4] (rev a1)
:03:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio
Controller [10de:0e0a] (rev a1)
[root@intel-vfio ~]#
In this example, the vendor ID of VGA controller is 10de and the product ID
is 11b4
Please bare in mind that you need to enable IOMMU, add pci-stub (prevent
the host driver for using GPU device) and disable the default nouveau
driver on the host Kernel command line.
to do that:
1. Edit host /etc/sysconfig/grub and add the next to GRUB_CMDLINE_LINUX:
- intel_iommu=on or amd_iommu=on
- pci-stub.ids=10de:11b4,10de:0e0a
- rdblacklist=nouveau
2. Regenerate the boot loader configuration using grub2-mkconfig command:
# grub2-mkconfig -o /etc/grub2.cfg
3. Reboot the host.
4. Verify configuration:
[root@intel-vfio ~]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64 root=/dev/mapper/vg0-lv_root
ro crashkernel=auto rd.lvm.lv=vg0/lv_root rd.lvm.lv=vg0/lv_swap rhgb quiet
pci-stub.ids=10de:11b4,10de:0e0a intel_iommu=on rdblacklist=nouveau
LANG=en_US.UTF-8
[root@intel-vfio ~]#
After running this, you should be able to passthrough GPU to VM.
BTW, why are you using engine-config and not doing it from oVirt UI or
using virsh edit command?
Thanks
On Mon, Mar 18, 2019 at 1:52 AM Darin Schmidt
wrote:
> Hello all, im trying to figure out how to configure the custom properties
> to enable my NVIDIA card to work in the VM. Its my understanding that the
> drives dont work because it detects its in a VM..
>
> Im trying to do something like this:
>
> engine-config -s
> UserDefinedVMProperties="kvmhidden=^(true|false)$;{type=vendor_id;state={^(on|off)$;value=^([0-9])$}}"
>
>
> But thats clearly not working. If I do this:
>
> engine-config -s
> UserDefinedVMProperties="kvmhidden=^(true|false)$;vendor_id={state=^(on|off)$;value=^([0-9])$}"
>
>
> It works but, the options are messed up. Im not sure how to find out the
> correct syntax to get this to work. Would appreciate any advice.
>
--
Nisim Simsolo
QE -Testing Engineer
IRC: nsimsolo
int phone - 8272305
mobile - 054-4779934
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3VN26COJRRIF7CGKY6DU5CURMQOK6X2Y/
[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC
Do you have any other Windows ISO (not necessarily Windows 10) to check in order to see if it's not an issue with the ISO file? On Tue, Feb 5, 2019 at 2:52 PM Darin Schmidt wrote: > I dont even get to that point. The VM seems to detect the windows.iso I > downloaded from MS, the windows icon shows up, then it sits there for a > while, then I get the error in the picture I attached complaining about a > Sytem Thread Exception Not Handled. I dont make it to the install process > for windows. > > On Tue, Feb 5, 2019 at 7:46 AM Nisim Simsolo wrote: > >> Hi >> >> If it's not Hyper-V SynIC issue, then it might be related to the disk >> interface. >> By default, the disk interface is VirtIO and Windows cannot see this >> interface until you intall VirtIO-Win disk driver. >> In order to do that, make sure you have VirtIO-Win.ISO in the ISO domain >> and during the Windows installation, when it's asking for disk location, >> change the VM CD to virtio-win.iso >> Click on "browse drivers" in the Windows installation window and install >> viostor from the ISO file. >> after the driver is installed, change the VM CD back to the Windows ISO >> -> refresh and continue the Windows installation. >> >> Please let me know if you still have issues. >> >> Thanks >> >> >> >> On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt >> wrote: >> >>> Thanks, that sort of helped. I've ran yum update a dozen times and not >>> till this morning was there a kernel update... lol >>> >>> I'm able to startup the VM, but when it loads the ISO to install Windows >>> 10 which I downloaded from Microsoft, Attached is what always happens. >>> Perhaps my ISO is corrupt? >>> >>> On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler >>> wrote: >>> >>>> On Fri, 1 Feb 2019 17:37:30 -0500 >>>> Darin Schmidt wrote: >>>> >>>> > [root@ovirt ~]# rpm -qa kernel >>>> > kernel-3.10.0-957.1.3.el7.x86_64 >>>> > kernel-3.10.0-862.el7.x86_64 >>>> > [root@ovirt ~]# uname -a >>>> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC >>>> 2018 >>>> >>>> https://bugzilla.redhat.com/1638835 looks like there is at least >>>> kernel 3.10.0-957.3.1.el7.x86_64 required. >>>> Can you please check if upgrading to kernel solves the issue for you? >>>> I expectect at least kernel 3.10.0-957.5.1 to be availible. >>>> >>>> > x86_64 x86_64 x86_64 GNU/Linux >>>> > [root@ovirt ~]# rpm -qa qemu-kvm-ev >>>> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 >>>> > [root@ovirt ~]# rpm -qa libvirt >>>> > libvirt-4.5.0-10.el7_6.3.x86_64 >>>> >>>> > here is the vdsm >>>> > >>>> >>>> contains: >>>> Hyper-V SynIC is not supported by kernel >>>> >>>> >>>> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler >>>> > wrote: >>>> > >>>> > > On Fri, 1 Feb 2019 11:48:51 -0500 >>>> > > Darin Schmidt wrote: >>>> > > >>>> > > > I have successfully setup a centos vm, its up and running. Now I >>>> > > > need to setup a windows 10 VM and I cant seem to get anything to >>>> > > > work. >>>> > > > >>>> > > > Ive tried setting the OS type to other or Windows 10 64bit. With >>>> > > > Windows 64bit, it fails to startup at all When I select >>>> > > > OtherOS it will allow me to start to run the Windows ISO, but >>>> > > > then fails after a few seconds as well. Is there something I'm >>>> > > > not correctly configuring? >>>> > > >>>> > > Would you please share vdsm.log, and the output of >>>> > > rpm -qa kernel >>>> > > uname -a >>>> > > rpm -qa qemu-kvm-ev >>>> > > rpm -qa libvirt >>>> > > from of the host, and the relevant part of engine.log? >>>> > > >>>> >>>> ___ >>> Users mailing list -- users@ovirt.org >>> To unsubscribe send an email to users-le...@ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BYIZ36LEPVD5FAD77L7FSDBHN2TZD4SD/ >>> >> >> >> -- >> Nisim Simsolo >> QE -Testing Engineer >> IRC: nsimsolo >> int phone - 8272305 >> mobile - 054-4779934 >> > -- Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XXBBLAI2W4UYAFMGA2YUWDU5FNNKETJ6/
[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC
Hi If it's not Hyper-V SynIC issue, then it might be related to the disk interface. By default, the disk interface is VirtIO and Windows cannot see this interface until you intall VirtIO-Win disk driver. In order to do that, make sure you have VirtIO-Win.ISO in the ISO domain and during the Windows installation, when it's asking for disk location, change the VM CD to virtio-win.iso Click on "browse drivers" in the Windows installation window and install viostor from the ISO file. after the driver is installed, change the VM CD back to the Windows ISO -> refresh and continue the Windows installation. Please let me know if you still have issues. Thanks On Sat, Feb 2, 2019 at 5:22 PM Darin Schmidt wrote: > Thanks, that sort of helped. I've ran yum update a dozen times and not > till this morning was there a kernel update... lol > > I'm able to startup the VM, but when it loads the ISO to install Windows > 10 which I downloaded from Microsoft, Attached is what always happens. > Perhaps my ISO is corrupt? > > On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler wrote: > >> On Fri, 1 Feb 2019 17:37:30 -0500 >> Darin Schmidt wrote: >> >> > [root@ovirt ~]# rpm -qa kernel >> > kernel-3.10.0-957.1.3.el7.x86_64 >> > kernel-3.10.0-862.el7.x86_64 >> > [root@ovirt ~]# uname -a >> > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC >> 2018 >> >> https://bugzilla.redhat.com/1638835 looks like there is at least >> kernel 3.10.0-957.3.1.el7.x86_64 required. >> Can you please check if upgrading to kernel solves the issue for you? >> I expectect at least kernel 3.10.0-957.5.1 to be availible. >> >> > x86_64 x86_64 x86_64 GNU/Linux >> > [root@ovirt ~]# rpm -qa qemu-kvm-ev >> > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 >> > [root@ovirt ~]# rpm -qa libvirt >> > libvirt-4.5.0-10.el7_6.3.x86_64 >> >> > here is the vdsm >> > >> >> contains: >> Hyper-V SynIC is not supported by kernel >> >> >> > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler >> > wrote: >> > >> > > On Fri, 1 Feb 2019 11:48:51 -0500 >> > > Darin Schmidt wrote: >> > > >> > > > I have successfully setup a centos vm, its up and running. Now I >> > > > need to setup a windows 10 VM and I cant seem to get anything to >> > > > work. >> > > > >> > > > Ive tried setting the OS type to other or Windows 10 64bit. With >> > > > Windows 64bit, it fails to startup at all When I select >> > > > OtherOS it will allow me to start to run the Windows ISO, but >> > > > then fails after a few seconds as well. Is there something I'm >> > > > not correctly configuring? >> > > >> > > Would you please share vdsm.log, and the output of >> > > rpm -qa kernel >> > > uname -a >> > > rpm -qa qemu-kvm-ev >> > > rpm -qa libvirt >> > > from of the host, and the relevant part of engine.log? >> > > >> >> ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/BYIZ36LEPVD5FAD77L7FSDBHN2TZD4SD/ > -- Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/J62MGIRVJSZE5TK7MW5YRJ7YUEQ6KQC2/
