Re: New installation v6.2 won't shutdown
Posted by pschaff on 2012/3/11 16:56:44
Quote:
I've noticed that, and generally find I get a configuration to suit my needs better by choosing Desktop and then adding development tools, particularly in a VM.
Quote:
That should get interesting. Last time I tried it all I managed was to lock up the guest.
Quote:
I agree, but apparently upstream thinks differently. It might also be good if the installer could detect if it was running on a virtualized system and adapt accordingly, but it currently does not, at least on VirtualBox or VMware.
artw wrote:
I had chosen the "Software Development Workstation" installation option and it included the virtualization software ... and also enabled it by default.
I've noticed that, and generally find I get a configuration to suit my needs better by choosing Desktop and then adding development tools, particularly in a VM.
Quote:
...
Disabling the service "fixed" my issue. I will leave the virtualization software there and try the vm fix ... see if I can get nested vm's working.
That should get interesting. Last time I tried it all I managed was to lock up the guest.
Quote:
Perhaps the hypervisor shouldn't be enabled by default on installation?
I agree, but apparently upstream thinks differently. It might also be good if the installer could detect if it was running on a virtualized system and adapt accordingly, but it currently does not, at least on VirtualBox or VMware.
Re: New installation v6.2 won't shutdown
Posted by artw on 2012/3/11 16:03:52
Quote:
Disabling the service "fixed" my issue. I will leave the virtualization software there and try the vm fix ... see if I can get nested vm's working.
Perhaps the hypervisor shouldn't be enabled by default on installation?
Thanks,
Art
gbohn wrote:
> Shutting Down...Running guests on default URI:
I just went through this myself running CentOS 6.2 64-bit under a VMware Workstation 8.0.2 host (Windows-7). If your issue is the same as mine, then this is a bug in the VMware Workstation 8.0.2 BIOS.
See the thread at http://communities.vmware.com/thread/391186?tstart=0 .
In my case, I tried the workaround of changing
vcpu.hotadd = "TRUE"
to
vcpu.hotadd = "FALSE"
in the VMs .vmx file and this solved my issue.
I was even able to start a nested Guest VM after this.
Alternately (if you don't care about getting nested Virtualization working), I found another way to avoid the shutdown issue. I discovered that I could just disable and stop the libvirt-guest service (from the System/Services panel) to avoid the shutdown issue (before I changed the VMware VMs .vmx file).
Good Luck.
Disabling the service "fixed" my issue. I will leave the virtualization software there and try the vm fix ... see if I can get nested vm's working.
Perhaps the hypervisor shouldn't be enabled by default on installation?
Thanks,
Art
Re: New installation v6.2 won't shutdown
Posted by artw on 2012/3/11 16:00:40
Quote:
I had chosen the "Software Development Workstation" installation option and it included the virtualization software ... and also enabled it by default.
Cheers,
Art
pschaff wrote:
You are inappropriately installing the hypervisor tools inside a virtual machine. I don't know if that is the cause of the shutdown issue, but it is certainly not a good thing to do.
I had chosen the "Software Development Workstation" installation option and it included the virtualization software ... and also enabled it by default.
Cheers,
Art
Re: New installation v6.2 won't shutdown
Posted by pschaff on 2012/2/21 11:23:22
First report I've seen on nested virtualization working - apparently a recent development, but still seems rather bleeding-edge.
Re: New installation v6.2 won't shutdown
Posted by gbohn on 2012/2/20 21:25:08
> Shutting Down...Running guests on default URI:
I just went through this myself running CentOS 6.2 64-bit under a VMware Workstation 8.0.2 host (Windows-7). If your issue is the same as mine, then this is a bug in the VMware Workstation 8.0.2 BIOS.
See the thread at http://communities.vmware.com/thread/391186?tstart=0 .
In my case, I tried the workaround of changing
vcpu.hotadd = "TRUE"
to
vcpu.hotadd = "FALSE"
in the VMs .vmx file and this solved my issue.
I was even able to start a nested Guest VM after this.
Alternately (if you don't care about getting nested Virtualization working), I found another way to avoid the shutdown issue. I discovered that I could just disable and stop the libvirt-guest service (from the System/Services panel) to avoid the shutdown issue (before I changed the VMware VMs .vmx file).
Good Luck.
I just went through this myself running CentOS 6.2 64-bit under a VMware Workstation 8.0.2 host (Windows-7). If your issue is the same as mine, then this is a bug in the VMware Workstation 8.0.2 BIOS.
See the thread at http://communities.vmware.com/thread/391186?tstart=0 .
In my case, I tried the workaround of changing
vcpu.hotadd = "TRUE"
to
vcpu.hotadd = "FALSE"
in the VMs .vmx file and this solved my issue.
I was even able to start a nested Guest VM after this.
Alternately (if you don't care about getting nested Virtualization working), I found another way to avoid the shutdown issue. I discovered that I could just disable and stop the libvirt-guest service (from the System/Services panel) to avoid the shutdown issue (before I changed the VMware VMs .vmx file).
Good Luck.
Re: New installation v6.2 won't shutdown
Posted by TrevorH on 2012/2/20 21:13:20
Remove all that libvirt\* set of packages, none of them should be installed on a client. The virt-what utility just tells you which virtualization package your guest is running underneath - your case you are apparently on a VMWare virtual machine.
Re: New installation v6.2 won't shutdown
Posted by pschaff on 2012/2/20 17:56:07
Pardon me, but nothing listed in post #3 is from VMware Tools.
Re: New installation v6.2 won't shutdown
Posted by artw on 2012/2/20 17:09:32
Quote:
Pardon? VMware Tools is an appropriate thing to install. Other than that, I didn't intentionally select any other hypervisor tools and tried to remove virt* things.
What needs to be removed, or installed "appropriately"?
Cheers,
Art
pschaff wrote:
You are inappropriately installing the hypervisor tools inside a virtual machine. I don't know if that is the cause of the shutdown issue, but it is certainly not a good thing to do.
Pardon? VMware Tools is an appropriate thing to install. Other than that, I didn't intentionally select any other hypervisor tools and tried to remove virt* things.
What needs to be removed, or installed "appropriately"?
Cheers,
Art
Re: New installation v6.2 won't shutdown
Posted by pschaff on 2012/2/20 16:10:56
You are inappropriately installing the hypervisor tools inside a virtual machine. I don't know if that is the cause of the shutdown issue, but it is certainly not a good thing to do.
Re: New installation v6.2 won't shutdown
Posted by artw on 2012/2/20 1:32:29
Sorry, I think I did a - yum remove virt* - and installed that virt-what today ... it comes back and says vmware.
Re: New installation v6.2 won't shutdown
Posted by artw on 2012/2/20 1:30:41
Installed Packages
libvirt.x86_64 0.9.4-23.el6_2.4 @updates
libvirt-client.x86_64 0.9.4-23.el6_2.4 @updates
libvirt-devel.x86_64 0.9.4-23.el6_2.4 @updates
libvirt-java.noarch 0.4.7-1.el6 @anaconda-CentOS-201112091719.x86_64/6.2
libvirt-java-devel.noarch 0.4.7-1.el6 @anaconda-CentOS-201112091719.x86_64/6.2
libvirt-python.x86_64 0.9.4-23.el6_2.4 @updates
python-virtinst.noarch 0.600.0-5.el6 @anaconda-CentOS-201112091719.x86_64/6.2
virt-what.x86_64 1.11-1.1.el6 @base
Available Packages
...
libvirt.x86_64 0.9.4-23.el6_2.4 @updates
libvirt-client.x86_64 0.9.4-23.el6_2.4 @updates
libvirt-devel.x86_64 0.9.4-23.el6_2.4 @updates
libvirt-java.noarch 0.4.7-1.el6 @anaconda-CentOS-201112091719.x86_64/6.2
libvirt-java-devel.noarch 0.4.7-1.el6 @anaconda-CentOS-201112091719.x86_64/6.2
libvirt-python.x86_64 0.9.4-23.el6_2.4 @updates
python-virtinst.noarch 0.600.0-5.el6 @anaconda-CentOS-201112091719.x86_64/6.2
virt-what.x86_64 1.11-1.1.el6 @base
Available Packages
...
Re: New installation v6.2 won't shutdown
Posted by TrevorH on 2012/2/19 21:16:29
Quote:
What does `yum list \*virt\*` say?
I did a - yum remove *virt* - which did nothing to affect my issue.
What does `yum list \*virt\*` say?
New installation v6.2 won't shutdown
Posted by artw on 2012/2/19 16:18:39
I know next to nothing about Linux (but am trying to learn). Now that we have that out of the way ...
I have an i5 - quad core 3.3Ghz, 16GB, 1TB SATA drives running (as plain as possible) Windows 7 Ultimate x64host - current on patches. On top of that I am running VMware Workstation v8 - VMware-workstation-full-8.0.2-591240 (latest update).
I have downloaded and installed http://ftp.telus.net/pub/centos/6.2/isos/x86_64/CentOS-6.2-x86_64-bin-DVD1.iso as a guest VM. I also installed the VMware tools into this CentOS installation.
The issue I'm facing is when I attempt to shutdown or restart CentOS, I am presented a black (non-graphical) screen with :
Shutting Down...Running guests on default URI:
(if it's a restart, replace "Shutting Down" with "Restarting")
and it just sits there. Every other VM (including Windows 7, Red Hat v6.2 and Fedora 16) shuts down "properly" and "powers off" the VM.
I did some searching on that text and came up with a few indications that it was something to do with Linux's Virtual environment .... possibly a bug in earlier versions.
I did a - yum remove *virt* - which did nothing to affect my issue.
Any (easy to follow
) suggestions?
Cheers,
Art
I have an i5 - quad core 3.3Ghz, 16GB, 1TB SATA drives running (as plain as possible) Windows 7 Ultimate x64host - current on patches. On top of that I am running VMware Workstation v8 - VMware-workstation-full-8.0.2-591240 (latest update).
I have downloaded and installed http://ftp.telus.net/pub/centos/6.2/isos/x86_64/CentOS-6.2-x86_64-bin-DVD1.iso as a guest VM. I also installed the VMware tools into this CentOS installation.
The issue I'm facing is when I attempt to shutdown or restart CentOS, I am presented a black (non-graphical) screen with :
Shutting Down...Running guests on default URI:
(if it's a restart, replace "Shutting Down" with "Restarting")
and it just sits there. Every other VM (including Windows 7, Red Hat v6.2 and Fedora 16) shuts down "properly" and "powers off" the VM.
I did some searching on that text and came up with a few indications that it was something to do with Linux's Virtual environment .... possibly a bug in earlier versions.
I did a - yum remove *virt* - which did nothing to affect my issue.
Any (easy to follow
) suggestions? Cheers,
Art
This Post was from: https://www.centos.org/newbb/viewtopic.php?forum=55&topic_id=35897