- tension and eitmoyerelia like this
Jump to content
Posted by stardot on 16 December 2015 - 04:30 PM
Here's the high level steps I took to migrate :
To migrate from Xen -> KVM with Solus :
1. create new vps with KVM with exact disk / ram (maybe 1gb above because space is not always exact)
2. shut down new vps
3. lvsnapshot existing LVM (not necessary if you can shut it down)
4. dd existing XEN LVM -> KVM LVM (you need to dd to the KVM LVM's main disk partition, not disk + swap)
5. e2fsck + resize2fs new KVM LVM to correct size differences
6. boot new KVM vps with liveCD (I used CentOS 7 x64 minimal install cd) & boot into troubleshooting
7. chroot the disk
8. modify /etc/fstab /etc/mtab and /boot/grub/grub.conf to change xvda disk label to vda
9. grub-install & run grub to setup the new disk , this installs the boot MBR
10. halt , remove mounted CD, boot off disk, no other changes needed
Note : you need to move IP addresses in Solus to the new KVM. The new VPS will boot up with the old VPS ip addresses set, so the old vps should be turned off to avoid IP conflict.
Posted by stardot on 12 December 2015 - 04:08 PM
I've been trying for the past few weeks to migrate my Xen PV servers which use LVM for storage to my newly installed and integrated Solus KVM servers, which also use LVM.
There is a lot of (sparse) documentation out there for various guides and strategies which mainly focus on ensuring that disk labels, grub configs and console labels and whatnot get changed when you migrate. This type of thing makes sense and I never had problems doing it.
The problems I've encountered is simply when I dd the Xen LVM -> KVM LVM, the disk doesnt boot. The KVM Bios sees no disks whatsoever. I'm kind of at a loss because I'm not even getting to the point where the kernel wont boot or find the partitions because of configuration disk labelling issues and whatnot.
I'm not sure what I'm missing and I wanted to avoid rsyncing the filesystem from Xen -> KVM, as I'd prefer the cleanest method possible. Once I figure out the best method to do this I will script and automate the entire process with a shell or python script (which I would be fine sharing here as well).
Any ideas why a Xen PV LVM image wont boot on KVM with a straight DD copy?
Posted by tension on 04 August 2015 - 07:44 AM
Posted by dhaivatnaik on 13 March 2015 - 08:34 AM
Can anybody Help me out with this ?
Posted by dhaivatnaik on 12 March 2015 - 01:02 AM
I have solusvm admin access. I want to delete few templates that i have created. By templates i mean the actuall template file stored on the server "templatename.tar.gz"
I donot see any option to delete those. Also how to connect to SSH or FTP of the SolusVM server. If somehow i can connect to the server FTP or SSH i can find the file and delete.
Please guide me with this issue.
Posted by mike503 on 08 March 2015 - 05:04 AM
I've been using LXC for a variety of things lately, and it seems much cleaner and integrated with the kernel than OpenVZ. Out of the box OpenVZ has way too many tunable options. LXC is simpler and provides a more modern approach to long-running containers (to me it feels like the evolution of OpenVZ)
It is pretty close to the same commands as well to start, stop, destroy, etc... would be awesome if SolusVM could deal with LXC-based containers the way it does with OpenVZ ones.
Posted by pcmarche on 04 January 2015 - 01:03 PM
WORKS,thanks a lot
Posted by Dave A on 30 May 2009 - 09:59 AM
<TABLE border=0 cellSpacing=1 cellPadding=6 width="90%" bgColor=#666666><TBODY><TR><TD bgColor=#ffffd2 align=left>SolusVM Version</TD><TD bgColor=#ffffd2 align=left>Description</TD><TD bgColor=#ffffd2 align=left>Release Date</TD></TR><TR><TD bgColor=#ffffff align=left></TD><TD bgColor=#ffffff align=left></TD><TD bgColor=#ffffff align=left></TD></TR><TR><TD bgColor=#ffffff align=left></TD><TD bgColor=#ffffff align=left></TD><TD bgColor=#ffffff align=left></TD></TR><TR><TD bgColor=#ffffff align=left>SolusVM Multi</TD><TD bgColor=#ffffff align=left>Mulit-server KVM & OpenVZ based.</TD><TD bgColor=#ffffff align=left>Mid August 2009 - Only OpenVZ supported, KVM & XEN will be added as updates at a later date.</TD></TR></TBODY></TABLE>
Posted by bip on 03 May 2016 - 02:56 PM
./install --release stable --nodeos RHEL --osversion 6 --svmtype 4no ...etc
Posted by 24x7server on 09 January 2016 - 03:32 PM
You can use natting for this. Routing all the traffic from public to private internal inside on VM.
Posted by tension on 03 September 2015 - 03:05 AM
Could you share this template
I'm afraid this theme is to be paid for.
Posted by Abueloton on 25 June 2015 - 03:11 AM
Posted by Brian on 04 February 2013 - 04:40 AM
Posted by Hannan on 28 January 2013 - 04:43 PM
Have you attached intbr0 to any physical devices? The only device that should be attached to any bridge is eth0. What is the output of brctl show.
[root@kvm2 network-scripts]# service network restart
Shutting down interface br0: [ OK ]
Shutting down interface eth0: [ OK ]
Shutting down interface intbr0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface intbr0: [ OK ]
Bringing up interface br0: [ OK ]
virbr0 Link encap:Ethernet HWaddr 52:54:00:7C:D7:93
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 TX bytes:0 (0.0
Posted by smoge on 24 May 2011 - 04:57 AM