Search results

Great, thanks.

Hello, just noticed, that after upgrade to 1.9, there is some changes in openvz system resource management? before upgrade there always been CPUs: 1 for every single openvz client and the client could see all the cores available on the host machine. so if i have 16 cores total on the host...

Today i've seen a new kernel update has arrived. is there something related to this issue too?

Hello, have You managed to reproduce this panic?

have You tried with bridged interface? i found on google, that this panic is typical for bridged interfaces only. try to actively connect to server with ip address that is rejected in some iptables rule. my iptables rules are in first post of this topic. on this server there is external traffic...

Hello, dietmar Glad that there is still war spirit to get some problems solved :) okay. kernel shows panic only when i use REJECT in iptables conf file (even without options). as soon as i add REJECT instead of DROP it gives me panic @ random time (this time it took about 17 minutes). As google...

nono, ur english is fine. i just didnt understand that ur question is related to the kvm functions only and wrote for u a whole manual, how to backup ur windows disk, using samba utils in linux :) and after tom's answer i just edited my message. :)

as proxmox does not support linux software raid (and i'm personally agree with such decision) there are not many choises for you left :) u should use a hardware raid controller and crete raid1 for ur /var/lib/vz and / dirs. mypersonal setup for proxmox systems is typically something like this...

-=[edited]=- didnt understand the question right.

okay, i dont know if some1 really interested in this bug, but the problem is in the iptables REJECT action (may be with option --reject-with icmp-host-prohibited only, i didnt test without it, cuz i don't really see if there are interested ppl). atm i changed it with DROP and there is no more...

ideas any1? it is not really safe to leave those vpses without any firewall? (and i don't really want to configure my border juniper firewall to protect some vpses)

Hello, in previous post i made lots of assumptions about what could be the reason of random kernel panics. i decided to make a new thread as the previous one started to grow with unneeded information. now i'm sure its up to iptables. if i dont run it on 2 of my proxmox machines, it runs fine. if...

Re: weird problem and kernel panic after uping to 1.9 hmmmmmmmmm, seems i've found the root of the problem! its iptables. if i run iptables on the proxmox host i get a crash after some random time! i will test it now. on other machine typically i ran iptables after reboot, but last time i...

Re: weird problem and kernel panic after uping to 1.9 wow, now it went a bit further and it had time to give me such message before rebooted :) kernel:Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff8149c55c does it help?

Re: weird problem and kernel panic after uping to 1.9 well, it does not matter. turning these options off dint help anyway.. i'm afraid i'll have to stick to the older kernel, seems is kernel. i had this error on other machine that is not totally different fro this one. will i miss something...

Re: weird problem and kernel panic after uping to 1.9 i'm afraid that i will get typical HP answer about my OS :(. if not rhel - no support. ok. i've turned them off and will test now.

Re: weird problem and kernel panic after uping to 1.9 well, seems like it could be a problem of network card. bios and dmesg say that it is 1 gbit, but it works in 100 mbit mode (cisco port is 10/100/1000) and if i force cisco port 1000 full duplex, server does not respond anymore. atm i'm...

Re: weird problem and kernel panic after uping to 1.9 rebooted to test new kernel .. and again. any ideas? what should i do? or any ideas what should i check? 2.6.32-4 works fine.

Re: weird problem and kernel panic after uping to 1.9 services:~# pveversion -v pve-manager: 1.9-24 (pve-manager/1.9/6542) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 1.9-43 pve-kernel-2.6.32-4-pve: 2.6.32-33 pve-kernel-2.6.32-6-pve: 2.6.32-43 qemu-server: 1.1-32 pve-firmware: 1.0-14...

Re: weird problem and kernel panic after uping to 1.9 i'm running 2.6.32-4 atm, as both 2.6.32-6 from stable and testing repo crashed.