Search results

If proxmox-boot-tool status shows your system boots from UEFI, then the options should be in /etc/kernel/cmdline You can check if option is taken into account : # cat /sys/module/usbcore/parameters/autosuspend -1

The linux kernel is running within a virtual machine with UTM (https://mac.getutm.app)

Thanks, but all credits should go to @Tux_1024 (I only `apt install proxmox-ve` what he packaged), then got issues with apparmor (I'm have to make my homework on this) Excited too, and 64GB macbooks are near already here ^^ (okay, letting a 120hz display closed isn't a good idea), and the "Mac...

Finally got a debian lxc container running on my m1 macbook : https://forum.proxmox.com/threads/how-to-run-pve-7-on-a-raspberry-pi.95658/post-425043

First thank you @Tux_1024, I get it to also works on Apple m1 MacBook using UTM (apparmor didn't helped...)

nice catch, so now I need to be able to run a Debian Official Cloud Images using Apple Virtualization framework (both intel and arm), as used here : https://github.com/evansm7/vftool and here https://github.com/gyf304/vmcli And finally follow the guide linked by @fpausp : root@armVM:~$ curl...

I agree with you for a production use, but as a developer, being able to have a proxmox (or even a cluster) right inside my (m1) macbook is really interesting, and having the same on my desk with few raspberry pis can allow to do some cluster testing easily (switch off one Pi for example)

a pi 4 cluster for playing could be very very cool :cool:

Help for anyone having this boot issue: got this while zfs-initramfs have been installed from debian backports (version 0.8.6-1~bpo10+1, due to invalid priorities) instead of pve version 2.0.4-pve1 Solved it by doing a rollback to last zfs snapshot of rpool/ROOT/pve-1 (when zfs helps fixing...

I got an ubuntu focal running on my m1 arm macbook air with https://github.com/gyf304/vmcli Does developing on macOS (ok... proprietary hardware and software, sorry) using a virtual machine would be easier ? One ubuntu (or debian) VM to compile the kernel, and copying it on the host to boot it...

ended up stopping the container, renaming the zfs FS, destroying the container and creating it again, copying /var/lib/docker from old FS to the new FS, and it works...

hmm.... tried to create another container # cat /etc/pve/lxc/1094.conf #test-docker arch: amd64 features: nesting=1 hostname: test-docker memory: 4096 net0: name=eth0,bridge=vmbr0,gw=10.1.0.1,hwaddr=02:37:82:7c:95:78,ip=10.1.0.94/24,type=veth onboot: 1 ostype: debian rootfs...

Having a unprivileged lxc container running docker container fine with 5.4.78-pve kernel Made the kernel upgrade, docker container can't start after, here is the error : docker run hello-world docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting...