Search results

i tried PVE Edge 6.0.6-1 with latest firmware/microcode .It's not better . VM with docker crash in a day..But pfsense VM has not crash yet...

Well, i after the "official" 5.19 who crash my server when the vm start, i try PVE Edge 5.19.14-2 I also disable c-states il the bios, and the balloing for the VM. I hope it's more stable. But i had tu use cpupower to lower the frequency, unless it was 2800 all the time ( N5105) ( kernel...

Configure a share storage which is available for the 2 two cluster with same name. you can do a live migration of the disk to this storage. you shudown the vm. copy the config file via ssh to the other cluster, maybe modify it if needed start the vm on the new cluster . you can do a live...

i have the same issue. DHCP + Bridge + bond balance-rr doesn't work. but with DHCP + Bridge + bond balance-tlb it works. For my boot on San serveur, its' a problem.. Any idea? PS: my switch doesn' support lacp ...(BUFFALO BS-MP2008)

I agree for the part that raid ZFS over consumer disk is a bad idea. i try and the wearout is massive. So i go back to my "old" install of proxmox over a raid 1 debian with mdadm, with a nvme disk and a Sata. The cool stuf with it is the option "write mostly" ...

i Know, that why i want to try this kernel...

this is the log the boot start at Sep 19 18:34:07 et crash at Sep 19 18:36:24 in the log we can see , the host try to start container lxc-224 and crash ( 18h34 ), and with kernel 5.15, no problem it start after lxc-175 ( 18h43) arch: amd64 cores: 2 features: nesting=1 hostname: Proxy memory...

With the 5.15, host stable, and one vm ( debian with container ( bitwarder ) crash. No problem with oher Vm / lxc. with 5.19, the host boot, but it seem that when it start lauching the VM /lxc , the hosts crash. i watch quickly, the log, and maybe it's a storage problem ( Nfs ganesha over...

I try to install it on my N5105 server , and it crash after booting with this version of 5.19

I try the 5.19 pve official. Proxmox freezer only a few seconds after it finish the boot. Back to 5.15 Official. With this one only the vm freeze not the entire server

i am still with the stock kernel. I put only one core and force cpu type host ( before 2 vcpu and kvm type) for the VM with container and no freeze for two days.

that's the one... but no try myself ( yet). the next crash i try.

i think it's a problem between the cpu model and the container. I have the same problem. before i have Intel Apollo Lake N3450 / with debian Vm with docker for bitwarden.E verything was working as expected i migrate on n5105 ( the same cpu branch a you ) and the vm crash . So far 2 times in...

on the screen the enp2s0 don't exist, so you can't add this card to the bridge. you only have enp1s0f0,enp1s0f1,enp1s0f2,enp1s0f3

I have replace my cluster of 3 x (Intel Apollo Lake N3450 8 Go ), with one N5105 with 32Go. So far i have no crash of the Hypervisor itself with stock kernel ( uptime 10 Hours), but i have perhaps one Vm ( container with bitwarden) with probably the same problem as bobbyrc. The VM crashed, and...

the conf : /etc/vzdump.conf tmpdir: i think you can see the path il the log of the backup job something like that: INFO: Upload config file '/var/tmp/vzdumptmp290473_175/etc/vzdump/pct.conf' i think the default tmpdir is /var/tmp , but you can change itin the /etc/vzdump.conf file

And the tempory folder like smecio said ??

Mdadm is the software raid. Do you have a raid over the iscsi disk? The iscsi lun is bootable? The network card is in the boot order in the bios? You use ipxe?

i have this running right now. Proxmox installation over a debian on boot on San ..Now piece of cake , you can directly install debian on isci Lun with the debian installer. for the record i use Pfsense for the the dhcp serveur / tftp / ipxe file..

Like l said it's my computer(workstation) @ home ...;) Whenever the method you use, giving the power to shutdown proxmox is a bit of risky