Windows7ge

I know when you run update-grub from the OS it can find other bootable partitions but if you don't have access to it...not sure.
 
I wonder if you could update-grub from another drive or if that would only move the problem to another disk. (Not a solution)

It might work or it might not.  But it should be the first step, as it makes subsequent action (involving others) better for you. 

You tried to solve the problem yourself in a professional manner. 

Don't overthink this. 

Establish your personal boundaries and politely enforce them. 

Warehouse manager here, I tell forklift operators what to do all day and have dealt with a very similar scenario.
If your boss isn’t listening, go to their boss. If their boss isn’t listening, go to theirs and so on.
Call them out in a group, as large of a group as you can. Let it impact your work and relay it to your boss when they start to question why your work quality is poor. Your boss may not give a shit about personal interaction but they absolutely have to give a shit about numbers and productivity. If one asshat is bringing down productivity, that will gain attention quickly from a chain above your boss who will want answers.
 
The biggest one though is to make it as public and visible as possible, get everyone’s attention on the matter to make sure they know. A lot of times stuff like this is glanced over regardless of severity because people just don’t want to be involved. When it goes unchecked it can escalate and nobody wants that.
Dont interact with the person if they start some shit, fuck off somewhere else directly to other people or management and relay the issue. Every single time it happens, do it again and again and again until it becomes a known issue.
 
Seniority means nothing as far as workplace etiquette and demeanor goes. Everyone is expected to act respectfully and civilly to eachother wether they’ve been at the workplace 20 years or 2 weeks. I’ve outright told my operators union rep before to get the fuck off my dock because they insisted on yelling at a new guy. Grieve me, I’ve got you on camera harassing a newbie. Doesn’t matter who you are, it’s unacceptable behavior.
 
Tldr
-don’t interact or respond to the person in any negative context
-every time they try and start, immediately contact a manager or larger group of people
-call out even the tiniest hints of it when you’re in a larger group with this person
-continue to pursue the issue with elevated management until it’s resolved 

Try to privately talk about it with the person first. 

"Hey can we talk privately for a few minutes?"

"Did you notice you often do X.  X makes me feel uncomfortable.  I am hoping there isn't an issue, and X can stop."

He's picking on you to make himself feel big and tough. Assertively verbally defend yourself next time he throws a hissy fit about some minor perceived sleight or butts his nose into your business. He might move on to an easier target.
  
So you're saying you have witnesses.
 
If it persists, go over their head.

Best is to first confront the person and tell them you don't appreciate how they treat you. If it continues, then time to go up the food chain until someone finally listens and steps in to correct it. 

Depends on the switches used:
 
If your unmanaged switches lack Spanning Tree Protocol (STP), adding a second cable between them creates a bridging loop. This saturates the network, rendering it unusable until the extra cable is removed.
  With STP-enabled unmanaged switches, only one of the switch-to-switch links is active.
  Manageable switches allow port aggregation/trunking for a speed boost slightly below the combined speed of the aggregated ports, accounting for some aggregation overhead.

Since I didn't see it mentioned anywhere, for the curious. The OG Whonnock server chassis was a NORCO RPC-4224.
 
 
Time sure flies eh? The NORCO 4224's do have some quirks but I don't inherently think are bad chassis. Getting one today isn't worth while though. You can still find them but the prices are stupid. Overall if you have one or one's being offered for cheap I think they're worth getting/keeping.

Since I didn't see it mentioned anywhere, for the curious. The OG Whonnock server chassis was a NORCO RPC-4224.
 
 
Time sure flies eh? The NORCO 4224's do have some quirks but I don't inherently think are bad chassis. Getting one today isn't worth while though. You can still find them but the prices are stupid. Overall if you have one or one's being offered for cheap I think they're worth getting/keeping.

The EPS 4 or 4+4 pin powers the CPU. It could point at a board problem involving power delivery to the CPU. i.e. the VRMs.

CPU's are normally quite resilient so more than likely it's something with the motherboard.
 
Have you tried an open testbed (motherboard box) with the setup:
No GPU One stick of RAM. Motherboard 20+4 pin w/ 8-pin EPS Absolutely nothing else connected to PSU. Same behavior or does it turn over?
If you get the same behavior:
remove CPU 8-pin. Only cable attached to anything being the 20+4. If at this point it still does the same thing I'd have to pronounce the motherboard dead assuming you don't just have a shorted fan. Would the board happen to still be under warranty?

That's strange considering you shouldn't need to blacklist the driver to blacklist based on Device ID. It defeats the purpose.
 
If you're saying you find you can turn the driver back on system-wide but vfio stays on the device you want that's an interesting bug but if it works it works.
 
Even when I wrote this tutorial the devs didn't have official documentation on HOW to implement VFIO. They just told you how to enable the driver modules. Everything we do here is experimental and for the community. If you find something that works it's worth noting and sharing.
 
Myself I'm thinking of buying a Quadro P1000 and using it w/ GPU pass-through for light VM use. It supports NVENC Gen 6 so hopefully it works with PARSEC and being a Quadro I hope it doesn't require a monitor be attatched.

I decided to investigate what I considered the easiest method of network installing Windows but Windows XP is definitely depreciated. It's no longer supported.
 

 
You might, maybe get away with Windows 7 but you'd need a much older version of WinPE to try and do this with XP. Go forward with your current idea and let's hope it works.

I don't know what would make it specific to UEFI but from a retired proxmox staff members mouth:
This exploit was discovered a few years ago. These were codenamed spectre & meltdown. It has the potential for a VM to learn what the host OS is doing. Not necessarily explicitly what it's doing but clues gathered over time as it reads memory locations the VM was not mean't to have access to.
 
I will look into if I have an old .ISO or if I can find an archive but it looks like blacklisting the driver is still possible. It's just not ideal.

You're pretty close. An HBA is just a controller that provides an expansion of SAS/SATA ports. What manages the drives is up to the OS.
A RAID Controller is like an HBA but has the onboard functionality to create a array which is then presented to the OS as a singular drive.
 
To contradict RONOTHAN## a little due to what sounds like a bias...there are pros and cons to each solution. The industry as a whole is starting to migrate to predominately OS based RAID solutions. Windows has Storage Spaces, Linux & UNIX have various File Systems that provide RAID features. If you want to follow industry trends you can use OS based RAID. It's a perfectly fine option.
 
On the oppose side of the fence. Depending on your hardware you can use a hardware RAID controller. These have a theoretical limit as to how many drives you can connect (4, 8, 16, 24) but this is usually circumvented with what are called SAS expanders which in turn can proved more ports for more disks. The controller is designed to do one job really well which can alleviate CPU load. OS based RAID is CPU reliant. Depending on the complexity of the array you can be CPU bottle-necked but this usually isn't a problem you'll run into with a home server. Not nearly enough disks. Additionally if your RAID card fails migrating an array to another RAID card isn't a plug'n'play task. There's also issues with data corruption and what can be lack of error checking which is why you don't want to cheap-out if you use a hardware RAID card.
 
There's many other examples but it's not as though either solutions is superior really. Both have their pros and cons. Which is better is dependent on your use case and other hardware. Choice of OS. Etc...

@thesteamy It looks like I'm going to have to post a thread on the PROXMOX forums. I figured out one problem but now I hit one of the first issues you were having.
 
So for reference, MAKE SURE you install the OS in UEFI mode. Go into your BIOS and select UEFI Only and disable CSM. PROXMOX needs EFI (part of UEFI boot) to run the functions for this process. Furthurmore use ZFS instead of EXT4 as ZFS doesn't try to create an LVM which is a whole other can of worms.
 
Secondly. None of my prior methods for loading drivers into hardware devices are working anymore. update-initramfs -u -k all seems to do nothing even though I've gotten rid of the errors. I'll post a thread on their forums and update you if I get responses.

Yeah W10 22H2. Just typical windows bs installed (IIS, msbuild) and qemu guest tools. Weird thing is this seem to happen at random intervals too. One boot it’s totally fine and the next it’s all messed up. I am certain this is a windows thing but haven’t really had a chance to replicate it elsewhere. 

I would expect no but the behavior is strange. Tell you what, Saturday I can setup a spare box I have and we can try replicating the error you're getting on your version of PROXMOX. It's possible the procedure has changed and might require different operations. That happened to using QEMU/KVM on Ubuntu.
 
I haven't played with Balloning/dynamic RAM allocation but what I have noticed is Windows creates some file system in RAM and fills what you give it which means if the hypervisor gives it 16GB it's going to swollow 16GB but in the VM RAM usage is like...2.5GB. Very annoying. Haven't replicated it on Linux or UNIX. It's just a bad OS design for virtualization.
 
I generally static my RAM allocation for all my VMs only changing it as needed but I have dumb amounts of RAM to go around so conserving it is not really a neccesity. I have to help thesteamy I might be able to test the problem you're having at the same time. I assume Windows 10 22H2? I should be able to make Windows 11 happen. You can add a TPM module in Proxmox.

Let's see. I have pass-through working on 7.1-7. Same methods.
 
Did you update-initramfs after adding all the vfio drivers to /etc/modules then restart the server?
 
You can verify if the driver should load at next boot with:
lsinitramfs /boot/initrd.img-5.15.30-2-pve | grep vfio If nothing shows up the driver isn't going to load. I imagine the driver might show the unavailable error if it hasn't been loaded into RAM by the kernel.
 
Ah, onboard Intel X540. That might be in it's own IOMMU group if there's no 0a:00:02. At the same time the paravirtualization driver works very well on Linux/UNIX and the windows downloadable driver is good too if you end up not being able to pass this through.
 
I assume you copy/pasted the script and just modded where you needed it.
 
Alternativly there are the other two options to perform pass-through. The vfio-pci driver helps in certain circumstances but just loading no driver into the device can work as well. If you don't have another X540 you could just blacklist the Device ID 8086:1528, or if you know that driver is only being used on that device you could blacklist the driver system-wide.
 
So you can mix & match methods to get the result you need.

Sudo is for when you want to run a command with elevated privledges. Ie as if you were root. In Proxmox the only usable accout is root so sudo isn't needed. Don't know if I included that...
 
Make sure you have the correct kernel version in the command "initrd.img-5.15.102-1-pve". Proxmox sometimes has multiple kervel versions installed. When you run update-initramfs -u -k -all the output should list the kernel it's using. Here it doesn't hurt to try rebooting and seeing if that makes it work.
 
The ironic thing is I could say the exact same thing to others myself. There are a lot of special topics I don't understand that I have no-one to turn to for answers. That's why I write tutorials. To share my findings to help the next person.

Hello and thank you Windows7ge,
Im trying to get this running on proxmox 7.2-3, sorry I should have known to put that in original post.
 good catch, my dyslexia would have never seen that... but i still get the "FATAL:"
 
root@ProxMoxBox:~# chmod 755 /etc/initramfs-tools/scripts/init-top/vfio-driver-override.sh chown root:root /etc/initramfs-tools/scripts/init-top/vfio-driver-override.sh update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.15.30-2-pve modprobe: FATAL: Module vfio-pci not found in directory /lib/modules/5.15.102-1-pve Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. root@ProxMoxBox:~#  
Results from
lspci -nn 0a:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)
0a:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)
 
 
GNU nano 5.4 /etc/initramfs-tools/scripts/init-top/vfio-driver-override.sh #!/bin/sh PREREQS="" DEVS="0000:00:1f.2 0000:0a:00.0 0000:0a:00.1" for DEV in $DEVS; do echo "vfio-pci" > /sys/bus/pci/devices/$DEV/driver_override done modprobe -i vfio-pci #00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] - IOMMU Group 27 #03:00.0 3D controller [0302]: NVIDIA Corporation GP104GL [Tesla P4] [10de:1bb3] - IOMMU Group 33 #04:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 [1000:0097] - IOMMU Group 34 #0a:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01) - IOMMU Group 39 #0a:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01) - IOMMU Group 40  
 
I can't tell you how happy I was to see your response this morning. it was like a lighthouse on a stormy night. I'm so grateful for your guidance and help. Thank you.
 
p.s I hope I'm doing the quotes and codes right in my forum post... I'm so noob I had to google that too.😞
 

I do need to update this tutorial. Some things don't corrispond to the latest PROXMOX version anymore.
 
Possible mistype?
Module vfio-pc not found in directory Driver is "vfio-pci".
 
You are going to have issues with the onboard devices if they aren't in their own IOMMU group or can't pass everything in the group.
 
0000:0a:00.0
0000:0a:00.1
 
What do these two devices show up as in your lspci command and can I see a copy of your vfio-driver-override.sh script?
 
What version of Proxmox are you running?

BIOS behavior is going to be completely independent from Windows. You would need to modify BIOS settings to influnce pre-Windows operations.
 
It sounds like you already have the video output set to use both iGPU and dGPU if the iGPU acts as your extended display in Windows.
 
The only simple solution I can offer here is to swap the display cables if the monitors have the inputs to do so. BIOS usually doesn't offer much in ways of altering video settings but you can check under the advanced tab. See what video settings your board offers.

I haven't ran WCG since they separated from IBM over a year ago. I'd love to go back and plan to if they're online again but right now isn't a great time for me. I'm not in a good position to jack my electric bill up $100 every month. Plus the heat, plus the noise, plus my landlord is already mad about how many I have while they're idling...
 
You better bet when I come back though I'm gonna come back swinging. E5-2699v3 CPUs are CHEAP and DL380 G9 servers aren't much more expensive. Plus my work can hook me up with free/cheap stuff. I'm gonna build myself a 240V cluster compute node with as many as 400 CPU cores! >:3

WCG has been running for quite a long time now FYI. Not run it since the move either though.