Search results

OK, I have no idea what happened with that LXC :rolleyes: As a test case I created a new Debian8 LXC, and was able to add the mount point. hmmmm...:confused: So then I created a fresh Debian9 LXC (which is what my original lxc was), and was able to add the mount point o_O Whatever, I must have...

Here is the error message; Job for lxc@110.service failed because the control process exited with error code. See "systemctl status lxc@110.service" and "journalctl -xe" for details. TASK ERROR: command 'systemctl start lxc@110' failed: exit code 1

arch: amd64 cores: 2 hostname: foobar memory: 4096 mp0: /mnt/foo,mp=/home/bar net0: name=eth0,bridge=vmbr0,gw=10.10.10.1,hwaddr=DA:EA:47:87:05:76,ip=10.10.10.220/24,type=veth onboot: 1 ostype: debian rootfs: local-lvm:vm-110-disk-1,size=8G startup: order=2,up=60,down=60 swap: 1024 unprivileged: 1

So here I am banging my head against the keyboard once again trying to get an NFS mount point into a container. previous post where I learned how to do it When I had PVE4.4 running I was able to successfully setup a bind mount point, but for some reason now with PVE5 running (fresh build) every...

https://bugzilla.proxmox.com/show_bug.cgi?id=1447

Thanks for the tip, but I was able to re-install PVE4.4 and then do an in-place upgrade to PVE5 with no issues. So I'm good for now with a fresh clean system :) BUT, for major releases I really like to perform a fresh bare metal install (I'm just running a home server so it's no big deal to...

Where to report the bug?? Wait till 5.1 o_O

re-downloaded the 5.0-af4267bf-4.iso, verified the SHA256 hash, installed on a different (newer) thumb drive, same result

WOW, tried one of the other drives in the system and...wait for it, geez it worked! So what could be wrong with the M.2 driver? As mentioned I had PVE4.4 running, same config, same install process, no changes. :(

Supermicro Micro ATX DDR4 LGA 1151 Motherboards X11SAE-M-O Intel Corp. BX80662E31245V5 Xeon Processor E3 1245 v5 Corsair Vengeance LPX 32GB (2x16GB) DDR4 DRAM 2133MHz (PC4 17000) C13 Memory Kit - Black MyDigitalSSD BPX 80mm (2280) M.2 PCI Express 3.0 x4 (PCIe Gen3 x4) NVMe MLC SSD (480GB) 4 of...

NOTE: there is another post with the same issue but in that case the issue may have been they were trying to install PVE5.0 Beta 2. ???hmmm??? Boot drive is an NVMe SSD tried both accepting all defaults and using custom drive config Using the same thumb drive that I had used for PVEv4.4 Used...

Hey all, I'm trying to perform a fresh install of Proxmox 5 on my server that I had been running v4.x on for some time now. I deleted all the partitions from all the drives, created a thumb drive, booted to the thumb drive, answered all the questions up to the where the next step is for the...

Good Grief :rolleyes: Just by chance I clicked on one of the tags that I had set for this post, low and behold I found my answer. I tested it and it works!! Problem solved in this post, I just needed the clearly written steps to setup a bind mount properly.

Reading back over my post, let me add; I have also read the NFS restrictions that Proxmox has implemented, and understand why they don't want to allow an NFS connection back to the main PXE volume, but I am not trying to map there, I am trying to get to a VM instead. I also read where apparmor...

o_O LOL You got me, what was I thinking when I wrote that ;) I was just syncing ID&IP numbers for illustration and to make easy to follow, those are not my real IPs obviously, I'll correct my original post. Thanx for pointing it out :cool:

Hey everyone, need some help in trying to figure this out as I have been banging my head on my keyboard for a week now trying to resolve my issue. The app I am running is a simple light weight program that preforms a single function with no user interactions and I have it configured to run as a...

solved my issue. Instead of selecting the default SCSI option for the hard drive (during the vm setup), I selected SATA and viola, os now boots upon completion of the install. I understand that PVE cannot anticipate all possible hardware configuration scenarios, but now it seems default values...

update: I've tried installing other linux ISOs as a KVM VM with the same result, install goes fine but upon restart of the vm, the proxmox bios just cycles in the console screen. And yes, I've disconnected the virt cd-rom image.

Installed a fresh PVE4.4 on Supermicro x11sae-m motherboard, 32GB DDR4 RAM, 480GB PCIe NVMe M.2 boot drive, other sata drives to be configured/used later. PVE installs just fine, have done it a dozen times now. I'm able to access PVE web page. I have been trying to create a Debian8 VM, install...

yes! Thank You! This was my issue as well, no network after fresh install (on new hardware). My motherboard has 2 NICs, and following your directions I found eth1 was up and eth0 was down, so just moved the network cable from one port to the other and viola!!!!