Hi Fernando. The blue screen message is in Portuguese, the majority of the list speaks English. So it will be hard to get some help on this. Regarding the message for non Portuguese speakers, is says that the BIOS and/or the firmware isn’t compatible with ACPI. Since the OS is legacy, this may be something related to missing drivers or something similar to this, like wrong drivers from other hypervisors. You said that you’ve imported the VM for other hypervisor, so it was preinstalled. Did you installed the oVirt Guest Tools before uploading the VM on oVirt? The guest tools should add the required drivers so the VM can boot. It’s a good ideia to remove the tools from the other hypervisor too. On 22 Feb 2021, at 12:15, Fernando Hallberg <fernando(a)webgenium.com.br&gt; wrote: Hi, I have a VM with 2003 server x64, and I upload the vm image to oVirt. The VM boot on the oVirt, but, the blue screen appear with a error message: <image.png> Anybody has some information about this? I try to convert de img file from raw to qcow2, but the error persists. Regards, Fernando Hallberg _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UPP7EBZZ776...

On 24. 2. 2021, at 16:13, Fernando Hallberg <fernando(a)webgenium.com.br&gt; wrote: Hi Vinícius, Thanks in advance. I'm update all ovirt drivers in the drivers in windows 2003, and change de IDE disk to VIRTIO-DISK. I'm started the VM on the old libvirt ( centos7 - kvm ), and the machine boot ok. I'm copy the disk file to ovirt, and i have the same error again. See VM dumpxml: <domain type='kvm'> <name>xxxxx</name> <uuid>c09c46c2-ead5-2cee-d5d7-bd8c701312cd</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='rhel6.3.0'>hvm</type> this doesn’t look like from ovirt, is this the original libvirt’s xml? how does it look on ovirt? what OS Type do you use? You may try older cluster level, with older machine type, but in 4.4 it’s still going to be at least rhel7.5.0. Check if it works with that machine type in your libvirt env first. Also, you can keep using IDE in ovirt…if it works then it’s alright, no? Thanks, michal </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/nfs-exo/badotti/badotti-ts-01.img'/> <target dev='vdb' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:22:42:0b'/> <source bridge='br0'/> <model type='rtl8139'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <console type='pty'> <target type='virtio' port='1'/> </console> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' autoport='yes' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='2'/> </redirdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> Any idea? Em seg., 22 de fev. de 2021 às 12:25, Vinícius Ferrão < ferrao(a)versatushpc.com.br&gt; escreveu: > Hi Fernando. > > The blue screen message is in Portuguese, the majority of the list speaks > English. So it will be hard to get some help on this. > > Regarding the message for non Portuguese speakers, is says that the BIOS > and/or the firmware isn’t compatible with ACPI. > > Since the OS is legacy, this may be something related to missing drivers > or something similar to this, like wrong drivers from other hypervisors. > You said that you’ve imported the VM for other hypervisor, so it was > preinstalled. Did you installed the oVirt Guest Tools before uploading the > VM on oVirt? The guest tools should add the required drivers so the VM can > boot. It’s a good ideia to remove the tools from the other hypervisor too. > > On 22 Feb 2021, at 12:15, Fernando Hallberg <fernando(a)webgenium.com.br&gt; > wrote: > > > Hi, > > I have a VM with 2003 server x64, and I upload the vm image to oVirt. > > The VM boot on the oVirt, but, the blue screen appear with a error > message: > > <image.png> > > Anybody has some information about this? > > I try to convert de img file from raw to qcow2, but the error persists. > > Regards, > Fernando Hallberg > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/UPP7EBZZ776... > > > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KTVYEYHATLK...

Il giorno lun 22 feb 2021 alle ore 16:18 Fernando Hallberg < fernando(a)webgenium.com.br&gt; ha scritto: > Hi, > > I have a VM with 2003 server x64, and I upload the vm image to oVirt. > Please note 2003 server gone end of life in 2015 ( https://www.microsoft.com/en-ie/mrap/products/windows-server-2003) I would consider updating to a supported windows OS before trying to migrate to oVirt. That said, I would also recommend ensuring latest virtio-win drivers are installed on the guest. > > The VM boot on the oVirt, but, the blue screen appear with a error > message: > > [image: image.png] > > Anybody has some information about this? > > I try to convert de img file from raw to qcow2, but the error persists. > > Regards, > Fernando Hallberg > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/UPP7EBZZ776... > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

Hi Fernando. On oVirt, you can use a no destructive reinstall. Its worked for me. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ECNAPNY2OBI...