Search results

I finally found that the proxmox hwoto 5.x to 6.0 is missing some information: actually the configuration files do interfer with the proxmox VE upgrade. As I had forwarding in the sysctl for the pfsense. After upgrade it was gone.... thats why I had the problems.

I experience the same by going form 5.4 latest to 6-2.12... pfsense wont come online. I changed CPU from host to kvm64, but no significant change.

I have the same thing, boot gets filled up. autoremove does what ever but does not touch boot. after deleting some old stuff in boot I managed to finish apt --fix-broken install since it was even for autoremove complaining about the abroted install and no free space on boot. then I purged like...

so, after monitoring this closly the past (3) hours, my swap is building very very slowly now, currently at 130MB. It semas, as my RAM is used at 52%, that still, the Kernel swaps stuff from an half empty RAM to SWAP. With swappiness = 0. I just dont understand why or what I did wrong. In...

I just noticed, that whil waiting for swapoff -a && swapon -a to clean out the swap files, that my RAM consumption on the host went up to 94%. This would account for the swap build up. I just reduced the RAM on many of my VMs where I saw that the VM did not even use 50% of the allocated RAM...

I run: Linux 4.15.18-9-pve #1 SMP PVE 4.15.18-30 (Thu, 15 Nov 2018 13:32:46 +0100) on a 8 x Intel(R) Xeon(R) CPU E3-1270 v3 @ 3.50GHz (1 Socket) While I do use aobut 80% of RAM for the VMs there are still 6gb free. But with the Mailserver VZ (Kapano) i see this First I gave the VZ all the...

for what its worth: so when you end up editing the config file, and then starting the ct and the config jumps back to the version of before, you know your working the wrong file. or, for google purposes: lxc.mount.entry keeps disaperaing from config file this is all about mounting an host dir...

found it look at row 60 of this file: /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js first of all, I just killed all not used languages with double dash '//' (even en) as the default still exists so now I got English (Default) and German.... that is a start. I'll just have to...

I would like a better thing than to replace the en files with the preferred local files. Since waiting for a interface to change the language every time at login is annoying. The software serves me, not the other way round. And also I am fluent in English; I rather have it in German. And I do...

works like a charm, for me it was for my test server for OMV4

sure could, both is based on debian as base OS but then who would want to maintain both debian deriavtes intermixed and make sure they dont kill each other? More important, dont open up some holes for crackers to highjack my machine. I started with proxmox (because of the the proxmox kernel...

sure, but it does not offer the nice klicky bunty (GUI) option, and im sick of every time starting a putty and sshing into a server to change some file access rules. WEB GUI is a nice solution for such stuff. and OMV got the best ratings for NAS Storage OSs So I wanted to run the OMV as a VM...

Anyway, next time I stay with standard hardware. Could build a micro server as efficient as the HP from any standard mini ITX Hardware. Only the ILO of HP is a nice option, but im sure there are some other options out there too. I just never checked it out.

sure, I switched operating systems. away from proxmox, I use OMV now. OMV is a native file storage system and provides also a virtual enviroment with virtualbox and many other addons. Since now the File Storage is native on the machines OS, I dont need to pass through the Raid Controler to any...

Thanks Patrick, im off PVE now, as I could not make PCIe passtrhough work, due to some things HP did to their hardware unsing parts of the PCIe addresses for other things like health reporting. So I cant further report on this issue anyhow, as Im moved away form Proxmox to Deb7 with...

for your info, dmesg only gave this away after i did all the modifications i mentiond above, ive been on this for about 3 days now. and now: f*cking s*ite ive found it! Its a F*CKING HP problem. Its related to a conflict of adresse via PCIe and RMRR. RMRR is used by HP to communicate some...

now i did try blacklisting of the kernel driver of the RAID modul (hpsa) and did acording to this https://forum.proxmox.com/threads/cant-blacklist-mpt2sas-module.26950/ the # update-initramfs -k all -u after updateing the blacklist.conf by adding "blacklist hpsa" no sucess then i added echo...

i made a litte progress.... my fans start to go ape when i issue the comand echo 0000:07:00.0 > /sys/bus/pci/drivers/pci-stub/bind I did follow this post: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM and first did load pci_stub with the command modprobe pci_stub I...

and this is the verbose output of lspci -vvv for the RAID controler. In know that passthrough works for the HP420 with the HP version of VMware ESXi. 07:00.0 RAID bus controller: Hewlett-Packard Company Smart Array Gen8 Controllers (rev 01) Subsystem: Hewlett-Packard Company P420...

Just for test I changened hostpci0: 07:00.0,pcie=1 to hostpci0: 03:00,pcie=1 if you look in the first post, its both of my NICs. I then started the VM and my websession to the PVE GUI went dead instantly. So i switched to the server itself and run qm for the 200 vmid, but the vm was dead...