@dustinb3403 said in KVM Virtual Machine Boot Order:

@matteo-nunziati said in KVM Virtual Machine Boot Order:

@dustinb3403 but this will include "wait until vm A is operational/service B is available"?

The hypervisor has no way of knowing what the VM does, so no. It just says start this VM first, then that one, and then that one etc.

At this level hyperv acts like xen. Anyway pre post hooks could be available...

@dustinb3403 but this will include "wait until vm A is operational/service B is available"?

@obsolesce said in KVM Virtual Machine Boot Order:

@matteo-nunziati said in KVM Virtual Machine Boot Order:

@dustinb3403 said in KVM Virtual Machine Boot Order:

@obsolesce that's annoying. . .

Edit: still annoying but doesn't Hyper-V have startup priority?

No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers

Hyper-V had startup priority since 2012... fully configurable... startup action and startup delay.

You mean you can use action to wait for another vm to be up and running? If so I ignored it. Delay is mostly a workaround as no one really knows when a dependency will be ready!

@dafyre nope starting order is still 'random'

@black3dynamite said in KVM Virtual Machine Boot Order:

Uncomment START_DELAY=0 in /etc/sysconfig/libvirt-guests file.

https://access.redhat.com/discussions/685243

This will kill parallel startup adding a delay between each vm boot

The only actual need I got was a vm expecting a postgres to be up. I delayed such a vm. But yes: complex dependency schemas are a PITA but also out of the smb standard scenario imho.

@dustinb3403 said in KVM Virtual Machine Boot Order:

@obsolesce that's annoying. . .

Edit: still annoying but doesn't Hyper-V have startup priority?

No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers

never got the issue on centos at work, but this trick of "dummy service" maybe can solve your problem too.

just create a dummy services which waits for the network service to be up and let it be started Before libvirtd.
In this way you do not modify original service unit files but you can add extra dependency between network and libvirt.

@scottalanmiller @dbeato was suggesting to try on linux to see if there is a corruption on the os.
Just before declaring the gpu dead

Dont know about your case. In my case the oem version expected few BIOS info masked by hyperv. Either I altered the hyperv registry or I followed the siplier demo to production conversion.

Ok this link has the command

@joel said in HyperVServer Build:

This server build is frustrating...I managed to get the HyperV server installed and able to connect to it via Hyper-V Manager. However when trying to boot the Guest VM via my CDRom (WindowsServer2016)m it tells me the BIOS was locked and the OS was tied to vendor. Note: I was using the original CD that I got shipped with the server!!!

I then tried burning an ISO (generic) to USB but was unable to mount and boot from it as the HyperV Manager couldnt see the USB plugged into the Host! I read about making it 'offline' first but when attempting that, it turns out i couldnt make removable media offline!!

This thing is a nightmare!
Thinking of packing in Hyper-V!

Sorry to be late. Me too got such errors. When tried to install the oem version of win server purchased with the machine. In my case I solved by installing from a demo iso and then coverting it in a production system via cmd line.
It was an hpe oem disk which refused to run due to hyperv exposed BIOS. Classic hpe shitwork.

Let me dig into the cmds I'll post later.

Accidentally buyed a coke zero with lemon. Terrible. Blah.

Also the ilo networking general info menu should show who is using a nic

Like most out of band systems you are able to mount a remote iso and install os like with virtualbox, to say.
If you have the proper ilo licence...

You shiuld have a left column menu with a dedicated ilo section.
If a shared port is present you should see it in the ilo networking settings.
Last time I deployed an hpe w/ shared port ilo notified it in network settings.

Also hpe sku should give info on hpe dite.

@matteo-nunziati f**k I will never learn how to write on a damn smartphone

@black3dynamite said in Virt-manager: copy the config to a laptop:

From what I can tell, none of conf files in /etc/libvirt needs to be backed up unless you modified them.

In /etc/libvirt/qemu and /etc/libvirt/storage, I do see files that are created when creating VMs, networks and storage.

Those are the VMs I think he means dome options in the vidualization of vmmanager. But I don't temember of anyone. I always open it as is and connect to the remote hypervisor

Check here

Youtube Video