Hi currently running xcp-ng 8.2 and within my small form factor I have 4 VMs. One of the VMs is currently virtualized pfsense. When xcp-ng boots I'd actually like the pfsense VM to start first. Is it possible to assign in XO or through the xcp-ng CLI itself the proposed boot order of the various VMs?
Best posts made by kevdog
-
Is it possible to prioritize the booting of certain VMs over another when xcp-ng starts?
-
RE: XCP-ng Center: Future
Hey thanks for working on XCP-ng Center -- I find it a really useful tool.
Is this a README that describes how your project differs from XenCenter.
-
RE: Windows Server 2016 & 2019 freezing on multiple hosts
FWIW -- I had a similar problem with VMs going randomly down -- it wasn't windows but various BSD and Linux VM's. Sometimes they would run a few days, other times they would lock up every other day. Logs didn't help because when the VM locked, logs were not written. I even had the xcp-ng installation lock a few times, although it was usually on of the VMs. I started searching for faulty hardware and eventually SMART tested all the drives and mem86 the RAM. Turns out I had some bad RAM modules which I later RMA'd. With new RAM (after after thoroughly testing it), I haven't had any lock ups. I'm not sure this will help you at all.
-
RE: How to choose which specific NIC/port for Xen-Orchestra server to bind to?
@julien-f Thanks for explanation. Thank you
-
RE: Question regarding copying of VMs within storage pool
Well damn -- you're right.
Well VM now up and running. Just have to figure out how networking works in this new copied VM. Thanks for help.
-
RE: Installing patches in pool fails (fixed)
Not that you actually needed this reply, but confirmed patch works after upgrade this morning.
Thanks for update and the patch.
-
RE: HTTP to HTTPS redirection
@nikade Hey thanks for for the link. I ended up just using a LetsEncrypt cert rather than self signed. I think had to add a DNS host override on my router to associate the Local LAN address of the xo server with the domain name of the server contained in the certificate -- Like 10.0.1.50 ---> xo.example.com. Thanks for pointing me in the right direction on this one.
Latest posts made by kevdog
-
RE: Error on attempting delta backup -- how to rectify?
@Danp Aww. see that box. Let me look into this problem a bit more. Learning some new things here.
-
RE: Error on attempting delta backup -- how to rectify?
@DustinB Didn't know about the health check drivers to be honest. My VM not working is a pfSense VM. I looked at the link posted and didn't see BSD drivers. Looking my XO installation for pfSense I dont even see anything in the GUI regarding healthchecks. Weird. Not sure how this option was even turned on in the first place.
-
Error on attempting delta backup -- how to rectify?
Been using XO with delta backups for a while however one of my VMs is now receiving an error and I'm not sure how to rectify. I'll post what I have below. Looks like there might be two errors -- VHD check error and WaitObjectState Error. Not sure how to actually fix any of these errors.
Thanks for help.
Clean VM directory VHD check error path "/xo-vm-backups/a8a20272-aaef-0bc9-82c8-d5ba96d1e725/vdis/fed92d10-c8a0-4587-a018-8a6b6c050453/60e7144d-ea34-4cf7-b798-c0bfd17134c2/.20240204T075759Z.vhd" error {"generatedMessage":false,"code":"ERR_ASSERTION","actual":false,"expected":true,"operator":"=="} Start: Mar 4, 2024, 01:00:02 AM End: Mar 4, 2024, 01:00:02 AM Snapshot Start: Mar 4, 2024, 01:00:02 AM End: Mar 4, 2024, 01:00:04 AM Backups for XO transfer Start: Mar 4, 2024, 01:00:06 AM End: Mar 4, 2024, 01:18:53 AM Duration: 19 minutes Size: 4.34 GiB Speed: 3.94 MiB/s health check transfer Start: Mar 4, 2024, 01:19:00 AM End: Mar 4, 2024, 05:34:33 AM Duration: 4 hours Size: 9.3 GiB Speed: 635.79 KiB/s vmstart Start: Mar 4, 2024, 05:34:33 AM End: Mar 4, 2024, 05:44:33 AM Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state Start: Mar 4, 2024, 01:19:00 AM End: Mar 4, 2024, 05:44:37 AM Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state Start: Mar 4, 2024, 01:00:04 AM End: Mar 4, 2024, 05:44:37 AM Duration: 5 hours Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state Start: Mar 4, 2024, 01:00:02 AM End: Mar 4, 2024, 05:44:37 AM Duration: 5 hours Error: waitObjectState: timeout reached before OpaqueRef:214f572e-ed48-4f80-a9c7-6f984129a2f7 in expected state Type: delta code_text
-
RE: How to choose which specific NIC/port for Xen-Orchestra server to bind to?
@julien-f Thanks for explanation. Thank you
-
RE: How to choose which specific NIC/port for Xen-Orchestra server to bind to?
Ok I looked at the hostname directive and changed it to the specific IP address. However just a few thoughts since honestly I've never thought about it before.
If I had two physical or virtual NICs assigned to a xcp-ng VM -- say eth0 and eth1 -- how does the program by default decide on which NIC its going to bind it's ports by default? Is it always the card assigned to eth0 (since eth0 can be manipulated by systemd network setting so it may not necessarily represent the first actual card brought up on the bus architecture)?
I also thought hostname was used in XO's acme plugin which would could be used to generate automatic acme LE certs. If you change the hostname to an actual IP address, isn't this process going to be altered?
Thanks for your insights. I don't mind disaster recovery since no matter how many times you practice or simulate things, it seems I learn the most when the actual S**T hits the fan.
-
RE: Can not recover /dev/xvda2
@olivierlambert Hey thanks for the suggestion. I'm pretty sure it's probably a problem with the underlying lvm hardware, but its funny, taking a look at Dom0, I don't see anything mentioning any disk related problem.
Sample of dmesg log below
[805638.417594] block tde: sector-size: 512/512 capacity: 419430400 [805641.656976] vif vif-30-1 vif30.1: Guest Rx ready [805649.655582] vif vif-30-1 vif30.1: Guest Rx stalled [805651.179897] device vif32.0 entered promiscuous mode [805655.092408] device tap32.0 entered promiscuous mode [805658.494363] device tap32.0 left promiscuous mode [805659.661403] vif vif-30-1 vif30.1: Guest Rx ready [805692.482092] device vif32.0 left promiscuous mode [805702.199871] vif vif-30-1 vif30.1: Guest Rx stalled [805711.543432] vif vif-30-1 vif30.1: Guest Rx ready [805719.664229] vif vif-30-1 vif30.1: Guest Rx stalled [805729.659247] vif vif-30-1 vif30.1: Guest Rx ready [805745.392833] block tde: sector-size: 512/512 capacity: 419430400 [805749.905041] device vif30.1 left promiscuous mode [805752.496307] device vif33.0 entered promiscuous mode [805755.222166] device vif30.0 left promiscuous mode [805756.847363] device tap33.0 entered promiscuous mode [805799.443948] device tap33.0 left promiscuous mode [805804.852848] vif vif-33-0 vif33.0: Guest Rx ready [830198.036797] device vif33.0 left promiscuous mode
In terms of backups --- kind of a sticky issue. Yes I have delta backups on a FreeNAS partition. Is there documentation on how to actually restore these backups if starting from scratch? By scratch I mean lets say no hardware disks with a new XO installation?
Here is my backup directory structure BTW in case things aren't exactly clear:
freenas% pwd /mnt/tank/backups/Xen freenas% ls 1632582667671.test encryption.json 1633705775069.test metadata.json 1668267335259.test xo-config-backups 1f5adaf3-7631-d478-3c74-468c48079177 xo-pool-metadata-backups 66efa31e-5595-dda6-5ce9-dc2a1bb26cb9 xo-vm-backups c514822f-74bb-bfde-77d8-8f2b0c0b844b
-
Can not recover /dev/xvda2
Not sure where to start here.
I'm running xcp-ng 8.2.1 on a Proctetli box.
My actual partitions on the hardware are as follows:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb 8:16 0 931.5G 0 disk └─XSLocalEXT--99f0de78--37cb--ead5--0c56--bd5e341416aa-99f0de78--37cb--ead5--0c56--bd5e341416aa 253:0 0 1.8T 0 lvm /run/sr-mount/99f0de78-37cb-ead5-0c56-bd5e341416aa tdc 254:2 0 10G 0 disk tda 254:0 0 100G 0 disk sda 8:0 0 931.5G 0 disk ├─sda4 8:4 0 512M 0 part ├─sda2 8:2 0 18G 0 part ├─sda5 8:5 0 4G 0 part /var/log ├─sda3 8:3 0 890G 0 part │ └─XSLocalEXT--99f0de78--37cb--ead5--0c56--bd5e341416aa-99f0de78--37cb--ead5--0c56--bd5e341416aa 253:0 0 1.8T 0 lvm /run/sr-mount/99f0de78-37cb-ead5-0c56-bd5e341416aa ├─sda1 8:1 0 18G 0 part / └─sda6 8:6 0 1G 0 part [SWAP] tdd 254:3 0 834.2M 1 disk tdb 254:1 0 721M 1 disk
Within the actual xcp-ng host I'm using local storage which is the LVM 1.8T partition.
I have a number of VMs on the host, however at the most I had either 4/5 running.
VMs on the host are either Arch Linux, Ubuntu Linux or pfsense. Currently I'm having a problem with all the Ubuntu and Arch VMs.I believe most of the VMs that were created were created with partition scheme of /dev/xvda1 --> boot partition, /dev/xvda2 ---> root partition, /dev/xvda3 ---> swap partition.
When attempting to boot the Arch or Ubuntu VM's, I'm getting i/o errors when trying to mount the /dev/xvda2 or the root partition.
Although I haven't troubleshooted every VM, I've tried the following:
- VM boots to recovery or busybox shell, try fsck /dev/xvda2 however process doesn't work
- Boot a rescue CD (such as an Arch Install Disk), and then try fsck /dev/xvda2.
When trying such an approach I'm seeing the following:
# lsblk :( NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 607.1M 1 loop /run/archiso/sfs/airootfs sr0 11:0 1 721M 0 rom /run/archiso/bootmnt xvda 202:0 0 100G 0 disk ├─xvda1 202:1 0 1M 0 part └─xvda2 202:2 0 100G 0 part # fsck -yv /dev/xvda2 fsck from util-linux 2.34 e2fsck 1.45.4 (23-Sep-2019) /dev/xvda2: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: Input/output error while recovering journal of /dev/xvda2 fsck.ext4: unable to set superblock flags on /dev/xvda2 /dev/xvda2: ********** WARNING: Filesystem still has errors **********
I've seen similar error when working with physical disk, however xvda represents virtual partitions.
I'm I just totally hosed here in terms of recovery?? I'm a little stumped how to recover. -
How to choose which specific NIC/port for Xen-Orchestra server to bind to?
I’m running Xen Orchestra on an Ubuntu VM with two virtual NICs attached to VM. The two NICs are designated eth0 and wg1. wg1 is a wireguard NIC and eth0 is a non-wireguard NIC.
Within the xen-orchestra configuration xo-server.toml, all I see is the option to bind to a specific port
[[http.listen]] port = 443
When starting the xo-server.service, xo-server listens on port 443 however this port seems bound to the eth0 interface, not the wg1 interface.
I’d actually like xo-server to listen on wg1 and not on eth0. I’m unfortunately not a networking expert nor expert using xen-orchestra. Is it possible to configure xo-server to listen on a specific NIC?
If looking at server I have xo server bound to IP address of the eth0 NIC:
# netstat -tulpn ... tcp 0 0 142.xx.xxx.xxx:443 0.0.0.0:* LISTEN 2258771/node ...
Current NICs on the system:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 1a:0b:43:61:c3:70 brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 142.xxx.xxx.xxx/20 brd 142.93.127.255 scope global eth0 valid_lft forever preferred_lft forever inet 10.10.0.5/16 brd 10.10.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::180b:43ff:fe61:c370/64 scope link valid_lft forever preferred_lft forever 3: wg1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.x.xxx.x/24 scope global wg1 valid_lft forever preferred_lft forever
-
Is it possible to prioritize the booting of certain VMs over another when xcp-ng starts?
Hi currently running xcp-ng 8.2 and within my small form factor I have 4 VMs. One of the VMs is currently virtualized pfsense. When xcp-ng boots I'd actually like the pfsense VM to start first. Is it possible to assign in XO or through the xcp-ng CLI itself the proposed boot order of the various VMs?
-
RE: Remove a host from a pool
So here is the dilemma I'm running into, the host I added with the incorrect network ports and such. It was reachable via the internet until I upgraded some pool patches, now its extremely unreachable. I can boot the installation, however I can't reach the slave to eject the host.
I tried emergency resetting network, however that didn't work either.
lshw -C network reveals a lot of unclaimed ethernet controllers which are the Intel 225-V version. I looked up various internet resources to see what "unclaimed" meant, and these sources suggest there isn't an appropriate driver -- which is weird since prior to the pool patches applied this installation was up and running (but misconfigured).
Sooo -- I either have two options at this point, and I don't really care. I'd like to eject this pool member -- destroy it -- however it seems I can't since it's unreachable, or I need to reinstall the I225V network driver.
Any suggestions?