Matthew Franz | 1 Oct 01:21 2011
Picon

Re: Checkpoint and restore on 64 bit Debian host.

I'm currently running several servers (for development environments)
on Debian Squeeze but am in the process of migrating to CentOS 6
because it seems to be a better supported environment and also
provides an LTS OS, whereas Debian's support lifecycle is more
"nuanced."

My assumption is also a larger bas of OpenVZ users run on
RHEL-derivatives than Debian, so it is always a safer bet. Running
RHEL6 kernels on Debian boxes since more problematic than migrating to
CentOS, even though I prefer Debian-based distros.

My other concern is the long term viability of OpenVZ on
non-RHEL-based distributions given that Ubuntu dropped OpenVZ support
and it seems that Debian will as well, given that (for good or evil)
LXC seems to be the container-based solution that Debian and Ubuntu
are going forward with.

The only problem I've encountered with OpenVZ on Debian (which is also
a concern) is http://bugzilla.openvz.org/show_bug.cgi?id=1747

- mdf

On Fri, Sep 30, 2011 at 6:05 PM, Kirill Kolyshkin
<kolyshkin@...> wrote:
> You don't have to switch the OS, just use rhel6 kernel. It is in rpm so for
> now you have to use alien plus do some work after installing new kernel (run
> mkinitd, modify grub.conf). We plan to provide deb report for rhel6 kernel
> real soon.
>
> On Sep 30, 2011 8:49 PM, "Hansel Dunlop" <hansel.dunlop@...>
(Continue reading)

Kir Kolyshkin | 1 Oct 03:53 2011

Re: chkpt/vzmigrate with SSL connections

Please file a bug to bugzilla.openvz.org

On Oct 1, 2011 2:24 AM, "Dariush Pietrzak" <ml-openvz-eyck <at> kuszelas.eu> wrote:
> Hi
> I recently tried migrating live postgresql slave, and it failed, right
> after migration such messages appeared in logfile:
>
>
> 011-10-01 00:04:39 CEST LOG: invalid record length at 0/2B008258
> 2011-10-01 00:04:52 CEST FATAL: no free slots in PMChildFlags array
> 2011-10-01 00:04:52 CEST LOG: process 10745 releasing ProcSignal slot 2056, but it contains 0
> 2011-10-01 00:04:54 CEST LOG: process 10743 releasing ProcSignal slot 2055, but it contains 0
> 2011-10-01 00:05:31 CEST FATAL: could not receive data from WAL stream: SSL connection has been closed unexpectedly
>
> 2011-10-01 00:05:31 CEST LOG: process 10746 releasing ProcSignal slot 2058, but it contains 0
>
> since it's just hot-standby and there was no reports running on it, it was safe to restart, so:
>
> 2011-10-01 00:05:39 CEST LOG: database system was interrupted while in recovery at log time 2011-10-01 00:03:43 CEST
> 2011-10-01 00:05:39 CEST HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
> 2011-10-01 00:05:39 CEST LOG: incomplete startup packet
> 2011-10-01 00:05:39 CEST LOG: entering standby mode
> 2011-10-01 00:05:39 CEST LOG: consistent recovery state reached at 0/2B008258
> afterwards it started working fine.
>
> Kernel is RHEL6 from 17 sep, machines between which guest was being migrated
> are identical, I'm not sure if the problem was in SSL contexts becoming
> corrupted, or was it somehow related to postgresql inner workings...
> I do believe I have successfully transfered running postgresqls before, this
> was my first attempt of moving PG with running replication, so I assume the
> problem might be related to SSL.
> Anyone else encountered something like this?
>
> (I do know that dhcp3 servers require restart after online migration, this is first
> time I see applications reporting data corruption in such case)
>
> best regards, Eyck
> --
> Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
> Total Existance Failure
> _______________________________________________
> Users mailing list
> Users-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
> https://openvz.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users
Lst_hoe02 | 3 Oct 12:48 2011
Picon

Re: Ubuntu 10.04 template issue

Zitat von Mark Johanson <mjohanson@...>:

>
> On Thu, 2011-09-29 at 12:00 -0400, users-request@... wrote:
>
>>         /etc/init/networking.conf
>>
>>         Change
>>
>>         start on (local-filesystems and stopped udevtrigger)
>>
>>         to something like this
>>
>>         start on (local-filesystems)
>>
>
> Thanks for the information on what to change, unfortunately that appears
> to already be set that way:
>
> start on local-filesystems
>
> task
>
> pre-start exec mkdir -p /var/run/network
>
> exec ifup -a
>
> I'll keep digging to see if udev is loading up somewhere else causing a
> issue, but any other suggestions on what to look at would be greatly
> appreciated.

Try to debug what is going on inside the VE by issuing "vzctl exec  
<VE-ID> ifconfig" and maybe looking at the VE logfiles. Another glitch  
for SSH is using OOM settings in the startupscript /etc/init/ssh.conf  
BTW.

Good luck

Andreas

Attachment (smime.p7s): application/pkcs7-signature, 8170 bytes
_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users
Hansel Dunlop | 4 Oct 19:00 2011

Re: Checkpoint and restore on 64 bit Debian host.

Thanks Kiril,

I'm experimenting with this now. I converted vzkernel-2.6.32-042stab037.1.x86_64.rpm into a deb and used it to boot but AWS did not want to run it. Complaining about XEN options. I see that the older kernel versions had specific XEN builds. I'm going to try and recompile the  2.6.32-042stab037 kernel from src. Are there any particular flags that I should set?

I did a diff on the config for a working Debian kernel and the EL6 version from OpenVZ, these are the options that relate to XEN. I guess I could just set them all and see if that works.

Debian is >
OpenVZ is < < CONFIG_XEN_MAX_DOMAIN_MEMORY=128                                                                                           > CONFIG_XEN_MAX_DOMAIN_MEMORY=32                                                                                            < CONFIG_XEN_DEBUG_FS=y                                                                                                      > # CONFIG_XEN_DEBUG_FS is not set                                                                                           > CONFIG_SWIOTLB_XEN=y                                                                                                       > CONFIG_MICROCODE_XEN=y                                                                                                     > CONFIG_XEN_DOM0=y                                                                                                          > CONFIG_XEN_PRIVILEGED_GUEST=y                                                                                              > CONFIG_XEN_DOM0_PCI=y                                                                                                      > # CONFIG_XEN_PCI_PASSTHROUGH is not set                                                                                    > CONFIG_PCI_XEN=y                                                                                                           > CONFIG_XEN_PCIDEV_FRONTEND=y                                                                                               > CONFIG_XEN_BACKEND=y                                                                                                       > CONFIG_XEN_NETDEV_BACKEND=y                                                                                                > CONFIG_XEN_BLKDEV_BACKEND=y                                                                                                > CONFIG_XEN_BLKDEV_TAP=m                                                                                                    > CONFIG_XEN_BLKBACK_PAGEMAP=y                                                                                               > CONFIG_XEN_PCIDEV_BACKEND=y                                                                                                > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y                                                                                           > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set                                                                                > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set                                                                                > # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set                                                                          > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set                                                                                    > CONFIG_XEN_MCE=y                                                                                                           > CONFIG_XEN_XENBUS_FRONTEND=y                                                                                               > CONFIG_XEN_GNTDEV=y                                                                                                        > CONFIG_XEN_S3=y                                                                                                            > CONFIG_ACPI_PROCESSOR_XEN=m     
Kind regards

Hansel

On 30/09/2011 23:05, Kirill Kolyshkin wrote:

You don't have to switch the OS, just use rhel6 kernel. It is in rpm so for now you have to use alien plus do some work after installing new kernel (run mkinitd, modify grub.conf). We plan to provide deb report for rhel6 kernel real soon.

On Sep 30, 2011 8:49 PM, "Hansel Dunlop" <hansel.dunlop-tPwS4dq8XOShEniVeURVKkEOCMrvLtNR@public.gmane.org> wrote:
> Hello,
>
> A question for the list.
>
> We have developed a web service on 64 bit Debian locally on ZEN and for
> deployment on AWS. We really want to use OpenVZ so that we can give our
> users persistent console sessions across deployments of our software.
>
> During our experiments with OpenVZ we discovered that Chkpt/Restore
> doesn't work on 64 bit Debian (or we couldn't make it work) which seems
> to be a known problem.
>
> We figure it could be three or four weeks of work to switch to CentOS or
> Scientific Linux.
>
> What advice do people have? I've been reading through the mailing lists
> but I don't feel like I have a clear picture of what is working and what
> is not right now. Are there events in the near future which might make
> this easier? Does anyone have working checkpointing on 64 bit Debian?
> Would it be quicker for us to try and fix the Debian issue itself?
>
> Any advice greatly appreciated!
>
> Kind regards
>
> --
> Hansel Dunlop
> hansel.dunlop-tPwS4dq8XOShEniVeURVKkEOCMrvLtNR@public.gmane.org
>
> PythonAnywhere: A console in your browser
> http://pythonanywhere.com
>
>
> _______________________________________________
> Users mailing list
> Users-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
> https://openvz.org/mailman/listinfo/users


_______________________________________________ Users mailing list Users-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org https://openvz.org/mailman/listinfo/users


-- Hansel Dunlop hansel.dunlop-tPwS4dq8XOShEniVeURVKkEOCMrvLtNR@public.gmane.org +44 7 5959 16478 PythonAnywhere: A console in your browser <http://pythonanywhere.com/> 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329. Registered address: 843 Finchley Road, London NW11 8NA, UK
_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users
Dietmar Maurer | 4 Oct 19:47 2011

RE: Checkpoint and restore on 64 bit Debian host.

> I'm experimenting with this now. I converted vzkernel-2.6.32-
> 042stab037.1.x86_64.rpm into a deb and used it to boot but AWS did not want
> to run it. Complaining about XEN options. I see that the older kernel versions had
> specific XEN builds. I'm going to try and recompile the  2.6.32-042stab037 kernel
> from src. Are there any particular flags that I should set?

You could also use the pve kernel from:

ftp://download.proxmox.com/debian/dists/squeeze/pve/binary-amd64/pve-kernel-2.6.32-6-pve_2.6.32-46_amd64.deb

That is the latest openvz kernel compiled for debian squeeze.

- Dietmar
Hristo Benev | 4 Oct 23:49 2011
Picon

Kernel 028stab094.3 not in current

 kernel/rhel5/028stab094.3 not moved in current

http://bugzilla.openvz.org/show_bug.cgi?id=2024


-----------------------------------------------------------------
100 лв БОНУС. Най-високи коефициенти. Tempobet.com
http://bg.tempobet.com/affiliates/3208311


_______________________________________________
Users mailing list
Users <at> openvz.org
https://openvz.org/mailman/listinfo/users

Daniel Bauer | 6 Oct 15:02 2011
Picon

several nics on the hn

Hello,

I've several nics on the hostnode. Only the internal service nic have an
internal IP. The other nics are without IPs and connected to different
internal subnets and public www.

I've read the differences between venet and veth
http://wiki.openvz.org/Differences_between_venet_and_veth
and want to use venet, but only venet0 is active in the hn, I think this
is connected to eth0, but how to access the other nics?

Thanks
Daniel
Gary Wallis | 6 Oct 15:24 2011

Re: several nics on the hn


Edit your:

/etc/vz/vz.conf

Specifically the VE_ROUTE_SRC_DEV value

...
# The name of the device whose IP address will be used as source IP for CT.
# By default automatically assigned.
#VE_ROUTE_SRC_DEV="eth0"
...

Daniel Bauer wrote:
> Hello,
> 
> I've several nics on the hostnode. Only the internal service nic have an
> internal IP. The other nics are without IPs and connected to different
> internal subnets and public www.
> 
> I've read the differences between venet and veth
> http://wiki.openvz.org/Differences_between_venet_and_veth
> and want to use venet, but only venet0 is active in the hn, I think this
> is connected to eth0, but how to access the other nics?
> 
> Thanks
> Daniel
> 
> _______________________________________________
> Users mailing list
> Users@...
> https://openvz.org/mailman/listinfo/users
> 
> 
Gary Wallis | 6 Oct 15:33 2011

Re: several nics on the hn

If you need to have some containers use other NICs than the default, you 
will need to probably to do some ip route stuff. Pretty advanced topic. 
Of course you can always give container direct access to /dev devices 
(like /dev/net/tun) via it's VEID.conf file. But that would involve all 
kinds of very advanced routing and kernel expertise for sharing the 
device among more than one container.
Esmé de Wolf | 6 Oct 15:55 2011
Picon

RE: several nics on the hn

Hi Daniel,

What's your setup? You have 1 'internal' NIC with an IP-address and other
NIC's without IP-address who you want to connect inside a container, for
what purpose?

If you use veth you could theoretically set up a bridge with one of those
devices, that would be easiest in my opinion. But why would you consist on
venet?

Probably with a little bit more information we can help you a bit further.

Kind Regards,

Esmé

-----Oorspronkelijk bericht-----
Van: users-bounces@...
[mailto:users-bounces@...] Namens
Daniel Bauer
Verzonden: donderdag 6 oktober 2011 15:02
Aan: users@...
Onderwerp: [Users] several nics on the hn

Hello,

I've several nics on the hostnode. Only the internal service nic have an
internal IP. The other nics are without IPs and connected to different
internal subnets and public www.

I've read the differences between venet and veth
http://wiki.openvz.org/Differences_between_venet_and_veth
and want to use venet, but only venet0 is active in the hn, I think this is
connected to eth0, but how to access the other nics?

Thanks
Daniel

_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users

Gmane