hsato03 commented on issue #8734: URL: https://github.com/apache/cloudstack/issues/8734#issuecomment-2043699192
> > @rastopato @DaanHoogland > > I could reproduce this bug in my environment. This happens when the user's VM and the VR are stopped and the user starts its VM. In this process, the VR is created with the same boot parameters from the user's VM, which causes the VR to not start when the user VM has the UEFI boot type. On Monday I'll work on a PR to fix this situation. > > As a workaround, you can do a restart with cleanup of your network and, after the VR is up, you can start your VM. > > I tried this scenario @hsato03 , but still the VR starts as expected. not sure what other configuration is in play here. @DaanHoogland Maybe the network should be in `implemented` state. This bug just occurs in VMware by the way. I explained in more detail how to reproduce it in https://github.com/apache/cloudstack/pull/8894. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
