Update an existing jail template

Status
Not open for further replies.

Marc Allard

Explorer
Joined
Mar 16, 2014
Messages
56
Hello,

I have installed freenas and I have a jail VirtualBox-4.3.10.
i have seen that there is now a new jail template VirtualBox-4.3.12
Is there a way to update the jail (without having to create a new one and remove everything)?

Thank you
Marc
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
There's a new 4.3.12 jail template? where? Because AFAIK there isn't one and there probably shouldn't be...
 

Marc Allard

Explorer
Joined
Mar 16, 2014
Messages
56
Hello,

In freenas 9.2.1.7 in the GUI, when you go in the Jails and in Templates you see a jail VirtualBox-4.3.12
Here is a print screen

Marc
 

Attachments

  • jailVBOX.png
    jailVBOX.png
    104.8 KB · Views: 328

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525

fracai

Guru
Joined
Aug 22, 2012
Messages
1,212
I have that same URL and my template list includes VirtualBox-4.3.12
I'm on 9.2.1.6
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
I'm on 9.2.1.7. I've asked about this because I don't have the answers. AFAIK you shouldn't be trying to use 4.3.12 as the kernel drivers haven't been updated in FreeNAS itself. So stay tuned.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Ok, so it turns out that 9.2.1.7 has the kernel drivers for virtualbox updated to 4.3.12. I thought this would have been in the release notes but it wasn't. I'll try to make sure this information is available in the future.

There is no way to 'update' an installed template with a newer template. If you want to use a newer template then you must destroy the current template and replace it with the newer template.

However, you should be able to upgrade your currently installed template from the command line. Just do a pkg update and pkg upgrade. Do take note that if you don't stay on top of this and 4.3.12 isn't offered through pkg-ng repositories you are kind of stuck until the next version is available. I'm looking into providing the compressed pkg for those that miss the window of opportunity to upgrade.
 

Marc Allard

Explorer
Joined
Mar 16, 2014
Messages
56
Hello,

Thank you.
I have the error
Proceed with this action [y/N]: y
[vbox] Fetching qt4-gui-4.8.6_2.txz: 100% of 4 MB
pkg: cached package qt4-gui-4.8.6_2: size mismatch, fetching from remote
[vbox] Fetching qt4-gui-4.8.6_2.txz: 100% of 4 MB
pkg: cached package qt4-gui-4.8.6_2: size mismatch, cannot continue


when I do the pkg upgrade (in the jail)
s
jexec 1 csh
pkg update
pkg upgrade


EDIT :
pkg update -f
and after that an upgrade won't work. there are problemw with the virtual box jail. I had to restore a snapshot.

Marc
 
Last edited:

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Sorry but there's not enough information in your post to even know what is wrong aside from something with the pkg-ng installation. :(
 

Marc Allard

Explorer
Joined
Mar 16, 2014
Messages
56
Hello,

I am sorry. Here is more information :
When I force the update (and the upgrade) I have a message telling me that the web server (apache) will be obsolete and I need to remove it. If I chose no, the upgrade doesn't work.
If I say Yes, the upgrade works.
After that, phpvirtualbox doesn't work anymore (I have a blank page).
My Freenas computer becomes slow (nearly one minute to make the login page of Freenas appear)
As soon as I try shut down the jail, the Freenas server restart.
When I look at the console (via IPMI) I see that my script to shut down the virtual machine doesn't work.
(http://forums.freenas.org/index.php?threads/autostart-virtualbox-vm.22116/#post-132606)
It says that the vboxheadless is not running.
After that there is a crash (of the freenas host).

Marc
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Are you stopping services like apache before doing the upgrade? Upgrading files that are in use doesn't always "go well".
 

Marc Allard

Explorer
Joined
Mar 16, 2014
Messages
56
Hello,

No I didn't do anything like that. As the message was about a problem with apache not being usable anymore after the update I didn't think it would me a problem.

Marc
 
Status
Not open for further replies.
Top