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" <[email protected] <mailto:[email protected]>> 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
> [email protected] <mailto:[email protected]>
>
> PythonAnywhere: A console in your browser
> http://pythonanywhere.com
>
>
> _______________________________________________
> Users mailing list
> [email protected] <mailto:[email protected]>
> https://openvz.org/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users


--
Hansel Dunlop
[email protected]
+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
[email protected]
https://openvz.org/mailman/listinfo/users

Reply via email to