Search results

  1. USB pass trough with equal vendor and device ID

    ....maybe this is similar to your problem? ...and follow that thread to the end for newer PVE...
  2. [SOLVED] Is Proxmox future-proof?

    You are dead wrong, sorry. Their goal is a business and this means growth. Even if you think with buying a license means getting insurance for future development, you're dead wrong. All the "BIG-Five" are shopping the world with vast amounts of cash, buying competitors (and their products) or...
  3. Anyone using a replicated NFS storage system?

    iSCSI wil be the fastest option, although with NFS you should be able to saturate a GBit-Link. Take a look into napp-it for a web-based management GUI ->
  4. Anyone using a replicated NFS storage system?

    ..what about using a ZFS based NAS/Filer with iSCSI? Use ZFS-Volumes on the NAS and export these as targets via iSCSI. ZFS will give you the ability to snapshot the targets this way.
  5. Installing PVE via Serva?

    By the looks the PVE installer does not see the boot-device as a cdrom. I cannot comment on using this particular PXE Installer/Server environment, but you could always try an alternate install based on Debian Wheezy -> If you can...
  6. Proxmox and zfs(onlinux) issue

    ...I *think* I've seen another topic around that issue floating around. The fix - in simple words - is to set startup and shutdown sequences for each component in the correct order. ...see:
  7. Homelab, software RAID with SSD-cache?

    ...cannot comment on this, as I am not using PVE+ZFS in a production environment and/or with heavy load. You might have a good point for VZ Containers and ZFS not being supported. I also like ZFS and found it very reliable, even on its Linux implementation. But i can follow your arguments...
  8. Homelab, software RAID with SSD-cache?

    AFAIK it will use the RAM as cache...all RAM there is, but I've never seen it causing the system to swap...also I've never seen ZFS preventing another application from sfarting with a "not enough memory" issue. Well, with ZFS the only thing that goes better than RAM with ZFS is ...even more RAM...
  9. Homelab, software RAID with SSD-cache?

    +1 for this option. As you already know your way with ZFS and tuning it for VM storage, this sound appropriate, doesn't it? I'd start with the Debian Wheezy install of Proxmox and - before adding PVE - install ZFS-on-Linux and apply that with LVM to the storage array as required by PVE.
  10. pve-headers install problem

    ..answering my own post.. - If not on a subsription, disable enterprise repos and enable no-subscription repos, as described in the wiki -> then do # apt-get update # apt-get dist-upgrade (this should get you...
  11. pve-headers install problem

    Well, I did not check versions but the OP stated that this was a fresh and clean install of PVE3.1 and the reported kernel version in use was reported as this one. However, if the repo is left out of the list intentionally...What procedure to get access to the actual kernel headers is the right...
  12. pve-headers install problem

    what does "apt-cache search pve-headers" give you? As I am not on PVE-3.1, I can't check, sorry
  13. ZFS or BTRFS for Proxmox 3.1 ?

    -> instructions as per wiki did not work? -> Edit: bummer!...what a coincidence..looks like you're not the only one... -> Edit2: check your /etc/sources/list ..pve-repos might be missing
  14. ZFS or BTRFS for Proxmox 3.1 ?

    ...this is not a real big deal. Based on your first post, I've gathered that you only want to employ a single disk. If you're happy with /boot being *not* on zfs, use the Debian way and use zfs for all filesystems on LVM, including root and storage
  15. ZFS or BTRFS for Proxmox 3.1 ?

    True, but the boot partition will not be LVM based and AFAIU the OP, zfs as the one-and-only filesystem is the requirement here.
  16. ZFS or BTRFS for Proxmox 3.1 ?

    ...if you only have that *one* and single disk, you could try and setup LVM on that disk first. You may need to install Proxmox via the Debian install method ...not sure if wheezy installer nowadays does support booting from lvm though. second option is to employ a small USB stick for boot
  17. no boot possible with LSI / IBM M1015 passthrough

    disable the ROM completely (enter at host boot) or flash the card without rom-file. I don't know if there are options in VM-Bios at all, like with VMware product.
  18. no boot possible with LSI / IBM M1015 passthrough

    not in that combination, but in general it should work. are sure that you have a vt-d capable system (CPU, mobo and BIOS settings)? If so, it should work....maybe try relocating the M1015 to another slot that is not located behind a PCIe-bridge. As for the USB errros...disable the USB...
  19. Fileserver "best practice" + proxmox to qemu 2 cents: With a real Fileserver (being virtualized or not) you want a RAID-like setup with your disks....otherwise you possibly just need a Filesharing solution, like install SAMBA on the host and you're done. Using virtual filesystems to tunnel all that to the VM is IMHO not a good...


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 your own in 60 seconds.

Buy now!