@planedrop Yes, doing thing like this frequently would not be fun at all. This is a one-off event. So, B is the way to go.
Best posts made by Ascar
-
RE: Best way to migrate a VM with PCIe device passes-through to another host
-
RE: Correct approach to passing block devices (SSD) through to a VM
@planedrop Oh, here is my old friend from previous discussions about how to get things done better.
Thank you @planedrop. I am coming up tomorrow with even a bigger question
Have a good evening
Latest posts made by Ascar
-
RE: Smartctl Plugin in XO 5.92 and XCP-NG 8.2
@Tristis-Oris Alright, so 8.3 is pre-requisite. Thanks for confirming.
-
Smartctl Plugin in XO 5.92 and XCP-NG 8.2
Hello, everyone. Please clear my doubt. I am on XCP-NG 8.2 fully patched and I also updated XO to 5.92.
Following the announcement of features in XO 5.87 and I was hoping to see the health of local hard drives and SSDs. The option is present in the Advanced tab of the Hosts page, however it is grayed out. Small message says "Smartctl plugin not installed".I checked the Plugins page and smartctl is nowhere there.
Simple question - as long as I am not on XCP-NG 8.3 am I not supposed to have the disk drive monitoring available in the WebUI of XO?Thank you in advance
-
RE: Adding OS Logos
@olivierlambert This topic was last time discussed in June of 2021.
I am wondering if some sort of solution has been built to add icons to VMs which don't have icons next to them?
I have one VM with FreePBX and while in its core this is a modified CentOS yet the OS reports itself as Sangoma Linux. Another VM is virtualized TrueNAS Scale. Both VMs are bare iconlessThank you
-
RE: Best way to migrate a VM with PCIe device passes-through to another host
@planedrop Yes, doing thing like this frequently would not be fun at all. This is a one-off event. So, B is the way to go.
-
RE: Best way to migrate a VM with PCIe device passes-through to another host
@dredknight Thank you. I did not try A but I was feeling that it would not succeed.
-
Best way to migrate a VM with PCIe device passes-through to another host
Knowledgeable people, please advise what should be the best sequence for migrating a VM with running pFsense to another host while a NIC is passed through to it:
a) Just try to migrate straight ahead
b) Stop the VM => Remove the PCIe device from the VM => Migrate => Pass the NIC through to the Migrate VM on the Target Host
c) Make a clone of the VM => Migrate the Clone to the Target Host => Pass the NIC to the new VM on the Target Host
Thanks in advance to everyone
-
RE: Correct approach to passing block devices (SSD) through to a VM
Hello, @planedrop
This is what has been on my mind recently. I have a home lab setup with a few nodes, 3 to be precise.
I bought refurbished Supermicro boards with Xeon-D processors, chassis and all other components required for home server builds. As software-defined storage is the technology of choice for many people nowadays my server nodes have Broadcom 9300-8i HBAs with SATA SSDs connected to them.
There is something, though, what is itching - lack of visibility of what is happening to the storage drives and the HBAs when using XCP-NG. MegaRAID Storage Manager does not work with 9300-series HBAs so there is no tooling to monitor the HBA and anything connected to it, SAS3IRCU is pretty useless as it does not provide anything other than HBA listing; if I wanted to be able to get more out of this utility I would have needed to use IR vs IT firmware in the HBA which defeats the idea of running an SDS stack.
Using smartmontool manually is not foolproof - I will always forget to check the stats and miss an event of drive failure. If I make and mdadm or even openzfs volumes again to be on top of things I will have to watch the server health myself and of course something will get in the way.
So, my thought process was like this - install XCP-NG on a PCIe M.2 stick and don't make any SRs from the SSDs connected to the HBA. Instead, the first VM on the host will be a TrueNAS instance and the drives or even the HBA, as you suggested yesterday, will be passed through to the TrueNAS VM. TrueNAS has all hardware monitoring built in and it is a "set it and forget it" thing, all automated and taken care of by TrueNAS. Moreover, for the NAS fleets with less than 50 drives in total you may use TrueCommand to have all monitoring tasks on autopilot. Plus you get the best automated ZFS array health monitoring done by TrueNAS.
Once this part is done make an NFS or iSCSI share on the NAS VM and then point XCP-NG to it and add a new SR. All network traffic will be flowing withing the PCIe bus of the host and even not traversing the network switches unless the SR is accessed by other XCP-NG hosts. This way we get like a hypervisor and a NAS running inside the same node, while a better, more advanced storage repository is placed on the ZFS-protected volume in the NAS.
What I wanted to discuss is whether there are any gotchas in my thinking and whether you and people like you can spot any oversights in my "design". Please share ideas and views.
-
RE: Correct approach to passing block devices (SSD) through to a VM
@planedrop Oh, here is my old friend from previous discussions about how to get things done better.
Thank you @planedrop. I am coming up tomorrow with even a bigger question
Have a good evening -
Correct approach to passing block devices (SSD) through to a VM
Hello, everyone. Please clear my doubt. If SSDs are connected to a SAS HBA and I want to pass them through to a VM should I do it with the SSDs as described here or I should pass the HBA through as a PCIe device?
Spent some time trying to pass the SSDs through and can't make this work. Wondering whether I just need to pass the whole HBA?
Thanks
-
RE: What is xo-server-log?
@ronivay So happy to see you here. Thank you for clarifying my confusion. I did not modify installation paths and I found what I was looking for.
logs-cli.mjs
does not run by itself and needsnode
to be prepended. Is this correct? However I made a symlink as you explained and it runs asxo-server-logs
directly.