Search results

If the interfaces are in different subnets, then the IP of the http server will tell the kernel which one to use. That's how routing works.

The official method for upgrading is here: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 Perhaps reviewing it will reveal a step that was overlooked. Did you see any error messages during the upgrade process?

DHCPOFFER of 192.168.48.100 from 192.168.48.1 DHCPREQUEST for 192.168.48.100 on eth1 to 255.255.255.255 port 67 DHCPOFFER of 192.168.48.200 from 192.168.48.1 DHCPREQUEST for 192.168.48.200 on eth0 to 255.255.255.255 port 67 DHCPACK of 192.168.48.100 from 192.168.48.1 These two ports are getting...

Again, from your log it appears that there are multiple interfaces on the same subnet. If they are not actually all connected somehow, this can't work as you want it to (and is a bad idea to begin with). You can still do what you want by only connecting one interface during installation. IOW, I...

To be clear, did you upgrade the Proxmox packages to PVE 9 or did you only upgrade the Debian packages? If the latter, you need to do the former as well.

Having a bunch of different interfaces on the same subnet with incomplete reachability between them is...sub-optimal. As you've noticed, since they are all on the same subnet the Linux kernel assumes they are equivalent and will just pick one to use for any given transaction. Maybe disconnect...

You are running Debian "buster", which is six years old and out of support for a year. Debian generally moves old releases to an archive repository. You will need to update your sources.list files to point to "archive.debian.org". See here: https://www.debian.org/distrib/archive There also...

Apt will ask if you want to keep the current configuration or replace it with the package maintainer version. It will offer a couple of other options including showing the differences.

I don't make the rules.

If a machine can't reach other cluster members it restricts changes so that when it gets back into the cluster there aren't conflicts. That's just how it works, as discussed a million times in this forum. Set up a q-device as recommended in the manual (which is liked at the top of the gui) and...

Personally, I just minimize how much I customize PVE and back up /etc. I recently replaced my Intel server with a much newer AMD one and this approach had me back up pretty quickly. No worries about requiring different firmware packages or different devices that need a rebuilt initramdisk and...

Maybe check the manual. It is linked at the top of the PVE web page. https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_import_virtual_machines

Mainly it is another thing to troubleshoot when things don't work. Stuff like "I changed the DNS but the new IP isn't being used" type of things two years later when you've forgot about the cache. Honestly, this whole discussion is kind of dumb.

Upated to PVE 9.x this week. I just wanted to let the Proxmox staff know that I appreciate them fixing the mobile web interface so it works on Firefox/Android.

The fact that it works with IOMMU disabled kind of says otherwise. Plus the fact that the kernel is binding vfio to the device says it thinks the device is being passed thru. What does "lspci -vmm" say?

The new disk is likely in the same IOMMU group as something you are passing through.

To be clear, the studies @bbgeek17 refers to are about using nvme-over-tcp vs iscsi on the host. It doesn't speak to whether nvme emulation in qemu would perform better or worse than virtio-scsi.

A lot of this kind of stuff is in qemu because people want to use it to do system emulation during SW development. It doesn't mean that it is performant or that it makes sense in a production environment.

The virtio-scsi device does not emulate any real device. That's why you need a special driver for it. What benefits could you possibly obtain by making it more complex?

Proxmox does not have a "desktop". It is a server OS and is mostly managed remotely via the web browser or SSH. It also does not have DHCP enabled by default so you will need to set a static IP by editing /etc/network/interfaces and /etc/hosts. Pick an address that is outside of your server's...