Search results

  1. R

    Proxmox on SD card

    You could wrap the tar -czf ... in a systemd unit and add a systemd drop-in configuration for whatever service that needs /var/lib/pve-cluster (I guess it's just pve-cluster.service) containing something along the lines of [Unit] Requires=the-tar-backup.service After=the-tar-backup.service
  2. R

    pvetest updates and RC ISO installer

    No need to do that - you can downgrade the package with: apt-get install pve-qemu-kvm=2.1-12
  3. R

    Help with stack trace! iommu related

    Re: Similar problem I can confirm that 2.6.32-96 is still affected (at least the oops). I am unsure if I can upgrade to 3.0 - is 2.6.32-95 compatible with pve 3.0 ?
  4. R

    Help with stack trace! iommu related

    Re: Similar problem I would presume that this issue will be fixed when the RHEL 6.4 kernel flows downstream (through OpenVZ) to proxmox. I'm still running on 2.6.32-12-pve, but I'll check -17 to see if it fixes the issue for me. If so, perhaps it will be possible to see what caused the...
  5. R

    Help with stack trace! iommu related

    Re: Similar problem According to a comment by a redhat engineer it seems that the problem (or something quite similar) has been addressed by Red Hat in their kernel-2.6.32-298.el6 . OpenVZ kernels (which I presume pve- kernels are based on) are still using the 279.9.1 build. How does one build...
  6. R

    Help with stack trace! iommu related

    Re: Similar problem The redhat bugzilla entry (https://bugzilla.redhat.com/show_bug.cgi?id=815998) has status set to "CLOSED DUPLICATE of bug 827193" , so I thought that there is a solution after all. The problem is that the bug mentioned seems to be private. Not sure if it's only for RH...
  7. R

    Help with stack trace! iommu related

    Re: Similar problem The system froze with the 2.6.32-15 kernel as well. Any more info I could provide? I could try to build the kernel with the patch from upstream (https://bugzilla.redhat.com/show_bug.cgi?id=815998), but I am unsure if there is a source package for the pve- kernel. Also the...
  8. R

    Help with stack trace! iommu related

    Re: Similar problem Hi, I upgraded and booted a while ago. The new kernel also emmitted the oops: WARNING: at drivers/pci/intel-iommu.c:2775 intel_unmap_page+0x15f/0x180() (Not tainted) Hardware name: PowerEdge R510 Driver unmaps unmatched page at PFN 0 Modules linked in: sg kvm_intel kvm...
  9. R

    Help with stack trace! iommu related

    Re: Similar problem I also have been hit by this bug. Kernel emitted: Sep 27 11:36:07 proxmox1 kernel: WARNING: at drivers/pci/intel-iommu.c:2775 intel_unmap_page+0x15f/0x180() (Not tainted) Sep 27 11:36:07 proxmox1 kernel: Hardware name: PowerEdge R510 Sep 27 11:36:07 proxmox1 kernel...

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!