Search results

Yes, I know that I can resize the visible area, but I think it would be better when a scroll bar appears (how it was in the earlier versions) and you can scroll to see the other tags... That can be true, but I use the tags to label what OS is running in the VM / LXC and to which network the VM...

I think I have found a bug since PVE 8.4.16 and also in PVE 9.1.2: In the left bar / list, where all VMs are listed, the tags are not displayed well when they are too long to the actual width. No scroll bar appears and they are cut off and 3 dots are displayed. Is this a new display design or a...

I have played around a little bit now and I use Q35 for the machine type... And when I use: CPU Type: x86-64-v2-AES Machine Type: Q35-10.0 it works. But I want to understand what is the problem :)

Hey Sivat, Sorry for the long reply time (silvester and new year are not good in my family for doing IT things...) My node have an Intel i5-8279U CPU and I do not touch any configuration of the VM. I have tested x86-64-v4, there I got failure messages for missing CPU features and then I...

Hi to the proxmox community, I have updated my proxmox node from 8.4.14 to 9.1.2 and want to start a Windows 11 VM that I had installed before the update. It stucks in the boot process now (after the update) and I didn´t change anything in the configuration of this VM... With cputype=host it...

Can I patch these in-flight patches to my PDM? When yes: How I can do that?

Hi to the Proxmoxlers :) Is the development still in progress or paused / canceled? I ask because no updates come for a some weeks / one month I think and before there were coming updates almost weekly.

Now I have another problem but similar to that here: Now I can reach the pfSense with the prefix:: but now the VyOS does not answer to neighbor solicitation messages. It has joined the correct multicast groups for its addresses. (solicited node multicast) but doesn´t answer to the NS messages...

No, it is also not reachable when I use the first address "::".

But I have this issue only when I use the first address of the IPv6 prefix the "::", when I use another like "::1" I don´t have this issue. And when it is an issue from freeBSD why I don´t have it any time? I don´t update any of the pfSense routers with patches or anything.

But it doesn´t work.

Hey, but I don´t understand why the MikroTik / VyOS is joining a solicited multicast address for an address which they don´t have? And when it isn´t something with proxmox why it began after a proxmox upgrade? (I think so) But I also think it would be a very strange problem when it comes from...

But I have the ip -6 neigh show here: $ ip -6 neigh show fd26:ab4d:3844:1000:: dev ens18 lladdr bc:24:11:ce:82:4f router STALE <- Wrong MAC address! (From the second router) fe80::d807:c4ff:fec1:e068 dev ens18 lladdr da:07:c4:c1:e0:68 router STALE fe80::be24:11ff:fece:824f dev ens18 lladdr...

But what I find very strange is why it is work sometimes and sometimes not.

I think the second router is joining the solicited node multicast address group for the <prefix>:: although he doesn´t have this address.

The working state was not for a long time :( On my other proxmox node (not upgraded, but I didn´t see anything in the updates that is associated with networking) it is the same issue. And now I have more details: The neighbor solicitation points to a wrong MAC address! There are more than one...

I upgraded now the proxmox. At the moment it is working but I don´t know how long that will be so. But I´m now unsure what the originator was.

I can do that 1. Ping (DIFFERENT ADDRESS warning!) 2. Routes And I captured the packets outgoing and coming in on the pfSense machine, and no echo requests are there, but Neighbor Solictitation messages to that aren´t a advertisement message is there as reply, so like the pfSense doesn´t have...

No help here anymore? Or did I understand something wrong?

Oh I didn´t see that with the language because in the proxmox datacenter manager forum was also answered in German. But for your question: The pings succeeds, but the ping answer comes from a wrong IP address. From the IPv6 address host address itself. The interface is configured normally with a...