SVN 3125 & Hyper-V 2012 R2
-
– svn: 3373
[B]-- Kernel: 4.0.1[/B]
– iPXE: 1.0.0+ (50e7)New msg for Quick Registration!
[CODE]Starting sshd: OK
/bin/fog.auto.reg: line 5: displayBanner: command not found
/bin/fog.auto.reg: line 7: getHardDisk: command not foundhard disk not found!
reboot: Restarting system[/CODE]
New msg for Full Registration!
[CODE]
Starting sshd: OK
/usr/share/fog/lib/funcs.sh: line 457: syntax error near unexpected tokenfi' /usr/share/fog/lib/funcs.sh: line 457:fi’
/usr/share/fog/lib/funcs.sh: line 457: syntax error near unexpected tokenfi' /usr/share/fog/lib/funcs.sh: line 457:fi’
/bin/fog.man.reg: line 4: clearScreen: command not found
/bin/fog.man.reg: line 5: displayBanner: command not found
/bin/fog.man.reg: line 7: getHardDisk: command not foundhard disk not found!
reboot: Restarting system
[/CODE]Reverting to [B]Kernel: 3.18.5 .[/B]
[B][/B] -
it’s not the kernel.
Update again.
-
Actually … it looks like the problem may be svn 3373. Reverting to 3.18.5 does not fix the new errors.
-
Hehe … doing that.
-
Okay, we’re back to the original problem.
Reverting to [B]Kernel: 3.18.5 .[/B]
-
Updating my Development Fog
– svn: [B]3385[/B] – Kernel: [B]4.0.2[/B]
– iPXE: 1.0.0+ ( [B]86aa[/B] )The problem persists as described at the top of this thread for the Hyper-V 2012 R2 client.
Reverting to [B]Kernel: 3.18.5 .[/B]
-
@Wayne-Workman said:
I’m going to try to network boot a Hyper-V win7 just to see what happens…
I’ll attempt to register and upload an image.Have you had a chance to test yet Wayne?
-
Not yet… sorry.
I’ll try to get to it on Tuesday. It should be pretty easy to test though.
I’ve got a lot of irons in the fire at work right now.
-
@sudburr I don’t know exactly what’s causing the problem in the future kernels. Tie that into the fact that not a whole log changed from moving to 3.19.* from 3.18.*. If you would like to see if there’s more, you could try building your own kernels. Of course, I ask if you can, if you figure it out, please let me and/or the community know what had to happen.
Here’s a link that should at least help you with getting started: https://wiki.fogproject.org/wiki/index.php/Build_TomElliott_Kernel.
During the
make menuconfigor
make ARCH=i386 menuconfigphases, check out the options and try to remember what you’ve changed or whatever.
I do know it’s a bit of work but I haven’t had any in finding a working option for you.
-
Meanwhile, updating my Development Fog
– svn: 3477 – Kernel: 4.0.4
– iPXE: 1.0.0+ ( 15759 )The problem persists as described at the top of this thread for the Hyper-V 2012 R2 client.
Reverting to Kernel 3.18.5 .
-
Updating my Development Fog:
– GIT 4367 aka SVN 3868
– Kernel: 4.1.4
– iPXE: 1.0.0+ ( 989f )The problem persists as described at the top of this thread for the Hyper-V 2012 R2 client.
Reverting to Kernel 3.18.5 .
I’ve uploaded some pics and vids of what happens
-
Good news everyone! Now it’s my turn to be called an idiot… maybe
When FOG came in as our deployment solution I also quickly ramped up through server revisions (core and gui) to our current 2012 R2u1 and Hyper-V. My initial tests with Fog 0.29 with whichever version of Hyper-V it was at the time, showed that I couldn’t PXE boot properly unless I disconnected the Ethernet adapter from the Virtual Switch, leaving the Legacy Adapter connected alone. One or the other could be connected, but not both at the same time.
Annoying, but the workaround … worked; albeit at 100Mb.
I couldn’t sleep tonight (yep, it’s 2am) so I tried something other than Quick or Full Reg; I tried a Quick Image on the Hyper-V VM. This option didn’t exist on FOG way back in 0.29 or so. I expected Quick Image to fail with what appeared to be a controller /sda no hard drive and unable to register error that appeared when attempting Quick or Full Registration. This time though, I got an adapter error.
How can this be? I can PXE boot. The Legacy adapter is obviously working.
I double checked the VM. Yep, Legacy is connected, and the ‘Ethernet’ (synthetic) is disconnected.
Hmm … so I reconnected the VM’s main ‘Ethernet’ adapter to the same virtual switch as the Legacy adapter, so both were connected at once and tried again.
The bloody thing works.
I’m glad it works but riddle me this batman. Why does 3.18.5 work with either both connected or just the Legacy connected? … while 4.1.4 requires that both be connected?
-
@sudburr said:
Why does 3.18.5 work with either both connected or just the Legacy connected? … while 4.1.4 requires that both be connected?
Who cares, it works??? lol. Stop making our brains hurt and just enjoy the victory
-
