Questions...

[tester]

Hi, im testing the new 4.0 release and have some questions. 1. I have a NFS share where all my isos are stored, when I connect my proxmox host it creates 2 folders "templates" and under it "isos". In the "Storage" Tab I just choose "ISO" as content. Why the folders will be created when there is only one content type? 2. How to deal with vlans? I planned a vlan for the proxmox nodes, one for storage and one vlan for the clients. Should I set it up this way? 3. I can't create any CT or VM, I've downloaded the ubuntu 15.04 lxc template and tryed to set up new CT but the setup process stops at creating the filesystem with

 Allocating group tables:  0/64 done  Writing inode tables:  0/64 done Creating journal (32768 blocks): done Multiple mount protection is enabled with update interval 5 seconds. Writing superblocks and filesystem accounting information:  0/64 Warning, had trouble writing out superblocks.TASK ERROR: command 'mkfs.ext4 -O mmp /var/lib/vz/images/100/vm-100-disk-1.raw' failed: exit code 144

I also tested with the centos 7 image with the same error. What's wrong here? If the post lacks of information ask me. Thanks for your time. tester

 

[dietmar]

Do you use ZFS?

 

[udo]

Hi, im testing the new 4.0 release and have some questions.
1. I have a NFS share where all my isos are stored, when I connect my proxmox host it creates 2 folders "templates" and under it "isos". In the "Storage" Tab I just choose "ISO" as content. Why the folders will be created when there is only one content type?

Hi,
the iso folder is below templates - this is the used directory structure since the beginning... (but perhaps it's time to change?) I see no real problem with this.

2. How to deal with vlans? I planned a vlan for the proxmox nodes, one for storage and one vlan for the clients. Should I set it up this way?

This depends on your network... each vlan is one network - so if all clients are in one network and it's not the same, where the pve hosts must be, it's OK.

To use an seperate network (vlan) for the storage is allways an good idea!

I use an seperate storage-network together with the cluster communication (on a dedicated NIC) and all other thraffic via one 10GB-Nic with vlan tagging. The https-access to the pve node is also done with an tagged interface (openVswitch).

Udo

 

[tester]

Hi,

Do you use ZFS?

Yes, I'm using ZFS, 2 HDD mirror.

Hi, the iso folder is below templates - this is the used directory structure since the beginning... (but perhaps it's time to change?) I see no real problem with this. .... Udo

It's not the best solution for me, I have to move all the isos (every new image) from the root folder to the subfolder. tester

 

[pirateghost]

I have to move all the isos (every new image) from the root folder to the subfolder. tester

I use a cronjob on my NAS to sync my ISOs over to the correct directory. This just means I have duplicates of all my ISOs on my NAS somewhere.

 

[sigxcpu]

You can do a cronjob that does symlinks. No space duplication, lightweight

 

[tester]

Hi,
thanks for the input -> symlinks .....
Is there anything new for the not createble CTs and VMs.

tester

 

[udo]

Hi,
thanks for the input -> symlinks .....
Is there anything new for the not createble CTs and VMs.

tester

Hi,
sounds that you don't select "Container" + "Iso Image" for that storage as Content.

Udo

 

[tester]

@udo: I think you got me wrong. It's about the local creating of CTs and VMs, not the storing of the images.

 

[udo]

@udo: I think you got me wrong. It's about the local creating of CTs and VMs, not the storing of the images.

Hi,
then explain, which steps do you do and which don't work.


Udo

 

[tester]

Hi,
it is this...

.... 3. I can't create any CT or VM, I've downloaded the ubuntu 15.04 lxc template and tryed to set up new CT but the setup process stops at creating the filesystem with

 Allocating group tables:  0/64 done  Writing inode tables:  0/64 done Creating journal (32768 blocks): done Multiple mount protection is enabled with update interval 5 seconds. Writing superblocks and filesystem accounting information:  0/64 Warning, had trouble writing out superblocks.TASK ERROR: command 'mkfs.ext4 -O mmp /var/lib/vz/images/100/vm-100-disk-1.raw' failed: exit code 144

I also tested with the centos 7 image with the same error. What's wrong here?

tester

 

[udo]

Hi,
it is this...



tester

Hi,
sounds like wrong permisions - you can't write as root to the storage.

Udo

 

[tester]

the directory /var/lib/vz/images has the rwxr-xrx root:root
the directory ./100 has drwxr----- root:root
the virt hdd has -rw-r----- root:root

is something missing?
tester