Can I somehow identify the physical machine from inside an OpenVZ container?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am using some VPSes in OpenVZ containers. As I can see, our hosting provider somes moves them between his physical machines. It also means unwaited (and unexpected) reboots.
I have no technical contact with the VPS provider (there is a... complex company structure ;-) ), but I would like to know, what is happening and why.
I checked the /proc/cpuinfo, yes it sometimes changes. But it is not enough.
Can I somehow extract some ID about the host machine, while I have only a root access to the VPS (and zero access to the host)?
proc sysfs openvz
asked Sep 16 at 17:15
peterh
4,03292755
add a comment |Â
up vote
1
down vote
favorite
I am using some VPSes in OpenVZ containers. As I can see, our hosting provider somes moves them between his physical machines. It also means unwaited (and unexpected) reboots.
I have no technical contact with the VPS provider (there is a... complex company structure ;-) ), but I would like to know, what is happening and why.
I checked the /proc/cpuinfo, yes it sometimes changes. But it is not enough.
Can I somehow extract some ID about the host machine, while I have only a root access to the VPS (and zero access to the host)?
proc sysfs openvz
asked Sep 16 at 17:15
peterh
4,03292755
As far as I remember openvz: only if the hosting provider has set something up that allows you to.
– Henrik
Sep 16 at 17:32
@Henrik Thanks! I've tought onrdtscto read the cpu cycles since the last poweron from the host cpu; and maybe somehow some cpuid is also available. I think the OpenVZ may have some intentional mechanism to avoid it, but it is not sure.
– peterh
Sep 16 at 17:45
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am using some VPSes in OpenVZ containers. As I can see, our hosting provider somes moves them between his physical machines. It also means unwaited (and unexpected) reboots.
I have no technical contact with the VPS provider (there is a... complex company structure ;-) ), but I would like to know, what is happening and why.
I checked the /proc/cpuinfo, yes it sometimes changes. But it is not enough.
Can I somehow extract some ID about the host machine, while I have only a root access to the VPS (and zero access to the host)?
proc sysfs openvz
asked Sep 16 at 17:15
peterh
4,03292755
I am using some VPSes in OpenVZ containers. As I can see, our hosting provider somes moves them between his physical machines. It also means unwaited (and unexpected) reboots.
I have no technical contact with the VPS provider (there is a... complex company structure ;-) ), but I would like to know, what is happening and why.
I checked the /proc/cpuinfo, yes it sometimes changes. But it is not enough.
Can I somehow extract some ID about the host machine, while I have only a root access to the VPS (and zero access to the host)?
proc sysfs openvz
proc sysfs openvz
asked Sep 16 at 17:15
peterh
4,03292755
asked Sep 16 at 17:15
peterh
4,03292755
asked Sep 16 at 17:15
peterh
4,03292755
asked Sep 16 at 17:15
peterh
4,03292755
asked Sep 16 at 17:15
peterh
4,03292755
4,03292755
As far as I remember openvz: only if the hosting provider has set something up that allows you to.
– Henrik
Sep 16 at 17:32
@Henrik Thanks! I've tought onrdtscto read the cpu cycles since the last poweron from the host cpu; and maybe somehow some cpuid is also available. I think the OpenVZ may have some intentional mechanism to avoid it, but it is not sure.
– peterh
Sep 16 at 17:45
add a comment |Â
As far as I remember openvz: only if the hosting provider has set something up that allows you to.
– Henrik
Sep 16 at 17:32
@Henrik Thanks! I've tought onrdtscto read the cpu cycles since the last poweron from the host cpu; and maybe somehow some cpuid is also available. I think the OpenVZ may have some intentional mechanism to avoid it, but it is not sure.
– peterh
Sep 16 at 17:45
As far as I remember openvz: only if the hosting provider has set something up that allows you to.
– Henrik
Sep 16 at 17:32
As far as I remember openvz: only if the hosting provider has set something up that allows you to.
– Henrik
Sep 16 at 17:32
@Henrik Thanks! I've tought on
rdtsc to read the cpu cycles since the last poweron from the host cpu; and maybe somehow some cpuid is also available. I think the OpenVZ may have some intentional mechanism to avoid it, but it is not sure.– peterh
Sep 16 at 17:45
@Henrik Thanks! I've tought on
rdtsc to read the cpu cycles since the last poweron from the host cpu; and maybe somehow some cpuid is also available. I think the OpenVZ may have some intentional mechanism to avoid it, but it is not sure.– peterh
Sep 16 at 17:45
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f469417%2fcan-i-somehow-identify-the-physical-machine-from-inside-an-openvz-container%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
As far as I remember openvz: only if the hosting provider has set something up that allows you to.
– Henrik
Sep 16 at 17:32
@Henrik Thanks! I've tought on
rdtscto read the cpu cycles since the last poweron from the host cpu; and maybe somehow some cpuid is also available. I think the OpenVZ may have some intentional mechanism to avoid it, but it is not sure.– peterh
Sep 16 at 17:45