Search results

Thank you. I missed your reply, but this indeed solves the issue! Thank you very much.

Thanks. This instantly resolved our issues with IPv6 neighbor discovery on VMs running on our platform! We had intermittend issues with machines unable to reach machines within the same subnet over IPv6. Disabling multicast_snooping on the hypervisor fixed it!

Nobody that can help me? I've tried to disable zeroing on the LVM thin with "lvchange -Zn vg/lv", but that doesn't resolve the issue. Could it be that it's the Proxmox tooling that is zeroing the drives before it actually starts the data transfer?

We have a Proxmox VE cluster with 3 nodes, all using local storage. Using local storage is a choice we made due to some issues in the past with different storage solutions. When we migrate a machine from node A to node B we are seeing IO-issues occuring on Node B. It's SSD drives are saturated...

Hi, I just wanted to inform the Proxmox team about an issue with the virtio network drivers. My setup consists of: - 1 Proxmox Hypervisor (Debian 9.11 with all updates, including those from Proxmox). 3 bridge interfaces. - 1 application proxy (apache with http_proxy) with 2 if's (1 external, 1...

The issue he was facing is not related to the GPG key. It is because 2 zfs packages contain the same file: trying to overwrite '/etc/default/zfs', which is also in package zfsutils 0.6.5-pve9~jessie The solution is zo uninstall the 3 packages I mentioned (and optionally reinstall them...

To be of assistance instead of telling people what they did wrong, here is the solution to this problem: Run: apt-get remove zfs-initramfs zfsutils-linux zfsutils Afterwards, run: apt-get -f install apt-get upgrade To finish the installation.

Thanks. That works like a charm. Only issue now is that the container doesn't have quota/diskspace limits. Can this be fixed? I see a patch from 2009 for disk cgroups, but as far as I can tell that patch hasn't been merged into the kernel. I dont think regular quota's can be used because the...

I did some additional research, and apparantly the default backingstore for LXC is "dir", what is basically the OpenVZ way instead of disk images. Proxmox seems to prefer "loop" type devices. I would like to change this behaviour but did not find a way to do this yet. I did try to update the...

We recently installed a machine with Proxmox 4 to try the new LXC system. I have a question regarding storage. With OpenVZ the filesystem of a container would be in /var/lib/vz/templates/<vmid>/. This was ideal for quick maintenance and backups. We could just backup the proxmox host instead of...

You need to configure multiple multipath's in the multipath config: Determine the www by using: /lib/udev/scsi_id --whitelisted --device=/dev/sda /lib/udev/scsi_id --whitelisted --device=/dev/sdb /lib/udev/scsi_id --whitelisted --device=/dev/sdc And then add these ID's to...

The package versions can change, as Debian Wheezy is not declared stable yet. So yes, you should use 0.97-67 instead of 0.97-66. I just grabbed the new grub (required for multipath boot) and looked at the dependencies it requires. I took grub packages instead of grub2 because squeeze uses...

Hi Petrus, 1. The package behave just as any other package, except it has a higher version number. Thus, should there be an update in the squeeze repo, then it will not be updated. However, it is very unlikely that these packages get an update. Most debian updates are security fixes in...

What I know for sure is that the VM that originally had this VM, never ran on proxmox2. So the "VM 111" (from tap111) must be another VM. That VM was in the same VLAN (402). VM 111 was also migrated without issues. Either using the GUI or using "qm destroy", I did not simply remove the config...

You are confused with disk images and partition. A disk image (.img, .raw, .qcow, whatever) is "a harddisk in a file". You create one or multiple filesystems on that "virtual harddisk" just as you would on a real harddisk. So, if you create a 15 GB "virtual harddisk" and deploy a 10 GB partition...

You could mirror the Proxmox Debian repository (http://download.proxmox.com/debian) onto a local server, and update your Proxmox's /etc/apt/sources.list to point to your new server. Thats the easiest solution. The more difficult version is to download all the required .deb's to a USB stick, and...

Oke, lets assume that it ran on this host some time. That doesn't explain my issue. I basicly have 2 things I dont understand: - Why wasn't the TAP interface removed when the VM was destroyed/stopped? - What is answering the ARP requests? Why is the dom0 doing this instead of the VM? In my...

It looks to me you should ask this in a Pound support forum, not Proxmox. But this setup isn't gonna work even if you manage to configure Pound properly. The VNC console uses a separate port (500x where X depends on the current active console sessions) outside of Pound and/or the Proxmox...

VM 111 does not exists anymore in the cluster. It is possible that VM111 is the old VM that used this IP. This VM was removed from the cluster (using the "Remove" button in the interface or qm destroy <vmid>). I had the exact same issue with yet another VM that was also migrated. None of the...

We've had some issues with our shared storage, so I've migrated some VMs to another proxmox server using local storage. Since this migration I am having network issues, which I boiled down to yet another proxmox server doing ARP replies for a machine that was never even on this proxmox server...