Hi, i converted two disks (sda, sdb) of a working vmware vm (ubuntu server + lamp).
Everything worked since first boot, except a virtualhost (the main one on that machine) which authenticates users against win2003 AD, which from the logs fails authenticating users
command line ldapsearch testing works both on the kvm vm and on the proxmox host (debian+pve), and i can read averything on the AD...
any hint of what could make mod_authnz_ldap apache2 module fail, having just converted vmdk to qcow2?
vmdk were copied from real disk with vmware-vdiskmanager (-t 0)
copied vmdks were then converted (-O qcow2) to .qcow2 format
i post here just to be sure nothing at pve level could block or interfere with this..., as i am a pve beginner: could be something in the bridged network?
pveversion -v output:
----------------------
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5
------------------
we can't really figure out what could be wrong...
Any hint would be greatly appreciated...
Marco
Everything worked since first boot, except a virtualhost (the main one on that machine) which authenticates users against win2003 AD, which from the logs fails authenticating users
command line ldapsearch testing works both on the kvm vm and on the proxmox host (debian+pve), and i can read averything on the AD...
any hint of what could make mod_authnz_ldap apache2 module fail, having just converted vmdk to qcow2?
vmdk were copied from real disk with vmware-vdiskmanager (-t 0)
copied vmdks were then converted (-O qcow2) to .qcow2 format
i post here just to be sure nothing at pve level could block or interfere with this..., as i am a pve beginner: could be something in the bridged network?
pveversion -v output:
----------------------
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5
------------------
we can't really figure out what could be wrong...
Any hint would be greatly appreciated...
Marco