Search results

  1. M

    HP MSA1000 SAN storage.

    Udo, Thanks for the assistance. I believe that I've corrected the issue. I was seeing "LOOP UP" followed immediately by "a cable is unplugged." So I swapped out the fibre cable and rebooted the server. Viola! I do have a few other questions that you may be able to answer. For some reason...
  2. M

    HP MSA1000 SAN storage.

    Yes. Well, it seems to be. pc-proxmox2:/etc/pve# ls /lib/firmware/ql*.bin /lib/firmware/ql2100_fw.bin /lib/firmware/ql2200_fw.bin /lib/firmware/ql2300_fw.bin /lib/firmware/ql2322_fw.bin /lib/firmware/ql2400_fw.bin /lib/firmware/ql2500_fw.bin pc-proxmox2:/etc/pve# ls...
  3. M

    HP MSA1000 SAN storage.

    I have some additional information that may be helpful. I have another blade from the same enclosure using the same HBA running Citrix XenServer (which is based on Red Hat...or some I'm told). I can expose the SAN storage to that OS as well. I also have an old HP DL380 with an Emulex HBA running...
  4. M

    HP MSA1000 SAN storage.

    Greetings! I am having a problem getting MSA1000 disk exposed to my Proxmox 1.7 host. I am running PM on a Dell M600 series blade server with a QLogic QME2572 HBA. Here is an applicable excerpt from the kernel message log: May 2 16:58:11 pc-proxmox2 kernel: QLogic Fibre Channel HBA...
  5. M

    vzdump mode failure - unable to detect lvm volume group

    Here is the output when that is attempted: proxmox3:~# qmrestore --unique --storage iscsi_vm /backups/vzdump-qemu-114-2011_04_07-13_49_31.tgz 135 INFO: restore QemuServer backup '/backups/vzdump-qemu-114-2011_04_07-13_49_31.tgz' using ID 135 INFO: extracting 'qemu-server.conf' from archive...
  6. M

    vzdump mode failure - unable to detect lvm volume group

    tom, ok, i've been trying to get this working with iscsi/network backing. i have followed the directions at http://pve.proxmox.com/wiki/Storage_Model. here is a quick overview of my setup. PM4 host: Proxmox 1.7 and iscsi-scst (also my iscsi target) (Node) PM3 host: Proxmox 1.7 (Master) PM2...
  7. M

    vzdump mode failure - unable to detect lvm volume group

    tom, Thanks for the response. I was afraid of that. Yes, all of the VMs are on an NFS share for use of the online migration feature. The idea is to reduce downtime. However, there seems to be an issue if, while in an attempt to reduce downtime through the online migration capabilities, one is...
  8. M

    vzdump mode failure - unable to detect lvm volume group

    Greetings! I am having a problem doing "live" snapshot-based backups using vzdump. When I attempt to do so, I receive the message listed in the title of this post. Subsequently, vzdump tries "suspend" mode instead. This causes unacceptable downtime. Here's some further information...
  9. M

    SCSI or Virtio Driver Issue: Windows Server 2008 R2 64 Bit

    Re: SCSI or Virtio Driver Issue: Windows Server 2008 R2 64 Bit [SOLVED] mmenaz, I had found a forum post referring to the ISO from the Fedora Project and was able to get this issue resolved. However, I wasn't aware of that particular wiki article. Looks like a good read. Thank you very much...
  10. M

    SCSI or Virtio Driver Issue: Windows Server 2008 R2 64 Bit

    I'm having trouble adding a SCSI or Virtio disk to a Windows Server 2008 R2 64 bit guest. The device shows as unknown in the device manager. Windows cannot locate a driver for the controller and; therefore, does not know what to do with it. Any suggestions? Many thanks in advance.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!