On Tue, 30 Mar 2010, Steven Crothers wrote:
Perhaps this question is better suited to the libvirt list? Since OpenVZ
does nothing to support libvirt afaik...
I have actually, the problem is libvirt already supports all of this, the
issue is on the interfacing with OpenVZ side of things just l
Perhaps this question is better suited to the libvirt list? Since OpenVZ
does nothing to support libvirt afaik...
-Original Message-
From: users-boun...@openvz.org [mailto:users-boun...@openvz.org] On Behalf
Of Nathan Stratton
Sent: Tuesday, March 30, 2010 9:41 PM
To: users@openvz.org
Subj
I found my bug report from October 2009 about not being able to stop
containers.
http://bugzilla.openvz.org/show_bug.cgi?id=1345
Back then we couldn't replicate it, and we chalked it up to "must have
already been fixed" or to issues with the VE configs, but here it is today.
Any ideas as to h
Is there anyone on this list that can update me on the progress of libvirt
integration with openvz? With the latest libvirt I am able to start and
stop a domain that is defined with a openvz config file, but I have not
yet been able to migrate to full libvirt control As an example migration
d
What does this mean?
CT: 85: failed to start with err=-12
I see that -12 is ENOMEM. Does this really indicate that my HN is "full"
and can't run anymore VEs?
Also, can someone explain to me the proper usage of vzmemcheck and how
to interpret its output?
--
HostGIS, Open Source solutions for
On Tue, Mar 30, 2010 at 4:42 PM, Gregor at HostGIS wrote:
>> It gets locked up trying to stop nfsmount. I believe
>> the problem is the virtual nic is down before the nfsmount tries to
>> stop and nfsmount waits forever to close the connection to the
>> server..
>
> Interesting. No connections mad
It gets locked up trying to stop nfsmount. I believe
the problem is the virtual nic is down before the nfsmount tries to
stop and nfsmount waits forever to close the connection to the
server..
Interesting. No connections made here, though; no NFS or similar.
Would that apply to open listening s
Thorsten Schifferdecker wrote:
and any entries logged in kern.log/dmesg as well ?
Nope. Just the same message "CT: 85: failed to start with err=-12"
--
HostGIS, Open Source solutions for the global GIS community
Greg Allensworth - SysAdmin, Programmer, GIS Person, Security
Network+ Server
What template are you using and where did you get it from?
Slackware 11 I created it myself, based on a working system.
This is the same template which we had used previously those months ago,
when we weren't able to replicate the bug.
Can you vzctl enter it?
Nope. "enter into CT 84 fai
Hi,
and any entries logged in kern.log/dmesg as well ?
Bye,
Thorsten
Steven Crothers schrieb:
> What template are you using and where did you get it from?
>
> I recently had a similar result from an Archlinux template, however I would
> need to know more about the container to be able to relate
> I recently had a similar result from an Archlinux template, however I would
> need to know more about the container to be able to relate it to my case.
>
> Can you vzctl enter it?
>
I have a restart problem on a self made gentoo container however I
know the cause. It gets locked up trying to sto
What template are you using and where did you get it from?
I recently had a similar result from an Archlinux template, however I would
need to know more about the container to be able to relate it to my case.
Can you vzctl enter it?
-Original Message-
From: users-boun...@openvz.org [mail
Hey guys. I reported a bug some months ago, not being able to stop and
restart a container, getting a timeout instead. When I reported the bug
months ago, I was unable to replicate it at the time. But here it is
once again: I cannot stop or restart the VE.
This clip shows the results which I s
13 matches
Mail list logo
