1359590548 Q * Ghislain1 Quit: Leaving.
1359594204 J * clopez ~clopez@9.12.117.91.dynamic.mundo-r.com
1359600098 Q * mcp Server closed connection
1359600147 J * mcp ~mcp@wolk-project.de
1359601805 Q * jrklein Ping timeout: 480 seconds
1359603434 J * jrklein ~osx@proxy.dnihost.net
1359604577 Q * clopez Ping timeout: 480 seconds
1359606484 J * lane ~lane@66.134.230.12
1359606494 M * lane Hello 
1359606531 M * lane I was wondering if there is any manageable way to migrate a vserver virtual machine into Vmware ESXi?
1359606556 M * lane I have a failing SAN and a virtualization host setup by a previous developer to the organization
1359606572 M * lane I'd like to move it to the VMWare environment we have
1359606624 M * lane Is anyone around?
1359606645 N * lane Guest136
1359606847 M * Guest136 Looks like its been 2 days since anyone was on here.
1359606853 M * Guest136 Talking...
1359607617 N * Bertl_zZ Bertl
1359607625 M * Bertl morning folks!
1359607647 M * Bertl Guest136: I think you're mistaken :)
1359607692 M * Guest136 Hi!
1359607702 M * Guest136 It appeared so from the logs on the website
1359607703 M * Bertl and yes, you can migrate a Linux-VServer guest to a full virtualization solution like KVM
1359607710 M * Guest136 Glad! That I am wrong!
1359607726 M * Guest136 Bertl: is there any documentation for doing this?
1359607767 M * Bertl well, it is usually simpler to setup a Linux-VServer host inside a full virtualization and then simply move the guest there
1359607817 M * Bertl because Linux-VServer uses isolation, there is no need for the guests to do any hardware related stuff, so usually the necessary drivers and setup parts have been stripped away
1359607849 M * Guest136 Bertl: I have a very special situation, with a production serving running on a Debian Linux Vserver system.  The San this host is attached to is showing signs of failure, the host and it's iSCSI connection to the SAN isn't documented, and the software in this VM is proprietary without vendor support.  
1359607861 M * Guest136 server running*
1359607895 M * Guest136 We have an active VMWare ESXi Environment I can migrate the guest into but if that's not possible then I'll take what I can get here.  
1359607898 M * Guest136 :-)
1359607925 M * Bertl I don't see what advantage that would give in your case, it looks to me like the san is your problem, no?
1359607963 M * Guest136 the power supply on the unit is showing errors related to fan, the issue is not with the integrity of the array 
1359607974 M * Guest136 we have a separate ESXi storage array
1359607982 M * Guest136 ideally I would do the VMWare converter here
1359607991 M * Guest136 like I was able to do with the other Debian based bare metal hardware
1359608006 M * Bertl so why not do the same with the Linux-VServer host?
1359608019 M * Guest136 The output so far has been "unable to query the live linux machine"
1359608037 M * Guest136 Will that work if the root file system is over iscsi to the san?
1359608044 M * Guest136 or will it continue to try and talk to the san?
1359608052 M * Guest136 that wouldn't help me
1359608087 M * Bertl see, that's my point, the problem is not the guest, but the host system/lan connection
1359608092 M * Guest136 yes
1359608101 M * Guest136 I would agree
1359608105 M * Bertl so, IMHO, the simplest approach would be the following:
1359608131 M * Bertl setup a brand new Linux-VServer host in your ESX environment (pick a distro you like)
1359608149 M * Bertl simply move the guest over to the new host (rsync, tar, dump, etc)
1359608171 M * Bertl as the Linux-VServer guests are hardware and host distro agnostic, it will just work
1359608209 M * Guest136 any supported way to get this virtual machine out of vserver and into esxi after that?
1359608218 M * Guest136 just dd it?
1359608219 M * Guest136 :-)
1359608239 M * Bertl nah, that is what I meant with add back the hardware related stuff
1359608253 M * Bertl i.e. there is no disk image for Linux-VServer guests
1359608273 M * Guest136 :-(
1359608274 M * Bertl and the guest is missing all the stuff you need to run it stand alone
1359608287 M * Bertl e.g. bootloader, hardware detection and setup, etc
1359608307 M * Guest136 how do you move it to KVM then?
1359608337 M * Bertl you install a host in kvm, then you move the guest
1359608344 M * Guest136 ah
1359608356 M * Guest136 so once this is in Linux Vserver it's just in Linux Vserver forever?
1359608362 M * Guest136 unless we rebuild the machine?
1359608373 M * Bertl unless you add back the missing parts
1359608410 M * Bertl but that's usually more time consuming than simply keeping it as Linux-VServer guest
1359608432 M * Bertl as there is no measureable overhead of running Linux-VServer guests on a Linux-VServer host, there is no reason not to go that way
1359608471 M * Guest136 I'm afraid I must be missing how to add back the missing parts:  The boot loader, driver detection and setup.  
1359608489 M * Guest136 Can I copy this file system to a new san and add those in? then simply dd it to a vm drive and boot?
1359608501 M * Bertl do you have an idea how Linux-VServer works?
1359608509 M * Guest136 Its paravirtualization
1359608513 M * Bertl nope
1359608518 M * Guest136 the kernel and system resources are shared with the guest
1359608521 M * Bertl it is isolation
1359608524 M * Guest136 okay then i'm sorry I don't
1359608537 M * Guest136 so it has a hypervisor and each guest has its own kernel?
1359608538 M * Bertl you know what chroot does?
1359608548 Q * yang Server closed connection
1359608550 J * yang yang@yang.netrep.oftc.net
1359608559 M * Guest136 not explicitly :-(
1359608566 M * Bertl maybe you know bsd jails?
1359608601 M * Guest136 I cut my teeth on building custom OpenVZ images with Proxmox a few years ago.  Thats as much experience as I have.
1359608609 M * Guest136 with this non-commercial stuff
1359608622 M * Bertl okay, no problem, that's close
1359608665 M * Bertl i.e. in Linux-VServer, processes run side by side (under the same kernel) isolated from each other (so other 'domains' are not visible to them)
1359608695 M * Bertl but they still use the same kernel to access devices, hardware, memory, etc
1359608759 M * Bertl the Linux-VServer kernel (patch) allows for this isolation and the management of those isolation domains (we call them contexts)
1359608803 M * Guest136 ok
1359608809 M * Bertl so, the guest system is basically a full distro install placed somewhere in the filesystem of the host
1359608815 M * Guest136 seems like I misunderstood the term paravirtualization
1359608837 M * Guest136 I took it to represent the exact environment you have described
1359608838 M * Bertl usually stripped down to the parts which are required _after_ a successful bootup
1359608852 M * Bertl paravirtualization is what xen does
1359608887 M * Guest136 ok
1359608913 M * Guest136 so the guests filesystem on the iSCSI device needs a host system boot into
1359608919 M * Guest136 there is a custom kernel setup to accommodate this 
1359608930 M * Guest136 the host os is the one with the hardware drivers
1359608932 M * Guest136 the grub install
1359608941 M * Bertl yes, once the host is booted, the guest can be started
1359608946 M * Guest136 yes
1359608951 M * Guest136 so...
1359608964 M * Guest136 if I install Debian onto a new box
1359608966 M * Bertl so, the simplest way to preserve a guest (which is, what you are interested in, no?)
1359608972 M * Guest136 and simple rsync the guest over it
1359608980 M * Guest136 it should work right?
1359608993 M * Bertl might work, might not work, depends on the debian version and the guest setup
1359609003 M * Guest136 ok
1359609009 M * Guest136 if the guest and the new host were the same debian version
1359609020 M * Guest136 … just brainstorming here
1359609030 M * Bertl but what will work for sure is to install a new debian (or whatever) system and a Linux-VServer kernel
1359609044 M * Guest136 trouble is getting that data over without downtime
1359609063 M * Guest136 I can't initiate an iSCSI connection to this SAN
1359609067 M * Guest136 I have no documentation
1359609073 M * Guest136 no passwords for it
1359609073 M * Bertl no downtime required to move the guest
1359609079 M * Guest136 well I'll do it now then
1359609089 M * Guest136 I have the Debian ISO already on the VMWare ESXi environment
1359609090 M * Bertl all you need is logon to the Linux-VServer host
1359609092 M * Guest136 I'll just install it
1359609096 M * Guest136 I have that
1359609111 M * Guest136 how long will you be on?
1359609113 M * Bertl so, that's enough to rsync the guest over to the new host
1359609158 M * Bertl I'm usually around, but often busy, just ask if you need something I'll reply when I read it (or somebody else here will)
1359609179 M * Guest136 can you walk me through the copy process then?
1359609183 M * Guest136 in case no one is around
1359609190 M * Guest136 I can rsync this over?
1359609192 M * Guest136 scp this over?
1359609196 M * Guest136 what would you recommend?
1359609203 M * Bertl rsync is better, and yes, that works for the guest data
1359609214 M * Guest136 doesn't the host have configs that are specific for the guest?
1359609265 M * Guest136 like /etc/network seems to be configured for guests
1359609892 M * Bertl yep
1359609905 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1359609918 M * Bertl as I said, all hardware related configuration is done on the host
1359611282 J * Ghislain ~aqueos@adsl1.aqueos.com
1359613794 Q * tolkor Server closed connection
1359613805 J * tolkor ~rj@tdream.lly.earlham.edu
1359615942 J * nkukard_ ~nkukard@196-210-205-18.dynamic.isadsl.co.za
1359616088 Q * nkukard Ping timeout: 480 seconds
1359616558 M * Guest136 Bertl: is there any reason I couldn't install Ubunt on this new server instead of Debian?
1359620228 M * Bertl for the host, it doesn't matter
1359620250 M * Bertl i.e. can be ubuntu or redhat or gentoo ... whatever you like
1359620262 M * Bertl the guest distro does not depend on the host distro
1359620868 M * Guest136 ok
1359620871 M * Guest136 I built a debian box
1359620873 M * Guest136 its up
1359620880 M * Guest136 how do I move the data to it?
1359620999 M * Bertl make sure that the host is working correctly first, including the Linux-VServer setup
1359621021 M * Bertl then simply rsync (with -axHPSD --numeric-ids) the guest data and config
1359621684 M * Guest136 ok, going to install vmware tools and the correct kernel then I'll try the rsync command
1359623946 J * fisted_ ~fisted@xdsl-87-78-233-241.netcologne.de
1359623954 Q * fisted Remote host closed the connection
1359623962 N * fisted_ fisted
1359624335 J * bonbons ~bonbons@2001:a18:1:1402:2c0:9fff:fe2d:39d
1359628517 Q * ensc|w Server closed connection
1359628825 J * ensc|w ~ensc@www.sigma-chemnitz.de
1359629816 Q * wmp Read error: Connection reset by peer
1359630010 Q * fisted Remote host closed the connection
1359630071 J * fisted ~fisted@xdsl-78-35-93-174.netcologne.de
1359630760 Q * Guest136 Quit: Guest136
1359632860 J * clopez ~clopez@fanzine.igalia.com
1359633525 Q * Rockj Ping timeout: 480 seconds
1359633625 J * Rockj rockj@rockj.net
1359635401 Q * ircuser-1 Ping timeout: 480 seconds
1359638045 N * ensc Guest187
1359638055 J * ensc ~irc-ensc@p54ADF7A5.dip.t-dialin.net
1359638463 Q * Guest187 Ping timeout: 480 seconds
1359638979 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1359639124 J * wmp ~wmp@2001:41d0:1:8616::1
1359639803 Q * fisted Quit: leaving
1359639814 J * fisted ~fisted@xdsl-78-35-93-174.netcologne.de
1359640674 Q * sid3windr Server closed connection
1359640675 J * sid3windr luser@bastard-operator.from-hell.be
1359643490 Q * Defaultti Server closed connection
1359643660 J * Defaultti defaultti@lakka.kapsi.fi
1359643691 Q * bonbons Quit: Leaving
1359648551 M * Bertl off for a nap ... bbl
1359648558 N * Bertl Bertl_zZ
1359651343 J * BenG ~bengreen@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com
1359655509 Q * BenG Ping timeout: 480 seconds
1359656738 J * BenG ~bengreen@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com
1359657572 Q * BenG Read error: Connection reset by peer
1359657772 Q * clopez Ping timeout: 480 seconds
1359657927 Q * Rockj Ping timeout: 480 seconds
1359658722 Q * sladen Server closed connection
1359659473 J * sladen ~paul@starsky.19inch.net
1359660812 Q * ncopa Remote host closed the connection
1359660828 Q * sannes Remote host closed the connection
1359660846 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no
1359663074 Q * tokkee Server closed connection
1359664577 J * tokkee tokkee@osprey.tokkee.org
1359665562 J * _WildPikachu_ ~nkukard@196-215-197-16.dynamic.isadsl.co.za
1359665712 Q * nkukard_ Ping timeout: 480 seconds
1359667042 Q * _Shiva_ Server closed connection
1359667043 J * _Shiva_ shiva@whatcha.looking.at
1359667674 N * Bertl_zZ Bertl
1359667677 M * Bertl back now ...
1359671778 Q * grobie Server closed connection
1359671780 J * grobie ~grobie@tyr.schnuckelig.eu
1359673210 Q * fisted Remote host closed the connection
1359673330 J * fisted ~fisted@xdsl-87-78-235-170.netcologne.de
1359673485 Q * Ghislain Quit: Leaving.
1359674210 Q * Jb_boin Server closed connection
1359674232 J * Jb_boin ~dedior@proxad.eu
1359675224 Q * imachine Server closed connection
1359675235 J * imachine ~imachine@robot.greenhost24.pl