I have an older quad-core AMD processor that supports hardware virtualization on a motherboard that does not support it in the bios.
Eventually I'll swap the mobo out on this box for one that will support hardware virtualization and use qemu-kvm. I prefer kvm because of SELinux and sVirt that protects the host from VM breakout should a VM become hostile.
In the meantime, I want to start work on a web project and want to use this idle machine and CentOS 6.0 in a VM. What I prototype and learn will eventually be moved to the production machine using kvm and sVirt.
So...I downloaded and installed Virtualbox 4.x but haven't yet had the time to check it out.
Any tips/tricks concerning it?
Dave
Any tips/tricks concerning it?
While I am used to using esx, I am forced to use vb on my wkst at my new gig and can tell you there are age old bugs that have never been resolved with respect to snap shot children not being cleaned up properly and the xml config while having a nice programatic interface is a pain to edit manually.
Bottom line, I don't like it at all and find it only moderately stable.
Not a fan...
jlc
If you want to install Virtualbox in CentOS, it is easy. Go to this download link http://download.virtualbox.org/virtualbox/4.1.4/VirtualBox-4.1-4.1.4_74291_r.... and download the RPM File, after simply install it.
I am not such a fan of Virtualbox neither but You can try installing VMware Player or buy VMware workstation, Both of them work perfectly on CentOS.
--------------------------------------------------------------------------------------------------------------------------------------------------------------- While I am used to using esx, I am forced to use vb on my wkst at my new gig and can tell you there are age old bugs that have never been resolved with respect to snap shot children not being cleaned up properly and the xml config while having a nice programatic interface is a pain to edit manually.
Bottom line, I don't like it at all and find it only moderately stable.
Not a fan...
jlc
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
A few things:
- It didn't/doesn't play well with other virtual machine libraries. - Don't forget to install the vbox extensions if you want/need to use USB 2.0 - Don't forget to install DKMS before pretty much anything else.
- It _is_ worth the hassle of adding the vbox guest additions to support seamless mouse and keyboard integration - ... not to mention resizing the machine window - Here's a relatively complete description on turning VirtualBox into a service under Redhat/Centos/Fedora (http://www.kernelhardware.org/virtualbox-auto-start-vm-centos-fedora-redhat/). Though I'd replace vboxmanage with vboxheadless. [Can't be bothered to remember if either of the two apps are camelcase or not - check.] - Dismount the guestadditions ISO / O/S installation ISO / any other non-essential ISO _*before*_ you take a snapshot. 8-) - If you want the guest system to be a server you need bridged networking (it works pretty well 'out of the box' actually). - RTFM (really)
It was the first VM I used (mainly because it works on hardware the doesn't support hardware virtualisation) and the only real problems I have had have been 64bit guests on 64bit hosts (both windows and unices).
YMMV
Toodles, Roy
________________________________ From: David McGuffey davidmcguffey@verizon.net To: CentOS mailing list centos@centos.org Sent: Wednesday, 2 November 2011, 1:27 Subject: [CentOS] VirtualBox on CentOS 6.0?
I have an older quad-core AMD processor that supports hardware virtualization on a motherboard that does not support it in the bios.
Eventually I'll swap the mobo out on this box for one that will support hardware virtualization and use qemu-kvm. I prefer kvm because of SELinux and sVirt that protects the host from VM breakout should a VM become hostile.
In the meantime, I want to start work on a web project and want to use this idle machine and CentOS 6.0 in a VM. What I prototype and learn will eventually be moved to the production machine using kvm and sVirt.
So...I downloaded and installed Virtualbox 4.x but haven't yet had the time to check it out.
Any tips/tricks concerning it?
Dave
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I had problems with VBox 4 in my CentOS6, so I had to install VirtualBox-3.2-3.2.12_68302_rhel6-1.x86_64 and I am very very happy with it. VMware Server meant a lot of problems with new kernels and the patch any-any... so I think Virtualbox does the trick.
El 02/11/11 09:04, Roy Trubshaw escribió:
A few things:
It didn't/doesn't play well with other virtual machine libraries.
Don't forget to install the vbox extensions if you want/need to use USB 2.0
Don't forget to install DKMS before pretty much anything else.
It _is_ worth the hassle of adding the vbox guest additions to support seamless mouse and keyboard integration
... not to mention resizing the machine window
Here's a relatively complete description on turning VirtualBox into a service under Redhat/Centos/Fedora (http://www.kernelhardware.org/virtualbox-auto-start-vm-centos-fedora-redhat/). Though I'd replace vboxmanage with vboxheadless. [Can't be bothered to remember if either of the two apps are camelcase or not - check.]
Dismount the guestadditions ISO / O/S installation ISO / any other non-essential ISO _*before*_ you take a snapshot. 8-)
If you want the guest system to be a server you need bridged networking (it works pretty well 'out of the box' actually).
RTFM (really)
It was the first VM I used (mainly because it works on hardware the doesn't support hardware virtualisation) and the only real problems I have had have been 64bit guests on 64bit hosts (both windows and unices).
YMMV
Toodles, Roy
From: David McGuffeydavidmcguffey@verizon.net To: CentOS mailing listcentos@centos.org Sent: Wednesday, 2 November 2011, 1:27 Subject: [CentOS] VirtualBox on CentOS 6.0?
I have an older quad-core AMD processor that supports hardware virtualization on a motherboard that does not support it in the bios.
Eventually I'll swap the mobo out on this box for one that will support hardware virtualization and use qemu-kvm. I prefer kvm because of SELinux and sVirt that protects the host from VM breakout should a VM become hostile.
In the meantime, I want to start work on a web project and want to use this idle machine and CentOS 6.0 in a VM. What I prototype and learn will eventually be moved to the production machine using kvm and sVirt.
So...I downloaded and installed Virtualbox 4.x but haven't yet had the time to check it out.
Any tips/tricks concerning it?
Dave
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Vreme: 11/02/2011 09:10 AM, Lorenzo Martínez Rodríguez piše:
I had problems with VBox 4 in my CentOS6, so I had to install VirtualBox-3.2-3.2.12_68302_rhel6-1.x86_64 and I am very very happy with it. VMware Server meant a lot of problems with new kernels and the patch any-any... so I think Virtualbox does the trick.
I use VBox 4.x (there is even repository for it) without problems. There was some initial problems with USB, but it was solved 3-4 months ago.
Notice that you can not upgrade 4.0.x to 4.1.x. You have to uninstall previous minor version to install newer minor version, but all settings remain the same.
On my windows Guest (banking app and sometimes for support) sometimes, after initial start, I have to restart guest to recognize card reader, but once it is up it is rock solid.
Use VBox share folders for nice "network" file sharing.
P.S. Please do not top post. On this list please write (in most cases) bellow the original text, or in between.
On Wednesday, November 02, 2011 04:55 PM, Ljubomir Ljubojevic wrote:
Vreme: 11/02/2011 09:10 AM, Lorenzo Martínez Rodríguez piše:
I had problems with VBox 4 in my CentOS6, so I had to install VirtualBox-3.2-3.2.12_68302_rhel6-1.x86_64 and I am very very happy with it. VMware Server meant a lot of problems with new kernels and the patch any-any... so I think Virtualbox does the trick.
I use VBox 4.x (there is even repository for it) without problems. There was some initial problems with USB, but it was solved 3-4 months ago.
4.0.x was okay for me (Windows server guests) but 4.1.4 was a complete disaster. The guest literally moved at SNAIL pace. Removed all cores save one and then it moved at TURTLE pace. 4.1.x is do not touch even with a ten foot pole. At least with Windows guests.
On Wed, 2 Nov 2011, Christopher Chan wrote:
4.0.x was okay for me (Windows server guests) but 4.1.4 was a complete disaster. The guest literally moved at SNAIL pace. Removed all cores save one and then it moved at TURTLE pace. 4.1.x is do not touch even with a ten foot pole. At least with Windows guests.
This doesn't appear to be universally true. We've run 4.1.4 with Windows 7 64bit on top of CentOS 6 and not seen any noticeable performance problems. The way you describe it makes me think it's not the sort of thing we could not notice if it was happening. This was Windows 7 Enterprise as opposed to a server OS guest.
jh
This doesn't appear to be universally true. We've run 4.1.4 with Windows 7 64bit on top of CentOS 6 and not seen any noticeable performance problems. The way you describe it makes me think it's not the sort of thing we could not notice if it was happening. This was Windows 7 Enterprise as opposed to a server OS guest.
Same, Its obviously related to host os and hardware. As I sit here over lunch manually fixing another snap shot debacle in 4.1.4... Sigh...
jlc
On Wednesday, November 02, 2011 10:33 PM, John Hodrien wrote:
On Wed, 2 Nov 2011, Christopher Chan wrote:
4.0.x was okay for me (Windows server guests) but 4.1.4 was a complete disaster. The guest literally moved at SNAIL pace. Removed all cores save one and then it moved at TURTLE pace. 4.1.x is do not touch even with a ten foot pole. At least with Windows guests.
This doesn't appear to be universally true. We've run 4.1.4 with Windows 7 64bit on top of CentOS 6 and not seen any noticeable performance problems. The way you describe it makes me think it's not the sort of thing we could not notice if it was happening. This was Windows 7 Enterprise as opposed to a server OS guest.
How many cores assigned? VT-X/AMD-V enabled? Hardware?
On Wednesday, November 02, 2011 10:33 PM, John Hodrien wrote:
On Wed, 2 Nov 2011, Christopher Chan wrote:
4.0.x was okay for me (Windows server guests) but 4.1.4 was a complete disaster. The guest literally moved at SNAIL pace. Removed all cores save one and then it moved at TURTLE pace. 4.1.x is do not touch even with a ten foot pole. At least with Windows guests.
This doesn't appear to be universally true. We've run 4.1.4 with Windows 7 64bit on top of CentOS 6 and not seen any noticeable performance problems. The way you describe it makes me think it's not the sort of thing we could not notice if it was happening. This was Windows 7 Enterprise as opposed to a server OS guest.
Oh, was io-apic enabled too?
On Wed, Nov 2, 2011 at 4:04 AM, Roy Trubshaw roy.trubshaw@yahoo.co.ukwrote:
- Here's a relatively complete description on turning VirtualBox into a
service under Redhat/Centos/Fedora ( http://www.kernelhardware.org/virtualbox-auto-start-vm-centos-fedora-redhat/ ).
Using VB 4.1.x under CentOS 6 to run CentOS 5 & 6 and WindowsXP guest VMs without issue. Be sure to read the comments on the above link, the script needs some minor adjustments.
Being able to copy guest VMs between Linux and Windows Hosts supports a robust development and fall back environment.
While I have noticed a few minor issues with VB, overall it has been stable. The issues I've noticed are occasional screen paint issues using seamless mode and there is no way to delete a snapshot without applying the changes from the snapshot.
Brett
-
Brett Serkez -
Christopher Chan -
David McGuffey -
Jerry Minston -
John Hodrien -
Joseph L. Casale -
Ljubomir Ljubojevic -
Lorenzo Martínez Rodríguez -
Roy Trubshaw