Re: [Users] Issues after updating to 7.0.14 (136)

2020-07-02 Thread Jehan Procaccia IMT
"updating to 7.0.14 (136)" !? I did an update yesterday , I am far behind that version /# cat /etc/vzlinux-release// / /Virtuozzo Linux release 7.8.0 (609)/ / / /# uname -a // //Linux localhost 3.10.0-1127.8.2.vz7.151.14 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 x86_64 x86_64 GNU/Linux// / why

Re: [Users] Issues after updating to 7.0.14 (136)

2020-07-06 Thread Jehan Procaccia IMT
Hello, I am back to the initial pb related to that post , since I updated to /OpenVZ release 7.0.14 (136)  | ///Virtuozzo Linux release 7.8.0 (609)// , I am also facing CT corrupted status . I don't see the exact same error as mentioned by Kevin Drysdale below (ploop/fsck) , but I am not abl

[Users] reload or refresh list of CT after move an already registered CT

2020-07-06 Thread Jehan Procaccia IMT
Hello because I have a fail CT on a hardware node , cf https://lists.openvz.org/pipermail/users/2020-July/007928.html I moved manually the CT files (hdds, conf, etc ...) to another hardware node (HW) that doesn't seem to have the pb yet ( not updateded to OpenVZ release 7.0.14 (136)) I did

Re: [Users] reload or refresh list of CT after move an already registered CT

2020-07-06 Thread Jehan Procaccia IMT
ot; service when you have this kind of problems and/or to "prlctl unregister" and/or "vzctl unregister". On 7/6/20 5:07 PM, Jehan Procaccia IMT wrote: Hello because I have a fail CT on a hardware node , cf https://lists.openvz.org/pipermail/users/2020-July/007928.html I

Re: [Users] Issues after updating to 7.0.14 (136)

2020-07-06 Thread Jehan Procaccia IMT
/private/144dc737-b4e3-4c03-852c-25a6df06cee4/root.hdd/root.hds already used by device /dev/ploop11432 # df -H | grep ploop11432 => nothing I am lost , any help appreciated  . Thanks . Le 06/07/2020 à 15:37, Jehan Procaccia IMT a écrit : Hello, I am back to the initial pb related to that p

[Users] routing between CT and EBtables

2020-10-05 Thread Jehan Procaccia IMT
Hello for students labs purpose, we use openvz7 CTs that have multiple interface and IPs for network simulation (routing) we notice that CT default configuration seems to drop packets ( ebtables ?) that are emitted from a different IP that the one configured for the CT itself . although it

[Users] Virtuozzo containers no longer a supported Virtuozzo product !?

2020-12-04 Thread Jehan Procaccia IMT
Hello defending the added value of virtuozzo containers (CT) , one replied me with : https://www.virtuozzo.com/support/all-products/virtuozzo-containers.html /*Please note*: Virtuozzo Containers for Linux is no longer a supported Virtuozzo product. Users can purchase extended support until

Re: [Users] Virtuozzo containers no longer a supported Virtuozzo product !?

2020-12-04 Thread Jehan Procaccia IMT
uozzo Hybrid Server" is basically what we have in openvz 7, plus premium features. Joe On Fri, Dec 4, 2020 at 10:36 AM Jehan Procaccia IMT mailto:jehan.procac...@imtbs-tsp.eu>> wrote: Hello defending the added value of virtuozzo containers (CT) , one replied me with :

Re: [Users] Virtuozzo containers no longer a supported Virtuozzo product !?

2020-12-04 Thread Jehan Procaccia IMT
a plus, for instance if I have to hold my nose     > and spin up a windows VM for testing.     >     > Jake     >     >     >     > On Fri, Dec 4, 2020 at 11:06 AM Jehan Procaccia IMT     > <mailto:jehan.procac...@imtbs-tsp.eu> <mailto:jehan.procac...@imtbs-tsp.eu