New answers tagged xenserver
I have experienced the same error, so start try take some informations. When you do the upgrade seme VM's lose the Xen Drivers for keybord and DVD driver, so can't detect it, specially if you did the upgrade with xentools.iso on it. To solve that i remove the VM, but not the disks, so i create a nev VM and atached the disks, worked for me.
If you an attach enough local storage you can build your own iSCSI HA-solution. Reiceipe: - drbd > 8.2.x - tgtd Set up two local VMs that replicate two LVs onto each other in drbd dual primary mode. Use each local iscsi target. In XEN-server make sure to use eacch target in active/passive mode (no rr!).
When choosing an HA solution, you'll need to decide what level of downtime (if any) is acceptable. This will affect the complexity of your setup. I think you have two options without purchasing additional equipment (with further permutations): "Always up" - DRBD in Primary-Primary 5-15 minutes of downtime - DRBD in Primary-Slave mode For the highest ...
You should be able to find it through: $ cat /etc/xensource-inventory DEFAULT_SR_PHYSDEVS='dev/sda3' It should be using lvm. Depending on the version and the state of the volumes, you may want to run: # pvscan PV /dev/sdb1 VG sas01 lvm2 [558.37 GiB / 228.37 GiB free] PV /dev/sda5 VG kvm01-vg lvm2 [237.63 GiB / 0 free] Total: 2 [796.00 ...
This is normal behavior of XenServer. All the metadata for the image (VDI) is in the Xapi database files, not in the image files themselves. Note that the UUIDs of images are also gone, so no matter if you've imported diskless VMs back from old hosts or recreated them from scratch, there's no way to Xapi to find which VDI belongs to which VM. Same goes for ...
I found the solution for the problem. The guide is wrong. It is extremely important to create the mdadm.conf before running mkinitrd. Without the correct mdadm.conf the device mapper will name /dev/md0 to something silly (/dev/md125). The problem then is, that the device for the rootfs is not found at boot.
I hav updated all my drivers (firmware and RAID/PERC drivers for dell 1950) and then installed AGAIN Xenserver 6.5. It s now working out of the box. My DELL BIOS was 2.0.x now its 2.7.0 so it was really old. Try it, must work. Regards.
The pool master and servers in the pool need to be the same XenServer version. To answer your question, yes you can remove one server at a time, upgrade, join the pool, then migrate the VM's. As always, make sure you make a backup first (export snapshots) before performing the upgrade.
Use scp and copy the VM files to another location.
Top 50 recent answers are included