Modify template Files
- Thread starter AntoWkill
- Start date
Hello AntoWkill
I think you mean VM templates rather than CT templates.
The answer is: No!
Note that a template is ready to be the base for one or more linked clones and a change in it´s filesystem can destroy all these dependencies.
Therefore: as soon as a VM is converted to a template it´s HD is read-only.
But what you can do is the following: create a new machine (full clone) based on the existing template - without starting it you can access to it´s HD (see http://blog.loftninjas.org/2008/10/27/mounting-kvm-qcow2-qemu-disk-images/) and change whatever you like. Afterwards you make a new template from it.
Kind regards
Mr.Holmes
I think you mean VM templates rather than CT templates.
The answer is: No!
Note that a template is ready to be the base for one or more linked clones and a change in it´s filesystem can destroy all these dependencies.
Therefore: as soon as a VM is converted to a template it´s HD is read-only.
But what you can do is the following: create a new machine (full clone) based on the existing template - without starting it you can access to it´s HD (see http://blog.loftninjas.org/2008/10/27/mounting-kvm-qcow2-qemu-disk-images/) and change whatever you like. Afterwards you make a new template from it.
Kind regards
Mr.Holmes
Thanks!! So i can mount qcow2 disk image on dedicated server and acces from the ssh of the dedicated server right?
anybody ever tried
http://libguestfs.org/guestfish.1.html
?
could it work on stopped proxmox kvm disks? on pve hosts or in other ways?
Marco
http://libguestfs.org/guestfish.1.html
?
could it work on stopped proxmox kvm disks? on pve hosts or in other ways?
Marco
Yes
Another possibilty seems to be "guestfish" (see new post). I didn´t know it before and don´t know what the advantage is compared with qemu-nbd which is already included in proxmox.
When i try to mount a NFTS disk (Windows) i have an error; mount: unknown filesystem type 'ntfs',
This method does not work with Windows?!
For access to ntfs filesystem package ntfs-3g is needed which is not included in standard proxmox installation. After installing it it should work - but I didn´t test it in a proxmox installation yet.
Yes it work perfectly, now i have the same problem for FreeBSD
You need the proper filesystem driver also in that case. Usually it can be done by
Code:
modprobe ufsbut this kernel module is not available in proxmox, moreover I think that supports only "read-only". Deeper investigation would be necessary.
>Module ufs not found.
It depends on the kernel, which in pve is derived from redhat stable (thus old).
You could try the 3.10 **test** kernel but you could get other side effects, mainly: currently it has no openvz.
one way could be, when you need to edit ufs filesystem resources, to start that vm with a livecd iso which has ufs module support (try #modinfo ufs), if this fits your needs..
then you could mount your "local" ufs disk in the livecd...
Marco
It depends on the kernel, which in pve is derived from redhat stable (thus old).
You could try the 3.10 **test** kernel but you could get other side effects, mainly: currently it has no openvz.
one way could be, when you need to edit ufs filesystem resources, to start that vm with a livecd iso which has ufs module support (try #modinfo ufs), if this fits your needs..
then you could mount your "local" ufs disk in the livecd...
Marco