virtualbox image upload r4792
-
Try a different kernel - I’d suggest the latest kernel.
4792 is really behind (by over 2,000 revisions), you should consider updating to the latest. The latest revision would also grab the latest kernel and init.
-
@Wayne-Workman r4792 is 6263
-
Red hat / Fedora / CentOS 7 instructions are below. Should be just copy/paste for the parts you want.
Older Ubuntu would be /var/www/fog/blah/blah instead of /var/www/html/fog/blah/blah#Delete previous backed up kernels & inits. rm -rf /var/www/html/fog/service/ipxe/old #Make a directory to put old kernels & inits into. mkdir /var/www/html/fog/service/ipxe/old #Move old inits, get new ones. mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz mv /var/www/html/fog/service/ipxe/init_32.xz /var/www/html/fog/service/ipxe/old wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz #Move old kernels, get new ones. mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/old wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32 #Reset permissions. chown -R fog:apache /var/www/html/fog/service/ipxe chmod -R 775 /var/www/html/fog/service/ipxe #Script complete. echo DONE!
-
@Wayne-Workman the kernel i am using is 4.4.1
-
@Raymond-Bell Does it show that text at the same spot every time or right from the start? Does the capture complete?
-
@Wayne-Workman said:
@Raymond-Bell Does it show that text at the same spot every time or right from the start? Does the capture complete?
It uploads between 30% and 60% the i get this message and it just repeats (the message) if i let it set there
I have tried about 12 times
-
@Raymond-Bell Have you been able to capture from a Virtualbox in the past?
-
@Wayne-Workman yes
-
@Raymond-Bell Do you remember when that was? Would you happen to know what kernel version you were using at the time?
-
@Wayne-Workman said:
@Raymond-Bell Do you remember when that was? Would you happen to know what kernel version you were using at the time?
It has been about 4 months ago and i am sorry i don’t remember the kernel at the time
-
@Raymond-Bell If you go to
FOG Configuration -> Kernel Update
can you try to grab the 64 bit 4.1.0 kernel or the 4.2.0 kernel and try those out? Let us know the outcome. -
@Wayne-Workman said:
@Raymond-Bell If you go to
FOG Configuration -> Kernel Update
can you try to grab the 64 bit 4.1.0 kernel or the 4.2.0 kernel and try those out? Let us know the outcome.It is 32bit image will that matter getting the 64bit kernel
-
@Raymond-Bell Is this actually impacting anything? I’ve heard of funny things displaying for virtual box, but to my knowledge things still worked.
-
@Raymond-Bell said:
It is 32bit image will that matter getting the 64bit kernel.
Well if it’s 32 bit than grab the 32 bit 4.1.x/4.2.x kernel and give it a shot.
I guess this is a good start for reading up on those messages: https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt
Does the system freeze or panic or just keeps going?
-
@Wayne-Workman @Tom Elliott @Sebastian-Roth
I used kernel 3.0.1 and it worked perfect…
-
@Raymond-Bell That still doesn’t answer our questions though, not that you necessarily need to.
Did the errors you saw actually stop things from occurring? Or were things actually halted?
-
Interesting, I’ve had this happen before (it halts the progress), but usually if I just try again it will work fine.
Is the computer running virtualbox doing other stuff while you’re trying to capture from it?
-
They stopped it from uploading the image so YES
-
I let it sit over night and still was hung when i came in next day.
And no the computer was not doing anything else…
-
@Raymond-Bell said:
@Wayne-Workman @Tom Elliott @Sebastian-Roth
I used kernel 3.0.1 and it worked perfect…
Ok, it works with kernel 3.0.1. The next step is to get the very next kernel version that is available after this and try it. Let us know the version number where it isn’t working. We can then compare the kernel configurations between that one and the previous one and probably figure out what changed.