Search results

Um, 1 gigabit = 1000 megabits = 1000/8 megabytes = 125 megabytes. With overhead and required dead times between frames 100 MiB is about what you would expect on a gigabit LAN. ETA: The OP has a 25 gigabit LAN.

Do you have the qemu guest tools installed inside the Windows VM? It is required otherwise Windows has no driver for virtio-scsi. If not you could try one of the other SCSI options or SATA.

In case your cluster hosts aren't identical. You can choose a lowest common denominator.

Maybe shutting down your PVE and pinging its IP would be a better way to detect a duplicate IP.

Man, this brings back memories of Usenet.

It will shut down VM's and containers. You shouldn't need to do anything.

There are build errors compiling the driver. Seems that some struct definitions are not as expected. This usually means you have the wrong version of the driver for the kernel you are building for. It appears that Release 470 is going on three years old so it would almost certainly need an...

Adding virt-manager to your existing Fedora would be simpler. Then you don't have to mess around with dual-boot. You could even put PVE into a VM to experiment.

I also found this bug from May 2024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071562 Seems like it might be similar to what you are seeing. I'm using a stock Debian 12 VM as the server, so it has kernel 6.1.0-26-amd64. The client VM's using the server are likewise Debian, although one...

I would try that. I have both set to "-N 2 -N 3" to only allow NFSv4 and it gives: -3 +4 +4.1 +4.2 (v2 is disabled by default). Seems like it should work to disable v4 as well. If not it would still be a bug I think.

That bug report is 9 years old and supposedly the bug didn't affect systemd (only sysv-init). Are you sure you used the right syntax? RPCMOUNTDOPTS="--no-nfs-version 4" RPCNFSDOPTS="--no-nfs-version 4" WITH the quotes? The file /etc/default/nfs-kernel-server is a shell script fragment so you...

Do you not believe the memtest result? It is a more thorough test than most BIOS provide. Plus, your symptoms sure could be caused by bad RAM. I would get a new RAM module and start swapping until memtest passes.

Being full won't prevent it mounting. The filesystem being corrupted might. Did you try running fsck on it? What filesystem is it anyway? OTOH, an I/O error could mean the disk has gone bad. ETA: Have you run SMART tests on it?

Does they disk have partitions? Maybe you should be mounting one of those instead of the full disk.

So your advice is at best very incomplete since uploading some ISO files is something a new user will want to do very soon after the install. Your personal use-case of being the forum gadfly and messing around with PVE to find bugs or design choices you disagree with is, shall we say, a minority...

Cables, controller, disk, power supply. The usual suspects. The SMART test tells you the disk thinks it is working fine, which points to one of the other culprits.

That is terrible advice to give a beginner. The journal will grow up to 2 GB by default, you need space for uploaded ISO files and the like, apt/dpkg will take significant space for their database, plus you need space in /var/tmp for making backups. 32 GB makes a lot more sense for most...

Yes, that is the proper way.

Seems like a pretty niche request. You might be the only person in the world who gets an IEEE address assignment for a hypervisor rather than for hardware you are manufacturing.

Isn't an OVA just a ZIP file that contains the disk image(s) and an XML file describing the device configuration?