I have a Windows Deployment server that works with Hyper-V. I am tryng to see if it will bare metal provision to Ovirt. I have the necessary drivers loaded and initially it gets an IP and starts the installation. When it comes to the screen starting setup, I get an IP error. I have included a screenshot. Has anyone see this before? I also considered provisioning from Foreman but I would rather use what I have instead of recreating the entire installation. Any help would be appreciated. Here is a link to the actual error: ftp://ftp.digitaldatatechs.com/pub/Windows%20Provision.jpg
On Wed, Feb 26, 2020 at 4:45 PM <eevans@digitaldatatechs.com> wrote:
I have a Windows Deployment server that works with Hyper-V. I am tryng to see if it will bare metal provision to Ovirt.
Do you want to provision Windows into an oVirt VM?
I have the necessary drivers loaded
I am not familiar with the Windows deployment server. Would you help me to understand which drivers are loaded to what?
and initially it gets an IP and starts the installation.
I understand that the windows installer is starting. Where does he get the files from?
When it comes to the screen starting setup, I get an IP error. I have included a screenshot.
Might this be related to network drivers? If Windows in an oVirt VM, what is the type of the virtual NIC? Maybe using the e1000 or rtl8139 as type of the virtual NIC helps until the VirtIO drivers are ins talled? Has anyone see this before?
I also considered provisioning from Foreman but I would rather use what I have instead of recreating the entire installation. Any help would be appreciated.
Here is a link to the actual error:
ftp://ftp.digitaldatatechs.com/pub/Windows%20Provision.jpg _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/BGGJTCK7PZKCUS...
I tried to bare metal provision Server 2016 into an ovirt vm. After much research I learned sine the ovirt drivers are not WHQL Windows Deployment Server will not use them. It gets an IP from the pxe boot and gets to a point that says starting setup, then I get the error. I loaded Server 2016, resealed with sysprep and created a template. I think this will be the easiest solution going forward. Inside WDS I can load the drivers for the install. I think this is futile unless I can get signed drivers from ovirt and that's not a possibility. If someone had Red Hat signed drivers from Red Hat Virtualization it may work, other wise I think it's a futile effort.
Hi
If someone had Red Hat signed drivers from Red Hat Virtualization it may work, other wise I think it's a futile effort. Hmm, though I don't think Red Hat will particularly like it, but when it comes to just the drivers, not the full ISO with the RHV/oVirt guest agents there might be a way. You can get a free developer subscription of RHEL (8) and then download the virtio-win package. These contain WHQL drivers with a valid signature.
I haven't had the ability to test it but I've checked the signature. I hope that this helps you a bit. Regards Mathieu
The server getting deployed does indeed get an IP even though it reports it does not. The WDS works flawlessly on Hyper-V so I know the deployment is not the issue. When I open the console to the server being deployed, it states it cannot find the dhcp server (see earlier screen shot) Foreman works deploying Centos 7 and 8 without issue so I'm not sure ever where to look to find out why I get this error. If someone could tell me what log to look in, maybe I can get it figured out. So far, I can't find anything in the logs I looked in. Any help is appreciated.
participants (3)
-
Dominik Holler -
eevans＠digitaldatatechs.com -
Mathieu Simon