New CT template - with issues

sweet-t

New Member
Oct 22, 2012
19
2
1
Hi folks. I am creating a new Centos-6.3-x86_64-minimal CT template and having some troubles. Hope you won't mind addressing some of my concerns.

My template is based on a KVM I spun up as a CentOS CT development KVM.
266MB - which seems large as I compare sizes of other available templates.
I've created a couple working CTs using it.

However, this is the initlog of one of these CTs using my template(all identical):
Code:
starting init logger
cat: /proc/self/attr/current: No such file or directory
Welcome to CentOS 
Starting udev: [ OK ] 
Setting hostname dcache.domain.com: [ OK ] 
Setting up Logical Volume Management: /proc/devices: No entry for misc found
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
No volume groups found
[ OK ] 
Mounting local filesystems: mount: unknown filesystem type 'ext4'
[FAILED] 
Enabling /etc/fstab swaps: [ OK ]

1) cat: /proc/self/attr/current: No such file or directory

Solutions?

2) Setting up Logical Volume Management: /proc/devices: No entry for misc found
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
No volume groups found [ OK ]


Assuming this is expected (as marked [ OK ]) but preceding lines only spell errors.

3) Mounting local filesystems: mount: unknown filesystem type 'ext4' [FAILED]

I believe this only affects enforcing disk quota? My NAS is formatted as XFS
Is there any other problems as to ext4? My CT seems to be booting normally otherwise.
What is the best practice to resolve this? Should I recreate the CT on an EXT4 storage?

After starting the CT I see this in my /var/log/messages:
Code:
# tail -f /var/log/messages
Oct 22 03:28:30 dauth2 lldpad: bound ctrl iface to /com/intel/lldpad
Oct 22 03:28:30 dauth2 lldpad[580]: init_ports: Error adding device venet0
Oct 22 03:28:30 dauth2 lldpad[580]: init_ports: Error adding device eth0
Oct 22 03:28:30 dauth2 fcoemon: error 2 No such file or directory
Oct 22 03:28:30 dauth2 fcoemon: make sure FCoE driver module is loaded!

4) lldap expectations?

5) fcoemon errors

I tried reinstalling fcoe. After, I restarted service:
Code:
service fcoe startStarting FCoE initiator service: FATAL: Could not load /lib/modules/2.6.32-14-pve/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32-14-pve/modules.dep: No such file or directory
                                                           [  OK  ]

I do not see this folder or path inside the CT, but the file does exist at the path described on my proxmox server.
Im not sure that I can or want to use lldap or fcoe in a CT - the system seems to be working.. would like to clear up these issues before recreating a error free template.

Thanks!
 
Ive stopped fcoe and lldpap on startup and now have no errors in the CT on boot.
Are these services needed?

As with the errors in each CT's initlog - Ive found no resolutions yet
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!