I heard the kernel from the unstable rep fixed this issue with KVM so, is the kernel from the test rep of proxmox based on unstable or is it based of test rep?
Nehalem Xeon E5520 and Intel S5520UR
- Thread starter nick
- Start date
Because proxmox was debian based i thought that...
But ok, the unstable rep of debian has a kernel that fixes this bug, maby you gys can take a look at the differences?
It was the 2.6.32 unstable, not the test rep.
But ok, the unstable rep of debian has a kernel that fixes this bug, maby you gys can take a look at the differences?
It was the 2.6.32 unstable, not the test rep.
Please test our kernel first - I don't want to waste my time hunting non-existent bugs.
Don't get me wrong, i installed the kernel .32 from the test rep op proxmox.
The problem is that i can't re-create the problem, the preveious kernel worked for like 2 month's but then crashed so i can't tell for sure if this one workes!
- What is the longest uptime of a VM?
- kernel 2.26.32-2 on the proxmox machine?
- And maby more info about the os of the VM etc.. ?
Thx
- kernel 2.26.32-2 on the proxmox machine?
- And maby more info about the os of the VM etc.. ?
Thx
Well but i usually am getting this issue once in about ~2months so how can you be sure it works ok?
Sorry to bother you so much but i am trying to figure out why i get the panic's.
- Wat are the specs of your hardware and how much vm's do you run on it?
- Are they debian vm's or...?
- Wat are the specs of your hardware and how much vm's do you run on it?
- Are they debian vm's or...?