This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About Gabeeh
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About Gabeeh
02-08-2023
1Post
2Likes
0Solutions
Feb 08, 2023Last Visited
User
Activity
User
Profile
Latest posts by Gabeeh
| Subject | Views | Posted |
|---|---|---|
| 1522 | 01-03-2023 12:05 PM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 2 Likes | 01-03-2023 12:05 PM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 1 Like |
User Badges
Community Statistics
| Member Since | 04-20-2022 09:32 AM |
| Date Last Visited | 02-08-2023 07:04 PM |
| Posts | 1 |
| Total Likes Received | 2 |
01-03-2023
12:05 PM
2 Kudos
We got a customer that runs into this issue recently, it's a known issue (not public) for versions 11.0.0, 10.2.3, 10.2.2-h1 (and also to us 10.2.3-h2, 10.2.2-2).
When you run into this, means that there's a hardware issue, please go to TAC in order to find the root cause.
VM-series fails to boot on Hyper V with older Intel Xeon CPUs.
This is happening with Hyper V.
The solutions that we used to fix it are two:
Revert to the previous version in maintenance mode:
Enter maintenance mode
Disk image
Revert to the previous
Deactivate the Vm and deploy a new one, in this case they use credits VM:
Deactivate the VM license: Deactivate License (Software NGFW Credits) (paloaltonetworks.com)
Deploy a new one.
I post this since it happened to me twice and couldn't find more info, or more relevant info regarding it.
Best wishes!
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks