Search results

Hi Stoiko, Thanks for the feedback. When I booted the Windows Server 2022 guest after shrinking the disk, I did not get any error messages about a missing GPT table, so hopefully that is a good sign? Speaking as a new ProxMox fan, I wish you guys would enable the shrink option through the GUI...

The ProxMox CLI says, "shrinking disks is not supported." I did it manually and it seems to have worked fine, but maybe I made a mistake and I just don't realize it. I have PVE 8.0.3 running a Windows Server 2022 guest with a 2 TB drive 0 and a 6 TB drive 1. Drive 0 is partitioned as a 50 GB...

I'll try that next time. Thanks.

I only had console access to the server, so I could not copy and paste the output. I also didn't want to type the whole thing out by hand to post it here, so I took a picture of it and ran it through an online OCR process. The OCR mistook a lot of the zeroes for "ohs" and I had to change them...

Thank you for pointing that out. I thought the destination was zpool0, which has plenty of space. The guest has 2 disks. One of them is 6TB and that one migrates fine because the destination is zpool0. The OS disk is the problem because it is trying to go to local-lvm. That said, I recall that...

I believe so. Here are the details from the destination ProxMox. root@vmhost52b:~# pvesm status Name Type Status Total Used Available % local dir active 67157384 4433040 59267116 6.60% local-lvm...

Greetings, I failed to migrate a Windows Server 2022 guest from PVE 7.3.3 to PVE 8.0.3. It failed with the following message. drive-ide0: transferred 80.2 GiB of 2.1 TiB (3.82%) in 6m 8s drive-ide0: transferred 80.2 GiB of 2.1 TiB (3.82%) in 6m 9s drive-ide0: transferred 80.2 GiB of 2.1 TiB...

Hi, I shared the contents of /etc/network/interfaces in my OP. Here is /etc/hosts... root@vmhost52b:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.8.110 vmhost52b.mycharts.md vmhost52b # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost...

I followed those threads and they were so complicated that I almost despaired. Then I found the Custom Schemes section of this page. Surprisingly, it worked on the first try. Thanks! https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES

Today I upgraded an older version of PVE 7 to the current version, rebooted, and everything went fine. Then I upgraded from the latest PVE 7 to PVE 8. Afterwards, the NICs do not come up. It also looks like it renamed the interfaces. How do I bring this thing back up? # ip link show 1: lo...

Never mind, I captured it with tcpdump. It's shop.proxmox.com (79.133.36.249). The subscription is now applied.

I bought the subscription from the ProxMox web site. I'm hoping someone from ProxMox will see the question. Thanks anyway.

Thanks for the feedback. When I click the "Upload key" button, it spins for a while and eventually pops up a dialog that says, "Connection error - timeout." I assume this is because we block traffic to sites outside the United States by default so it cannot reach the registration server. Is...

We've been running the free version of PVE 7 for a couple of years. We just purchased licenses, but we can't figure out how/where to apply the license.

Yep, you're right. The instructions for Debian worked fine. When I originally tried it, I had trouble with apt-get pulling down the repo data, but I worked around it. Thanks for checking.

We use OSSEC HIDS as part of our security architecture and it was easy to install on everything except PVE. I can't find instructions anywhere. I'm checking here on the off chance that someone has done it before.

That is exactly right, I do use zfs! It's okay with me if zfs uses lots of ram for the ARC as long as it releases it when apps or VMs need it. Is that the expected behavior?

My PVE 7 server has 1 TB RAM. There are only 6 guests running. 4 of them have 16 GB RAM each, the other 2 have 2 GB RAM each. That works out to 68 GB total. Why does the summary screen in ProxMox show 452 GB RAM in use?

Never mind, figured it out. I just have to select the target storage from the drop-down instead of accepting the default, which is to get it from the backup configuration.

I backed up a VM located in folder /main_pool on PVE server VMHOST01 to an NFS share on a different server. Now I'm trying to restore it from the NFS server to folder /zpool0 on PVE server VMHOST02. However, when I attempt to restore the dump, I get an error message that 'main_pool' does not...