Search results

  1. V

    KVM + physical device

    Hi Tom, yes the Samsung HDD is on /dev/sdb. Latest Update proxmox-testserver:~# pveversion -v pve-manager: 1.4-7 (pve-manager/1.4/4366) qemu-server: 1.1-5 pve-kernel: 2.6.24-16 pve-qemu-kvm: 0.11.0-2 pve-firmware: 1 vncterm: 0.9-2 vzctl: 3.0.23-1pve3 vzdump: 1.2-2 vzprocps: 2.0.11-1dso2...
  2. V

    KVM + physical device

    Hi Tom, sorry for the example. I mean ide1: i have make a mistake. Here is my qm conf ide2: local:iso/openfiler-2.3-x86-disc1.iso,media=cdrom vlan0: e1000=FA:4B:2A:A1:9F:86 bootdisk: ide0 ostype: other ide0: local:113/vm-113-disk-1.raw memory: 512 sockets: 1 ide1: /dev/sdb qm start 113...
  3. V

    KVM + physical device

    Thanks Tom, i have this (ide:1 /dev/sda) insertet bevor i post. Looks like this is a qemu bug. Become the message "unable to parse volume ID /dev/sda" Regards and a nice weekend, Valle
  4. V

    KVM + physical device

    Hi Tom, sorry but bevor i posted, i have read the manuel for qm but found anything about physical harddrive device. Regards, Valle
  5. V

    KVM + physical device

    Hello, i want to add a physical device /dev/sdx to a kvm machine. How can i do this? Regards, Valle
  6. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    sorry, i wrote a totaly crap.... time for a dinner ;-) forget all what i wrote today ;-) sorry for that.
  7. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    ok, found the problem. If i make a backup vzdump --snapshot --compress --dumpdir /var/lib/vz/dump/ 112 Where dumpdir lies on the local hdd in an lvm When i make vzdump --snapshot --compress --dumpdir /backup/ 112 Where dumpdir here is on the local proxmox HDD, the backup never...
  8. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    its posibble ... but where they comes from? the host (iscsi device) has a update from 50 days ... mhh...
  9. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    no, at 10 Oct 2009 23:30:00 CEST i am not at the business. But the backup was running at this time.
  10. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    log out/in time stand at the end of the logfile. The log is from the iscsi storage.
  11. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    no storage are disabled but the storage "KVM-DATA-02" is unused because the VM is stopped that use the KVM-DATA-02 cat /etc/pve/storage.cfg iscsi: i4500.eth1 portal 192.168.1.95 target iqn.2004-10.com.thecus:iseries-000a40e50:default-target content none lvm...
  12. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    ok, second backup runs finde now. Oct 12 11:21:01 INFO: Starting Backup of VM 112 (qemu) Oct 12 11:21:01 INFO: running Oct 12 11:21:01 INFO: status = running Oct 12 11:21:02 INFO: backup mode: snapshot Oct 12 11:21:02 INFO: bandwidth limit: 10240 KB/s Oct 12 11:21:02 INFO: Logical volume...
  13. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    ok, have killed the tasks and startet the backup again. now it grows. I have checked the syslog again and found something at later time at the backup starts Oct 10 23:32:14 proxmox01 kernel: connection1:0: iscsi: detected conn error (1011) Oct 10 23:32:15 proxmox01 iscsid: Kernel reported...
  14. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    Hi Dietmar, no it didn´t grow. Device is running and working without any issue. The Device is 8GB. No hints in syslog found. Regards, Valle
  15. V

    Proxmox 1.4beta2: Backup from iscsi storage didn´t finish....

    Hello, i have a probleme to backup a VM from a iscsi storage. The Backup didn´t finished and is running from Oct 10 23:27 till now. Oct 10 23:27:52 INFO: Starting Backup of VM 112 (qemu) Oct 10 23:27:52 INFO: running Oct 10 23:27:52 INFO: status = running Oct 10 23:27:53 INFO: backup mode...
  16. V

    openvz & iscsi

    try vzctl and the [--devnodes device:r|w|rw|none] parameter! or add it to the /etc/vz/conf/$VEID.conf file like DEVNODES="sdd1:rw sde1:rw sdf1:rw " Regards, Valle
  17. V

    PVE 1.4 beta2: migration KVM on storages crashed

    we use an amd processor. processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 4 model name : Quad-Core AMD Opteron(tm) Processor 2376 stepping : 2 cpu MHz : 2300.093 cache size : 512 KB physical id : 0 siblings : 4 core id : 0 cpu cores...