Search results

Hi well, I rebooted some hardware-nodes to get the latest 2.6.32-6-pve kernel to work. The problem that arises is now that ipv6 shows up in the VE though it is a system based on debian-3.1 template (which should normally prevent the script to inject v6 configurations in...

Thanks for the feedback, with promox-2.6.18 I'm stuck with non-working NTP. I guess I would have to try to use the openvz-2.6.18 kernel, but I suppose due to missing KVM support this wouldn't work with promox... I guess I'm lost again :(

Hi actually this is a long standing issue - there have been some suggestions on this forum to get this solved, but in fact to leave the VM as "standard" as possible for us too e1000 is the way to go (in fact not only on Win2k3/8 but also on Ubuntu Kernels running within the VM according to our...

according to current documentation and promox staff 2.6.32 is stable and supports vz and kvm, so I see no big point here, especially as we had lots of NTP and clock issues with the 2.6.18 proxmox kernel on our IBM boxes here, therefore 2.6.32 is running (as already shown in the original post...

actually we already maxxed out the 4 GB lv size for this backuprun in the COW - and yes on some backups (like the one in question especially) the COW table gets too big and lvm kicks out the snapshot-volume - this would all be perfectly fine and the backup could go down for this, but it's...

Aug 15 06:41:32 p03 kernel: Aug 15 06:41:32 p03 kernel: Buffer I/O error on device dm-2, logical block 0 Aug 15 06:41:32 p03 kernel: lost page write due to I/O error on dm-2 Aug 15 06:41:32 p03 kernel: EXT3-fs error (device dm-2): ext3_get_inode_loc: unable to read inode block - inode=1990657...

Hi we had this on one machine now twice, therefore I'm reporting it. Things go like this: vzdump does it's job, but takes (for whatever reason) forever to finish, so after starting this backup at 22:22 hours, the following (quite expected for the given circuumstances): Aug 15 06:40:09 p03...

well, I could have searched for "failed" before in the mail-folder where all the "backup successfull" mails are stored. therefore I can say - this has happened before once: 75002: Jul 08 03:40:03 INFO: Starting Backup of VM 75002 (qemu) 75002: Jul 08 03:40:03 INFO: running 75002: Jul 08...

Hi again, I will look into it - and - I have to report another anomaly that I overlooked because it too says everything is fine - this happened during the same backup-job but two VMs before: RAID-Controller claims everything is fine: hmmm...

Hi in the backuplog I see: the storage for this VM resides in a lvm-volume named /dev/SASRAID5/vm-75004-disk-1, I have never seen this thing building itself to "-real" added at the end nor do I know why it might have failed to deactivate - and at the moment this thing isn't listed in lvscan...

Hi I found this thread in search of the very same problem - NFS mounts aren't there until I look at them via the GUI after a reboot (or vzdump is invoked as our nfs mount is dedicated to vzdump images). I see in Proxmox V1.8 there is already S21vz in /etc/rc2.d. But my problem seems to be...

hi /etc/hosts is already fixed up :) grepping only brought light to bacula that contains the old hostname and all lvm config mentioning the creatinon_host - all listing the old hostname and of course ssh_host_rsa und _dsa files mentioning the old hostname. the vnc-java-thing not found yet...

Hi actually it seemed quite usual - change the hostname in /etc/hostname - reboot. but then there's still /etc/mailname - well - changed that too and reconfigured postfix. after all - the java-applets for the vnc-console are still delivered to the client with the old hostname. any way to get...

Re: ldconfig complains about /usr/lib32/libx...not a symbolic link during aptitude up Udo, thanks for pointing other software out - I was obviously blinded. I guess it has to do with the megaraid-storage-manager we tried to install (but fatally failed). thanks - case closed... (though any...

this happened today on a proxmox kvm-only host: ~# aptitude full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done The following...

Hi we see this in syslog (or rather it surfaced...): pvedaemon[23076]: WARNING: Cannot encode unnamed element as 'hash'. Will be encoded as 'map' instead anyone any idea if we should ignore this in logwatch or any clean solution for this one? regards hk

uhm - why didn't you go for the GUI? simply add another vmbr interface and if you want to add vlanid 7 tagged on eth0 to you new vmbr device simply add "eth0.7" to your bridge ports and you're done. regards hk

Hi as we've been researching a HA storage setup for proxmox too I can only speculate, but ask for confirmation of the gurus if possible: lvm on proxmox doesn't know about the drbd-block-device being shared between two hosts, therefore the problem arises that two lvm configs can't work concurrent...

hi could one please correct the subject of this thread in order to not get other sysadmin's heart to a sudden standstill for virtually nothing? thanks, hk.

Dear Dietmar, thanks for the pointer - I have to investigate this further I think, as Redhat EL5 / CentOS 5 is running a much older kernel than mentioned in this link I can not make sense yet, but then it might also relate to backports done to either the kernel or the lvm tools. Anyways, it is...