So, excitedly, I began to start setting up my environment for the CASP+ TTT.
However, it seems that VBox 6.1.28 decided to throw this error in the first tantrum of the morning:
Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).
According to this forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=104175&p=507408, there are issues with VBox 6.1.28 in running the GNS3 VM. Not sure what other VM's may be having trouble, but I rolled it back to 6.1.26. No go.
For some reason, despite having shut down every Hyper-V thing and even having Windows report that Hyper-V was down, only to have VirtualBox tell me in the log files that it wasn't, I took a sip of coffee and said, "well, heck..it's just a VM, so I guess we're going Redmond and rocking GNS3 on Hyper-V. It can't be all that bad...right?"
Well, seemed like everything was going smooth, until the GNS3 decided to tell me that eth0 wasn't configured. What? You should be getting IP information from Hyper-V...right?
> Get-NetNat
Nope...dead...like my dreams.
I guess I had to set up a different vEthernet switch, configure manually, configure eth0 in the VM to go manual...and after three cups of coffee and several colorful metaphors, scaring off the Amazon guy with a growl of frustration, and watching the minute hands on both of my wall clocks swing round about 3-4 times, I THINK I have it working now. I think it all makes sense.
Downloading Lee's project files - I think that's gonna take a little bit, so I'll finish up the bit of the preso from last night.
Didn't someone say this was the fun part...getting it to work? I'd like to have a little talk with that individual.
Anyone else have as much "fun" as I did? Comments and other snide comments below...
/r
However, it seems that VBox 6.1.28 decided to throw this error in the first tantrum of the morning:
Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).
Result Code: | E_FAIL (0x80004005) |
Component: | ConsoleWrap |
Interface: | IConsole {872da645-4a9b-1727-bee2-5585105b9eed} |
According to this forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=104175&p=507408, there are issues with VBox 6.1.28 in running the GNS3 VM. Not sure what other VM's may be having trouble, but I rolled it back to 6.1.26. No go.
For some reason, despite having shut down every Hyper-V thing and even having Windows report that Hyper-V was down, only to have VirtualBox tell me in the log files that it wasn't, I took a sip of coffee and said, "well, heck..it's just a VM, so I guess we're going Redmond and rocking GNS3 on Hyper-V. It can't be all that bad...right?"
Well, seemed like everything was going smooth, until the GNS3 decided to tell me that eth0 wasn't configured. What? You should be getting IP information from Hyper-V...right?
> Get-NetNat
Nope...dead...like my dreams.
I guess I had to set up a different vEthernet switch, configure manually, configure eth0 in the VM to go manual...and after three cups of coffee and several colorful metaphors, scaring off the Amazon guy with a growl of frustration, and watching the minute hands on both of my wall clocks swing round about 3-4 times, I THINK I have it working now. I think it all makes sense.
Downloading Lee's project files - I think that's gonna take a little bit, so I'll finish up the bit of the preso from last night.
Didn't someone say this was the fun part...getting it to work? I'd like to have a little talk with that individual.
Anyone else have as much "fun" as I did? Comments and other snide comments below...
/r