Host is generally the fastest. The CPU type can't create new features, it only masks or unmasks the ones the real host CPU supports. Mitigations on/off is a separate thing that applies to the host kernel.
Turning mitigations off on the host might speed the whole thing up significantly, or not...
I do not understand what you are trying to do here. On the one hand you have imported a disk image to lvm-thin storage. The config file has sata0 being on an lvm-thin as well and yet you have added args to say there is a disk image in /var/lib/vz/images that is the same name as the image you...
Reading the MAC address from an Ethernet device requires software, namely the driver for the device. It is not externally visible like a PCI ID (typically the MAC is stored in non-volatile memory on the card). Since you passed the devices to a VM, no driver will be loaded on the host so the host...
I have never purged grub-pc or grub-efi, but I would think it is ok to remove since it is just a dependency package and only exists to bring in other packages that it depends on. Configuration files should be in the common packages. To be sure maybe do "apt install --reinstall grub-efi" before...
Could it have run out of space during the upgrade? It will download a whole bunch of files and then install them, so the final space used could be less than what was needed during the upgrade.
The tools are very well-tested and in 20 years of using Debian I have never had an upgrade leave...
How can I point out the possible problem with a reverse proxy if you neglect to mention that you use one? Not everyone does! And you seem to think this is a fine attitude.
Talk about annoying...
Seriously? You're asking for help. Which means you don't know the cause of the problem and the reverse proxy is right there in the path that is broken. Filtering based on what you think the problem is just misleads people who might try to help.
I thought the whole point of Docker was to be able to put a bunch of containers on a computer and have them be isolated from each other. Which is what LXC does. Using the exact same mechanisms but with different management schemes.
It tends to break in unpredictable ways when LXC or kernel or systemd is upgraded. Containers inside of containers. What is the point of that again?
Good for you.
So it is a newer variant. That's fine. The way you have turned tso off doesn't seem right. Did you verify it is really off with:
ethtool -k eno1
I'm betting it didn't really get turned off. The thread you linked to suggests something like this:
iface vmbr0 inet manual
<other stuff>...
Just to get clarification...you are running E1000 cards on the host or on the virtual machines? If on they host are they really E1000 (very old) or are they one of the newer variants? Did you try turning off the offload as suggested (some of this hardware has features that don't work right with...
Disable the VM with the passthrough so you can see what the error is. Most likely the PCI ID's are changing and something (commonly the network device) is no longer where the configuration thinks it is.
ETA: There are several threads here about AMD boxes and passthrough. Basically, most AMD...
1. Running Docker in LXC is not recommended. See the many, many threads here for why.
2. If you need the whole machine, why are you using Proxmox and LXC at all?
Maybe you should have asked the question that way in the first place.
You only need the efi packages for booting with an EFI BIOS and you only need the pc packages for booting from legacy BIOS. You need the common packages for both. You normally only get one or the other set, your setup is an...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.