<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user">
    <title>gmane.linux.openvz.user</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5141"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5140"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5139"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5138"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5137"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5136"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5135"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5134"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5133"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5132"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5131"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5130"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5129"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5128"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5127"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5126"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5125"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5124"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5123"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.openvz.user/5122"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5141">
    <title>Re: vzctl error</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5141</link>
    <description>&lt;pre&gt;
Hmm, looks weird.

The fact that it works from console and doesn't work from ssh is 
interesting. Maybe you should compare your environment from console and ssh.

If you want I can take a look, email me privately.
_______________________________________________
Users mailing list
Users-GEFAQzZX7r8dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org
https://lists.openvz.org/mailman/listinfo/users
&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-22T12:44:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5140">
    <title>vzctl error</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5140</link>
    <description>&lt;pre&gt;Hi,

I have a strange error on one of our servers when I use vzctl. There's a 
running host with a few VE-s and if I type /vzctl enter "CTID"/ then I 
receive /enter into CT "CTID" failed/ and no further messages. After a 
lot of debugging I realized that it works if I directly connect via the 
server's console, but if I login via ssh it gives the error.
The system parameters:
OS: CentOS release 6.4
Kernel: Linux vm4 2.6.32-042stab078.10 #1 SMP Wed May 8 19:45:03 MSK 
2013 x86_64 x86_64 x86_64 GNU/Linux
vzctl: vzctl-core-4.2-1.el6.x86_64
          vzctl-4.2-1.el6.x86_64

I've tried to reboot the system with different kernels, but the same 
error. There's another strange thing: we have another machine with the 
same kernel but I cannot reproduce the error there.
I've also tried to run vzctl with gdb and search in the source code, and 
there seems to be a problem around setting up the environment:
In src/lib/hooks_vz.c there's a function:

/static int vz_env_create_ioctl(vps_handler *h, envid_t veid, int flags&lt;/pre&gt;</description>
    <dc:creator>Csiszár Tamás</dc:creator>
    <dc:date>2013-05-22T12:24:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5139">
    <title>Re: vzctl --noatime</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5139</link>
    <description>&lt;pre&gt;
Oops, it's a bit wrong, noatime should be ignored but I forgot to take 
into account that it comes with an argument.


Don't ask Google, ask GIT

http://git.openvz.org/?p=vzctl;a=commit;h=127ad44743

Then, for ploop CTs you can use --mount-opts parameter.
&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-13T21:28:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5138">
    <title>vzctl --noatime</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5138</link>
    <description>&lt;pre&gt;Hello all,

couple years ago vzctl had option --noatime. But now there is no such
option:

# vzctl set ${ve} --noatime yes --save
non-option ARGV-elements: --save

# man vzctl | grep noatime
#

What happened with it? Did not find anything about it in google.

&lt;/pre&gt;</description>
    <dc:creator>Nick Knutov</dc:creator>
    <dc:date>2013-05-13T20:39:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5137">
    <title>Re: AES-NI inside CT</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5137</link>
    <description>&lt;pre&gt;Aes-ni doesn't depend on containers features. Its just cpu instructions executed natively.
Probably difference in library set.

On 12.05.2013, at 2:02, "Nick Knutov" &amp;lt;mail-wOnFu4v91cPQT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Kirill Korotaev</dc:creator>
    <dc:date>2013-05-12T11:42:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5136">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5136</link>
    <description>&lt;pre&gt;Thanks for hints, I'll try to make rules file to be better, also just
realized need to add "Suggests" (may be even "Recommends") for
bash-completion too.




--
Best regards,
[COOLCOLD-RIPN]
&lt;/pre&gt;</description>
    <dc:creator>CoolCold</dc:creator>
    <dc:date>2013-05-12T01:15:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5135">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5135</link>
    <description>&lt;pre&gt;
It's just I already have make install* targets, they are developed with 
packaging in mind
(i.e. DESTDIR is supported). By doing your own install you basically 
duplicate the efforts
and code, and will have to add stuff if I add stuff.

I just realized I need "install-all" target.

&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-12T00:53:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5134">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5134</link>
    <description>&lt;pre&gt;To be honest, I'm not makefiles expert ;( and didn't even thought
about doing this way, so used much more simpler 'shell scripts'
methods ;)




--
Best regards,
[COOLCOLD-RIPN]
&lt;/pre&gt;</description>
    <dc:creator>CoolCold</dc:creator>
    <dc:date>2013-05-12T00:36:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5133">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5133</link>
    <description>&lt;pre&gt;Well, for vzstats scripts I'm trying to comply with Debian policy
which says (note about arch independent) :
It is recommended that supporting files and run-time support programs
that do not need to be invoked manually by users, but are nevertheless
required for the package to function, be placed (if they are binary)
in a subdirectory of /usr/lib, preferably under /usr/lib/package-name.
If the program or file is architecture independent, the recommendation
is for it to be placed in a subdirectory of /usr/share instead,
preferably under /usr/share/package-name. Following the package-name
naming convention ensures that the file names change when the shared
object version changes.

from: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-support-files
.
Though it is not strict, it is possible to move them into
/usr/lib/vzstats/bin , but I'm not sure this should be done. I suggest
to leave this as is.


On Sun, May 12, 2013 at 4:00 AM, Kir Kolyshkin &amp;lt;kir-GEFAQzZX7r8dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.o&lt;/pre&gt;</description>
    <dc:creator>CoolCold</dc:creator>
    <dc:date>2013-05-12T00:31:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5132">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5132</link>
    <description>&lt;pre&gt;
Speaking of location for vzstats scripts, I just looked into FHS, and it 
says internal
binaries should go to /usr/lib or a subdirectory. So it should be 
something like
/usr/lib/vzstats in our case. As usual, the problem is a mess of 
/usr/lib vs /usr/lib64
(at least in RPM world), therefore in vzctl I switched to /usr/libexec 
and did the same
in vzstats from the beginning.

But I will try to make it configurable now.


&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-12T00:00:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5131">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5131</link>
    <description>&lt;pre&gt;

Thanks a lot, I hope some Debian/Ubuntu users will install this.

For bash_completion, why don't you use something like
     make DESTDIR='$(INSTALL_DIR)' install-bashcomp
from debian/rules?

Same for other install targets.
For bin location, you can use REPDIR=/usr/share/vzstats/
(you still need to fix vzstats man page and script)

In fact let me try to have REPDIR configurable...

&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-11T23:47:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5130">
    <title>Re: vzstats 0.2.1 debianization</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5130</link>
    <description>&lt;pre&gt;I've updated debianization to match 0.3.2 version, source is available
on GitHub - https://github.com/CoolCold/vzstats .
Changes are:
1) including manpage
2) including bash completion
3) added deps for lsb_release

misses:
1) manpage does contain wrong paths like /usr/libexec/vzstats/ which
should be changed to proper Debian ones.

prebuild package for can be downloaded from
http://repo.coolcold.org/pool/main/v/vzstats/
or you may add
deb http://repo.coolcold.org/ squeeze-coolcold main contrib non-free
in sources.list to add repo ( http://repo.coolcold.org/README.TXT ).


On Wed, May 1, 2013 at 4:21 AM, CoolCold &amp;lt;coolthecold-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>CoolCold</dc:creator>
    <dc:date>2013-05-11T23:25:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5129">
    <title>AES-NI inside CT</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5129</link>
    <description>&lt;pre&gt;Hello,

on the node # openssl engine -t
(aesni) Intel AES-NI engine
     [ available ]

# vzctl enter 123
inside CT # openssl engine -t
(dynamic) Dynamic engine loading support
     [ unavailable ]

Does AES-NI available inside CT? Should I add some capabilities to CT or
something else?

&lt;/pre&gt;</description>
    <dc:creator>Nick Knutov</dc:creator>
    <dc:date>2013-05-11T21:34:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5128">
    <title>OpenVZ Maintenance Partnership</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5128</link>
    <description>&lt;pre&gt;Parallels is now offering an OpenVZ Maintenance Partnership program.
The program provides bug resolution support and feature development
to the OpenVZ community. The OpenVZ Maintenance Partnership has
a small annual fee and provides two benefits to partnership members.

1. Partnership members will receive a support ID that will allow them
to submit up to10 high priority bugs per year. These bugs will be placed
at the highest priority level in the development stack.

2. Partnership members will also be able to submit a feature request(s)
which will be reviewed by the Parallels engineering team. They will work
with you to clarify the requirements and implementation options and
provide an implementation estimate and a schedule.

Learn more and join the OpenVZ Maintenance Partnership here:
http://www.parallels.com/support/virtualization-suite/openvz/
&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-08T01:37:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5127">
    <title>Re: add second ploop device to CT</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5127</link>
    <description>&lt;pre&gt;
We are planning to add this functionality to vzctl, but there is no ETA yet.
If you need it now, you have to do it manually, using ploop utility
and vzctl mount/umount scripts.
&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-06T23:22:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5126">
    <title>Re: Openvz template for Debian Wheezy</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5126</link>
    <description>&lt;pre&gt;Hi Benjamin,

I've just tested your Wheezy template out of /contrib and it works out of
the box (latest OpenVZ kernel / tools here). Thanks!

On a side note, I noticed your template has the Germany mirrors configured
as well as Central European Summer Time. The official OpenVZ (Squeeze)
template has the US default mirrors configured (you could cp -a
/usr/share/doc/apt/examples/sources.list /etc/apt/sources.list in your
template, or use one of the Debian GeoMirror[1]) and the America/New_York
timezone (but perhaps yours could be configured to GMT if you prefer).

Thanks again!

[1] http://wiki.debian.org/DebianGeoMirror

Simon


On Mon, May 6, 2013 at 5:55 AM, Benjamin Henrion &amp;lt;bh-wt5ZJWH5N74&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

_______________________________________________
Users mailing list
Users-GEFAQzZX7r8dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org
https://lists.openvz.org/mailman/listinfo/users
&lt;/pre&gt;</description>
    <dc:creator>Simon Boulet</dc:creator>
    <dc:date>2013-05-06T20:00:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5125">
    <title>Re: Openvz template for Debian Wheezy</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5125</link>
    <description>&lt;pre&gt;Benjamin,

----- Original Message -----

I just added your submission to the contrib directory.

I think Kir needs to manually run something so it shows up on the fancy HTML page listing.

TYL,
&lt;/pre&gt;</description>
    <dc:creator>Scott Dowdle</dc:creator>
    <dc:date>2013-05-06T15:15:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5124">
    <title>add second ploop device to CT</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5124</link>
    <description>&lt;pre&gt;Hi all

Is it possible to add a second ploop device to a CT? If so, how?

I figured how to manually create a ploop image and mount it into the
running CT. However, I didn't know how to automate that on CT start.

Any hints are welcome.

Roman
&lt;/pre&gt;</description>
    <dc:creator>Roman Haefeli</dc:creator>
    <dc:date>2013-05-06T14:11:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5123">
    <title>Why does vzctl not check dirty flag of ploop device?</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5123</link>
    <description>&lt;pre&gt;Hi all

We are running several CTs on a cluster of a few OpenVZ host nodes. The
nodes share an NFS export where the ploop images of the CTs are located.

I noticed that 'vzctl start CTID' will happily start a ploop-based CT
that is already running on a different node. This is also possible with
simfs-CTs (having their private directory on NFS), but running a
ploop-CT on two nodes at the same time severely corrupts the CTs
filesystem. Before deploying such a setup, I would like to much sure
that this is avoided by any chance.

I found that a ploop imagefile will set a 'dirty flag' when it is in
use. Why doesn't 'vzctl' take that into accout? If 'vzctl' would read
that flag on CT start and refuse to start the CT when it is dirty, it
would not be possible to start the same CT twice.

I would like 'vzctl start $CTID' to do something like this:

ploop-fsck -f -r /vz/private/$CTID/root.hdd/root.hdd &amp;amp;&amp;amp; \
  vzctl start $CTID

What do you think?

Roman
&lt;/pre&gt;</description>
    <dc:creator>Roman Haefeli</dc:creator>
    <dc:date>2013-05-06T14:09:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5122">
    <title>Openvz template for Debian Wheezy</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5122</link>
    <description>&lt;pre&gt;Hi,

I just updated my debian wheezy template with the debian release of
this weekend:

http://filez.zoobab.com/openvz/templates/debian-7.0-x86_64.tar.gz

I created it with:

https://github.com/zoobab/openvz-scripts/blob/master/create-template-debian-amd64.sh

--
Benjamin Henrion &amp;lt;bhenrion at ffii.org&amp;gt;
FFII Brussels - +32-484-566109 - +32-2-3500762
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."
&lt;/pre&gt;</description>
    <dc:creator>Benjamin Henrion</dc:creator>
    <dc:date>2013-05-06T09:55:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.openvz.user/5121">
    <title>Re: "-R" TASK_ALIVE option</title>
    <link>http://permalink.gmane.org/gmane.linux.openvz.user/5121</link>
    <description>&lt;pre&gt;This is a wrong list, please use criu-GEFAQzZX7r8dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org
On May 3, 2013 8:48 AM, "Bhargav Bhikkaji" &amp;lt;bhargav.ietf-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

_______________________________________________
Users mailing list
Users-GEFAQzZX7r8dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org
https://lists.openvz.org/mailman/listinfo/users
&lt;/pre&gt;</description>
    <dc:creator>Kir Kolyshkin</dc:creator>
    <dc:date>2013-05-03T18:03:16</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.openvz.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.openvz.user</link>
  </textinput>
</rdf:RDF>
