Posts made by VoipDude

@olivierlambert

In the interfaces list, each interface that is bonded should have this info:

• The bond device name and network
  This is already present today in XO, so no changes here.

• The type of bond
  Derived from xe bond-list and then xe bond-param-list uuid=XXXX

• The underlying interfaces (ex: eth0, eth1) that are participating in the bond
  Derived from xe bond-list and then the slave UUIDs references to the device names from xe pif-list

In terms of "where", it should be in either Pool > Network or Pool > Host > Network (or both, still not sure the difference between viewing networks in the pool or host)

And as @TheNorthernLight mentioned, it would be great to be able to modify bonds (ex: remove or add or change the underlying interfaces that are in the bond). I don't have XenCenter handy to test if that's a thing, it might be not be possible to modify existing bonds.

Thanks!

@olivierlambert Yup, you're right! This command gives the bond type:

# xe bond-param-list uuid=5f470b0a-f59e-5c34-69a5-4676719da6d6
uuid ( RO)               : 5f470b0a-f59e-5c34-69a5-4676719da6d6
             master ( RO): 8d0b83b2-4336-c7a5-f84f-be0d6a49064f
             slaves ( RO): 3598380c-3da3-c096-7a84-2c4ac2b280ee; 7188d716-cf0a-4e34-5ab1-5ddae4e6fe28
               mode ( RO): active-backup
         properties (MRO): 
      primary-slave ( RO): 3598380c-3da3-c096-7a84-2c4ac2b280ee
           links-up ( RO): 2
    auto-update-mac ( RO): true

@olivierlambert

(I have snipped some of the output for brevety)

Yes, so this command shows the interfaces that are participating in the bond:

#  xe bond-list
uuid ( RO)      : 5f470b0a-f59e-5c34-69a5-4676719da6d6
    master ( RO): 8d0b83b2-4336-c7a5-f84f-be0d6a49064f
    slaves ( RO): 3598380c-3da3-c096-7a84-2c4ac2b280ee; 7188d716-cf0a-4e34-5ab1-5ddae4e6fe28

But then we need to find out which UUID corresponds to which interface by doing a pif-list:

# xe pif-list
uuid ( RO)                  : 8d0b83b2-4336-c7a5-f84f-be0d6a49064f
                device ( RO): bond0
    currently-attached ( RO): true
                  VLAN ( RO): -1
          network-uuid ( RO): f5f7ee91-dcc9-104e-c696-1e74d7ddedb1

uuid ( RO)                  : 3598380c-3da3-c096-7a84-2c4ac2b280ee
                device ( RO): eth4
    currently-attached ( RO): false
                  VLAN ( RO): -1
          network-uuid ( RO): 192daa64-2df8-41a3-9849-8f403104b3fe


uuid ( RO)                  : 7188d716-cf0a-4e34-5ab1-5ddae4e6fe28
                device ( RO): eth5
    currently-attached ( RO): false
                  VLAN ( RO): -1
          network-uuid ( RO): 4f7a5c61-9bd6-dbb5-b34a-3bfe46ced469

So we can see eth4 and eth5 are part of bond0.

I then can find out what kind of bond it is with this command:

# ovs-appctl bond/list
bond	type	recircID	slaves
bond0	active-backup	0	eth4, eth5

Thanks,

@olivierlambert said in Bonded interface viewing support in XO:

That's already there. There's an eye button with an hover text: "Show PIFs".

edit: I'm not sure to fully understand what's missing exactly, can you be more specific?

In my case, pressing on this button just shows the bond interface and not what makes up the bond. See screenshot:

Edit: Sorry, realized that you wanted to understand what it's missing.
For me, it should show what type of bond it is (ex: in my case it's Active-Passive) as well as the physical interfaces that make it up (Ex: in my case bond0 is eth4 and eth5 bonded together).
Even better would be to be able to even edit the bond (ex: change up interfaces in case something fails), but that might be a Xen limitation.

Hello,

Does XenOrchestra have a way to view existing bonded network interfaces?

Looking both at the pool and host, I can see the "bond0" interface in the list, but there is no way to list which physical interfaces are making up the bond and neither what kind of bond it is. I had to go to the CLI for this.

Just wondering if I'm not looking at the right place or if this is just something on your to-do list.

Thanks,

Hello guys,

Glad to hear that my thread had traction and others helped with troubleshooting

My issue still keeps on happening and I now just left that Win Server 2019 VM that keeps crashing nightly when it tries to auto-apply Windows updates.
xl dmesg shows that it's out of memory:

[14:59 xenhome ~]# xl dmesg
m_pod_demand_populate: Dom18 out of PoD memory! (tot=2097695 ents=524256 dom0)
(XEN) [4145112.313876] domain_crash called from p2m_pod_demand_populate+0x751/0xa40
(XEN) [4145112.317876] p2m_pod_demand_populate: Dom18 out of PoD memory! (tot=2097695 ents=524256 dom0)
(XEN) [4145112.317879] domain_crash called from p2m_pod_demand_populate+0x751/0xa40
(XEN) [4145112.320228] p2m_pod_demand_populate: Dom18 out of PoD memory! (tot=2097695 ents=524256 dom0)

However, this host should have more than enough RAM. Here is a screenshot of the RAM graph from XO for the last week:

The windows VM in question has a 2GB/8GB dynamic allocation, but the graph shows the 8GB always in use:

And unlike @pescobar, I am running the latest version of XCP-NG here:

[15:03 xenhome ~]# cat /etc/redhat-release 
XCP-ng release 8.2.0 (xenenterprise)

I'm glad to hear that not doing dynamic solved the issue for pescobar, but now I want to get to the bottom of this because maybe this bug might impact someone in prod.

Let me know what other info I could provide so that we can troubleshoot this further.

Thanks!

Hello world,

I've been using XenServer for years and the combination of XCP-NG and XenOrchestra is a breath of fresh air.

I'm running the following setup, with two VMs running on three separate XCP-NG hosts (no shared storage):

• Site 1:
• • Host 1: 1TB local array, running VM A
• • Host 2: 1TB local array, running VM B
• Site 2:
• • Host 3: Offsite, 1TB local array, running no VMs.

Both VM A and B have a single 300GB disk created for them.
I then use continuous replication of VM A from host 1 to hosts 2 and 3 and VM B from host 2 to host 1 and 3.
The idea is to be able to survive a catastrophic failure of their main hosts and also if the main site goes offline.

Given that XenServer was a bit peculiar in the past with storage (ex: not able to reclaim disk space online after deleting a snapshot in older versions if I remember correctly), I have a few questions to double-check and I won't run into limitations in the future.

I'm also running with local storage with thick provisioning, the local storage is mechanical SAS drives so I don't want to lose performance with fragmentation all over the place.

My questions are:

1. Is it "safe" to use continuous replication for this kind of scenario and could this be done hourly with no long-term issues? I.e.: will 4 years from now (when XCP-NG LTS 8.2 will near EOL ) will this not cause to run into weird errors because the VM has been snapshotted/imported/exported tens of thoudsands of times. From what I understand in your documentation, coalescing fixes this so it should be fine.

2. Knowing that each host has 1TB local storage, will it be enough place to continue using CR and even snapshots from time to time?
   Let me explain:
   In the past, I tried labbing with 400GB storage VMs, but it refused to create snapshots (from what I understand, XCP-NG wanted to see the whole 400GB space available). (400GB VM + 400 GB CR = less than 400GB remaining)
   Now I use 300GB disk space VMs, so 300GB VM + 300GB CR = more than 300 GB remaining

Is there any other limitation that I should be aware?

I also want to use temporary snapshots before major upgrades on the VM, just in case. But those snapshots would be quickly deleted after I confirm the upgrade went correctly. I suppose the disk space would be reclaimed after deleting the snapshot, right?

Thanks!

Hello everyone,

I've got a strange issue on my XCP-ng installation at home.

Short story:
In short, a CentOS 8 VM that I have keeps crashing whenever I try to perform updates or give it some IO load (more on this later). I seem to have the same issue with a Windows Server 2019 VM which also crashes sometimes while performing updates (but am unable to reproduce this consistently). A brand new CO8 VM does not have this issue neither other older CO VMs (5 and 6) on the same host.

Symptoms:
When I say crashing, from the XO console for the CO8 VM it simply looks like a reboot. I lose SSH and I see the VM rebooting, no error messages nor anything. There is nothing in the VM's logs either following the crash. I tried finding logs in XCP-ng and either they're empty or I'm not looking in the right place.

The VM is not running any services/workload either. The crash is reproducible whenever I run a yum update or an IO benchmark (such as fio)

Troubleshooting that I did:
At first, I suspected RAM issues. I ran memtest86 overnight with no errors reported. I even changed out the RAM from another working computer, but the same issues happened. So I do not suspect this is bad RAM.

The XCP-ng install is running in Software RAID1 (configured by the XCP-ng installer) over a pair of RAID edition SATA disks. I do not suspect the disks are bad, as other VMs have no issues neither are there any errors reported in logs.

I then thought perhaps this was a bug with XCP-ng 8.1, so I upgraded to 8.2 recently. Same issue persists with no difference.

I also doubt that it's a hardware problem in general as my other CentOS 5 and CentOS 6 VMs run rock solid, no matter how hard I hit the IO. A brand new CO8 VM was also able to complete IO benchmarks without crashing.

Nothing crazy was done on the crashing CO8 VM either, it's running the stock CO kernel. I even uninstalled the xen guest tools in case it was an issue with them.

My question is as follows:

What could I do to to troubleshoot this further? Does XCP-ng have a log that could give me clues?
I'm happy that this is happening in my home testing environment and not production, but I'd like to resolve this issue and gain insight into how I could troubleshoot this if I'm ever faced with such a thing in prod.

Thanks!