Recent content by left4pve

The QEMU prebuilt image contains a file named `agl-demo-platform-crosssdk-qemux86-64.ext4`.

Hi everyone. I'm looking for a way to run AGL as a Proxmox VM. Here's the official documentation about different ways of installation. 1. They provided a QEMU prebuilt image and kernel image, and the official way is to use qemu to bring the VM up 2. A VirtualBox image 3. An image which can be...

Here's my setup. pfSense is running as a VM of proxmox. `eth0` is associated `vmbr0`, and pfSense also has a virtual network device connected to `vmbr0`. There are two options: 1. Make the network device `eth0` VLAN aware, and configure a separate VLAN device in side pfsense. 2. Create a...

@vesalius Thanks for the reply. Now I'm really curious why it's working..The switch I'm using is Yuanley 8 Port Gigabit PoE. Could it be that VLAN it handled transparently in this case?

Sorry to bring this up again. I'm looking to do the same thing and I've now created the VLAN10 so that other VMs on the same PVE can join the VLAN using a tag(basically option 1 in this thread). However, other machines connected to the LAN unmanaged switch(which is connected to the LAN port of...

Update: VM connected to the same vmbr0 but with different VLAN id now can get IP from VLAN DHCP and can access the internet. This is the setup(though I'm using VLAN ID 10 in this case): PVE network: pfSense VLAN setting: pfSense interfaces: However devices connected to the LAN...

So I have pfSense virtualized as a VM inside PVE, and here's my current network setup and it worked fine(despite no VLAN) I then created a VLAN in pfSense using `vnet0` but with a VLAN id 20, and I turned on the `VLAN aware` flag in the PVE network config page. I'm not sure if the diagram is...

Hi guys. I'm running pfSense as a VM on a host with J4125 CPU. The LAN network is connected to a Gigabit NIC. When using kvm64 as the CPU type, I can saturate the NIC at around 940Mbps, which is expected. However if switched to `host` as the CPU type, I can only reach around 850Mbps. Could...

@dscapak Upon some investigation, it might actually be related to the Samsung 980 Pro 2TB NVMe SSD I'm using? This model(as well as other Samsung NVMes) is notoriously bad for the 0E problem, which is confirmed on my machine with `smartctl`. I'm going to order another brand and see if the...

Sorry for the silly question. I'm seeing exactly the same error as in this post. My screen is flooded with this error with even no VM is running. kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0 kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected...

No I haven't done anything like that.

The builtin memory test all passed without any problem, even several times. I then used the same SSD but on a different socket on the motherboard(previously it was M2P and now it's M2A). It's been three days now and I don't see any error even if I have a very frequent scrub cronjob. According...

After re-installing everything on a new SSD, the degraded error happened again within 12 hours.

@leesteken Got it. I'll start testing with another NVMe SSD.

@leesteken Uh, the data corruption happened again today. In `zpool status -v` I saw a lot of `Permanent errors` and the status of the rpool became DEGRADED again. Do you think if it's an indicator for a bad NVMe SSD? Even one in the VM disk. `rpool/data/vm-101-disk-0:<0x1>`