VM starts before host network is 100% up

A

adamb

Famous Member
Proxmox Subscriber
Mar 1, 2012
1,329
77
113
We have a configuration were we are running a single windows VM on a host. Within the windows VM we have a application running in assigned access as a "kiosk". This application can only check for network connectivity one time when it starts due to limitations in assigned access.

It seems that proxmox is starting the VM before linux networking is up 100%. Because the windows VM boots so quickly it gets into the assigned access app, checks for connectivity and it fails.

I thought I could get around this with a startup delay of the VM, but it looks like that won't work with a single VM.

Ideally, it would be nice if the VM wouldn't start until after networking is up 100%. Does anyone have any suggestions or ideas?

Sep 12 09:44:36 K-787-Fingerlks pve-guests[1672]: <root@pam> starting task UPID:K-787-Fingerlks:00000698:00002AF8:5B991844:startall::root@pam:
Sep 12 09:44:36 K-787-Fingerlks pve-guests[1688]: <root@pam> starting task UPID:K-787-Fingerlks:0000069B:00002AF9:5B991844:qmstart:100:root@pam:
Sep 12 09:44:37 K-787-Fingerlks kernel: [ 110.957095] vmbr1: port 1(tap100i0) entered blocking state
Sep 12 09:44:37 K-787-Fingerlks kernel: [ 110.957097] vmbr1: port 1(tap100i0) entered disabled state
Sep 12 09:44:37 K-787-Fingerlks kernel: [ 110.957183] vmbr1: port 1(tap100i0) entered blocking state
Sep 12 09:44:37 K-787-Fingerlks kernel: [ 110.957184] vmbr1: port 1(tap100i0) entered forwarding state
 
The VM start has the dependency on the network service being up. But with Win10, it could be that the start of the Windows is pre-initialized on "shutdown" and that state is not there anymore. It might help, if the start of the Windows is delayed too.
 
Alwin said:
The VM start has the dependency on the network service being up. But with Win10, it could be that the start of the Windows is pre-initialized on "shutdown" and that state is not there anymore. It might help, if the start of the Windows is delayed too.
Click to expand...

That is what I was hoping to do, simply delay the start of the windows VM. However it doesn't seem like the start/stop delay can handle this with only 1 VM on the host?
 
adamb said:
That is what I was hoping to do, simply delay the start of the windows VM. However it doesn't seem like the start/stop delay can handle this with only 1 VM on the host?
Click to expand...
You can set two delays, one for the VM start and the other for the OS inside the VM.
 
You must log in or register to reply here.
Top Bottom