Recent content by briankwest

  1. B

    Enable or Disable Hyperthreading?

    You'll want it on (Especially on an E5). Its not vCPU's when Hyper-threading is on. It takes the pipeline and splits it allowing to to process two thread per core. Its way better than when it first came out. /b
  2. B

    Only 1 backup(s) allowed?

    Does it not remove old backups? The first thing that came to mind when that option was presented was that it would remove the oldest backup automatically. /b
  3. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Source is a : Intel(R) Xeon(R) CPU E31275 @ 3.40GHz Target machine is: Intel(R) Xeon(R) CPU X3370 @ 3.00GHz /b
  4. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Debian 32bit template.. the two nodes are different but equal in features for this. /b
  5. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Anyone else able to confirm this works or not with latest proxmox 2 build? /b
  6. B

    Advice for someone looking at using Proxmox (KVM) in our small office

    1. Its bare metal so you don't need an os. 2. They offer support on their website its not very expensive. 3. YES CONVERT! /b
  7. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Updated both systems and tried again. pve-manager: 2.0-59 (pve-manager/2.0/18400f07) running kernel: 2.6.32-11-pve proxmox-ve-2.6.32: 2.0-66 pve-kernel-2.6.32-10-pve: 2.6.32-63 pve-kernel-2.6.32-11-pve: 2.6.32-66 lvm2: 2.02.88-2pve2 clvm: 2.02.88-2pve2 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-2...
  8. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Here is a screen shot of what the console said: http://i.imgur.com/lVEAv.jpg
  9. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Message from syslogd@proxmox00 at Apr 12 16:48:15 ... kernel:Oops: 0000 [#1] SMP Message from syslogd@proxmox00 at Apr 12 16:48:15 ... kernel:last sysfs file: /sys/kernel/uevent_seqnum Message from syslogd@proxmox00 at Apr 12 16:48:15 ... kernel:Stack: Message from syslogd@proxmox00 at...
  10. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Apr 12 16:37:08 starting migration of CT 110 to node 'proxmox00' (192.168.1.252) Apr 12 16:37:08 container is running - using online migration Apr 12 16:37:08 starting rsync phase 1 Apr 12 16:37:08 # /usr/bin/rsync -aH --delete --numeric-ids --sparse /var/lib/vz/private/110...
  11. B

    Online Migration of OpenVZ container causes target box to kernel panic.

    Has anyone else seen this? Before I go digging more. /b
  12. B

    KVM Migration

    Done. As I get more into the code I'll be able to give more back in patches... Right now I can test test test. Thanks you guys. /b
  13. B

    Assign some hard disks to a OpenVz CT

    You can't as far as I know. Its a container so it already has close to raw access to the disk the container is on. /b
  14. B

    KVM Migration

    OK one way to make this more usable is to just fail the migration if the disk image isn't visible from the target node when using storage marked shared? /b
Top Bottom
Back