--- On Wed, 11/10/10, jayeola@gmail.com jayeola@gmail.com wrote:
From: jayeola@gmail.com jayeola@gmail.com Subject: Re: [CentOS-virt] KVM: where are the directions? To: "Discussion about the virtualization on CentOS" centos-virt@centos.org Date: Wednesday, November 10, 2010, 7:15 PM rpm -ql kvm rpm -qa | grep kvm
to continue this: ------------- verify an amd64 install of kvm -------------- $ rpm -qa | grep kvm etherboot-zroms-kvm-5.4.4-13.el5.centos kvm-83-164.el5_5.21 kmod-kvm-83-164.el5_5.21
$ sudo lsmod | grep kvm kvm_amd 69416 0 kvm 226336 2 ksm,kvm_amd
yum install bridge-utils tunctl ------------- snip ---------
kvm is basically qemu. The kvm launcher is (by default) not in your path: /usr/libexec/qemu-kvm
request help on qemu-kvm and you will see almost the same thing which is in qemu.
Trying to learn kvm via libvirt is over-kill - stick with the commandline.
To launch a live CD do #/usr/libexec/qemu-kvm -cdrom /path-to/pup-431.iso -boot d -m 384 -net nic,model=rtl8139 -net tap -localtime -usb &
this works over ssh too if you forward X.
On 11/10/2010 08:31 PM, Mark Pryor wrote:
--- On Wed, 11/10/10, jayeola@gmail.comjayeola@gmail.com wrote:
From: jayeola@gmail.comjayeola@gmail.com Subject: Re: [CentOS-virt] KVM: where are the directions? To: "Discussion about the virtualization on CentOS"centos-virt@centos.org Date: Wednesday, November 10, 2010, 7:15 PM rpm -ql kvm rpm -qa | grep kvm
to continue this: ------------- verify an amd64 install of kvm -------------- $ rpm -qa | grep kvm etherboot-zroms-kvm-5.4.4-13.el5.centos kvm-83-164.el5_5.21 kmod-kvm-83-164.el5_5.21
$ sudo lsmod | grep kvm kvm_amd 69416 0 kvm 226336 2 ksm,kvm_amd
yum install bridge-utils tunctl ------------- snip ---------
kvm is basically qemu. The kvm launcher is (by default) not in your path: /usr/libexec/qemu-kvm
request help on qemu-kvm and you will see almost the same thing which is in qemu.
Trying to learn kvm via libvirt is over-kill - stick with the commandline.
To launch a live CD do #/usr/libexec/qemu-kvm -cdrom /path-to/pup-431.iso -boot d -m 384 -net nic,model=rtl8139 -net tap -localtime -usb&
this works over ssh too if you forward X.
Thank you!
Fedora 13 Live CD: qemu-kvm -cdrom ./Fedora-13-i686-Live-XFCE.iso -boot d -m 384 -net nic,model=rtl8139 -localtime -usb
Froze up at "automatic boot in 10 seconds". This is probably because my CentOS 5.5 is 32 bit and I am running a really old version of qemu-kvm.
BartPE (Windows XP Personal Edition on a CDROM): qemu-kvm -cdrom ./KAS7.Bart.iso -boot d -m 384 -net nic,model=rtl8139 -localtime -usb -smp 2
Ran very well. Even found my rtl8139.
I have to work on the TAP device thing.
-T
2010/11/11 MargoAndTodd margoandtodd@gmail.com:
On 11/10/2010 08:31 PM, Mark Pryor wrote:
--- On Wed, 11/10/10, jayeola@gmail.comjayeola@gmail.com wrote:
From: jayeola@gmail.comjayeola@gmail.com Subject: Re: [CentOS-virt] KVM: where are the directions? To: "Discussion about the virtualization on CentOS"centos-virt@centos.org Date: Wednesday, November 10, 2010, 7:15 PM rpm -ql kvm rpm -qa | grep kvm
to continue this: ------------- verify an amd64 install of kvm -------------- $ rpm -qa | grep kvm etherboot-zroms-kvm-5.4.4-13.el5.centos kvm-83-164.el5_5.21 kmod-kvm-83-164.el5_5.21
$ sudo lsmod | grep kvm kvm_amd 69416 0 kvm 226336 2 ksm,kvm_amd
yum install bridge-utils tunctl ------------- snip ---------
kvm is basically qemu. The kvm launcher is (by default) not in your path: /usr/libexec/qemu-kvm
request help on qemu-kvm and you will see almost the same thing which is in qemu.
Trying to learn kvm via libvirt is over-kill - stick with the commandline.
You'll never need to run it from the command line, use the available management tools (libvirt+virsh from the command line, libvirt+virt-manager from X11), it makes your life much much easier. I've been running qemu-kvm from the command line for several years, and while it's fine to know how the system works, then you definitely don't want to manage your enterprise virtual machines that way. For example, if you start qemu-kvm twice in parallel, with the same HDD image, you'll damage or destroy your HDD image. Libvirt takes care of such banalities and many others.
Fedora 13 Live CD: qemu-kvm -cdrom ./Fedora-13-i686-Live-XFCE.iso -boot d -m 384 -net nic,model=rtl8139 -localtime -usb
Froze up at "automatic boot in 10 seconds". This is probably because my CentOS 5.5 is 32 bit and I am running a really old version of qemu-kvm.
No, you're not running an old version of qemu-kvm in CentOS. Like most other packages, Red Hat has selected an (old and stable) version as the baseline version and then backported bugfixes and new features from newer versions of the package, to fulfill the needs of their enterprise customers. kvm-83 in CentOS is NOT equal to upstream kvm-83. That said, as you've probably already read in the docs, KVM is a "technology preview" in RHEL 5.x...6.0 will be the first version with official/stable KVM support by Red Hat.
Best regards Kenni
On 11/11/2010 01:50 PM, Kenni Lund wrote:
You'll never need to run it from the command line, use the available management tools (libvirt+virsh from the command line, libvirt+virt-manager from X11), it makes your life much much easier. I've been running qemu-kvm from the command line for several years, and while it's fine to know how the system works, then you definitely don't want to manage your enterprise virtual machines that way. For example, if you start qemu-kvm twice in parallel, with the same HDD image, you'll damage or destroy your HDD image. Libvirt takes care of such banalities and many others.
Thank you!
These are small business servers. The CentOS server is the only server on the network. I start my VM's in rc.local and shut them down in rd.shutdown (I wrote my own). So, I am stuck with the command line. Thank you for the heads up on running them twice!
But, on my new office machine, I will be running them headed, so I will be using your instructions there.
-T
2010/11/13 MargoAndTodd margoandtodd@gmail.com:
On 11/11/2010 01:50 PM, Kenni Lund wrote:
You'll never need to run it from the command line, use the available management tools (libvirt+virsh from the command line, libvirt+virt-manager from X11), it makes your life much much easier. I've been running qemu-kvm from the command line for several years, and while it's fine to know how the system works, then you definitely don't want to manage your enterprise virtual machines that way. For example, if you start qemu-kvm twice in parallel, with the same HDD image, you'll damage or destroy your HDD image. Libvirt takes care of such banalities and many others.
Thank you!
These are small business servers. The CentOS server is the only server on the network. I start my VM's in rc.local and shut them down in rd.shutdown (I wrote my own). So, I am stuck with the command line. Thank you for the heads up on running them twice!
But, on my new office machine, I will be running them headed, so I will be using your instructions there.
Running from the command line doesn't mean you can't use the management tools:
Quick'n'dirty overview:
Install new guests: virt-install
Start guest: virsh start $guestname
List running guests: virsh list virsh list --all
Shutdown guest (sends an ACPI signal to the guest, telling it to shutdown correctly - same a clicking on the power button for 1 sec on most computers): virsh shutdown $guestname
Shutdown guest immediately (like pulling the power cable from a computer): virsh destroy $guestname
Edit a guest: virsh edit $guestname
etc. etc...run virsh --help and virt-install --help for more options.
Best regards Kenni
On 11/13/2010 02:05 AM, Kenni Lund wrote:
2010/11/13 MargoAndToddmargoandtodd@gmail.com:
On 11/11/2010 01:50 PM, Kenni Lund wrote:
You'll never need to run it from the command line, use the available management tools (libvirt+virsh from the command line, libvirt+virt-manager from X11), it makes your life much much easier. I've been running qemu-kvm from the command line for several years, and while it's fine to know how the system works, then you definitely don't want to manage your enterprise virtual machines that way. For example, if you start qemu-kvm twice in parallel, with the same HDD image, you'll damage or destroy your HDD image. Libvirt takes care of such banalities and many others.
Thank you!
These are small business servers. The CentOS server is the only server on the network. I start my VM's in rc.local and shut them down in rd.shutdown (I wrote my own). So, I am stuck with the command line. Thank you for the heads up on running them twice!
But, on my new office machine, I will be running them headed, so I will be using your instructions there.
Running from the command line doesn't mean you can't use the management tools:
Quick'n'dirty overview:
Install new guests: virt-install
Start guest: virsh start $guestname
List running guests: virsh list virsh list --all
Shutdown guest (sends an ACPI signal to the guest, telling it to shutdown correctly - same a clicking on the power button for 1 sec on most computers): virsh shutdown $guestname
Shutdown guest immediately (like pulling the power cable from a computer): virsh destroy $guestname
Edit a guest: virsh edit $guestname
etc. etc...run virsh --help and virt-install --help for more options.
Best regards Kenni _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Thank you!
On 11/11/2010 01:50 PM, Kenni Lund wrote:
No, you're not running an old version of qemu-kvm in CentOS. Like most other packages, Red Hat has selected an (old and stable) version as the baseline version and then backported bugfixes and new features from newer versions of the package, to fulfill the needs of their enterprise customers. kvm-83 in CentOS is NOT equal to upstream kvm-83. That said, as you've probably already read in the docs, KVM is a "technology preview" in RHEL 5.x...6.0 will be the first version with official/stable KVM support by Red Hat.
Best regards Kenni
Hi Kenni,
This is my setup:
$ cat /etc/redhat-release CentOS release 5.5 (Final)
$ uname -r -m 2.6.18-194.26.1.el5 i686
$ rpm -qa *kvm* kvm-36-1 kmod-kvm-36-3
Not even close to 83. :-(
-T
2010/11/13 MargoAndTodd margoandtodd@gmail.com:
On 11/11/2010 01:50 PM, Kenni Lund wrote:
No, you're not running an old version of qemu-kvm in CentOS. Like most other packages, Red Hat has selected an (old and stable) version as the baseline version and then backported bugfixes and new features from newer versions of the package, to fulfill the needs of their enterprise customers. kvm-83 in CentOS is NOT equal to upstream kvm-83. That said, as you've probably already read in the docs, KVM is a "technology preview" in RHEL 5.x...6.0 will be the first version with official/stable KVM support by Red Hat.
Best regards Kenni
Hi Kenni,
This is my setup:
$ cat /etc/redhat-release CentOS release 5.5 (Final)
$ uname -r -m 2.6.18-194.26.1.el5 i686
$ rpm -qa *kvm* kvm-36-1 kmod-kvm-36-3
Not even close to 83. :-(
These KVM-packages are from some 3rd party repository, aren't they? I don't think that 5.5 has KVM support on i686 at all...use CentOS 5.5 x86_64 instead.
Best regards Kenni
On 11/13/2010 07:44 AM, compdoc wrote:
$ uname -r -m 2.6.18-194.26.1.el5 i686
$ rpm -qa *kvm* kvm-36-1 kmod-kvm-36-3
Not even close to 83. :-(
My centos 5.5 has kvm 83. I'm not sure how you got that old stuff
I am 32 bit.
yum install kvm kmod-kvm
2010/11/14 MargoAndTodd margoandtodd@gmail.com:
On 11/13/2010 07:44 AM, compdoc wrote:
$ uname -r -m 2.6.18-194.26.1.el5 i686
$ rpm -qa *kvm* kvm-36-1 kmod-kvm-36-3
Not even close to 83. :-(
My centos 5.5 has kvm 83. I'm not sure how you got that old stuff
I am 32 bit.
yum install kvm kmod-kvm
You might have it installed it with yum, but in that case you've added 3rd party RPM-repositories (rpmforge, EPEL, etc).
These are the packages which were available in *32 bit* CentOS 5.5 at release time (search for kvm and you'll find nothing): http://mirror.stanford.edu/yum/pub/centos/5.5/os/i386/CentOS/
And these are the packages available currently to *32bit* CentOS 5.5 through updates: http://mirror.stanford.edu/yum/pub/centos/5.5/updates/i386/RPMS/ (still nothing)
Now, these are the packages which were available in *64bit* CentOS 5.5 at release time: http://mirror.stanford.edu/yum/pub/centos/5.5/os/x86_64/CentOS/ Notice that this list contains kvm-83-164.el5.x86_64.rpm and other related KVM packages...
...and the current 64-bit updates: http://mirror.stanford.edu/yum/pub/centos/5.5/updates/x86_64/RPMS/ which contains several kvm-packages, with the latest being kvm-83-164.el5_5.23.x86_64.rpm.
So, as I said, the 32 bit CentOS doesn't contain KVM, not v36, not v83 - you'll need a 64-bit system. Also, if you want a stable system, DON'T use 3rd party repositories unless you take extremely care and know what you're doing. If you enable some random bleeding edge 3rd party repository, and lets yum install packages and updates from it, you could just as well setup your server with some bleeding edge Linux distribution instead of RHEL/CentOS; Fedora, Ubuntu Desktop, Gentoo, Arch Linux, [insert your favorite bleeding edge distro here]. Unless you've setup yum priorities (which is not a good thing either, but better than nothing), yum will always download the unstable packages from the 3rd party repositories, and replace stable CentOS packages with them (since they're newer).
Best regards Kenni
On 11/14/2010 03:11 PM, Kenni Lund wrote:
...and the current 64-bit updates: http://mirror.stanford.edu/yum/pub/centos/5.5/updates/x86_64/RPMS/ which contains several kvm-packages, with the latest being kvm-83-164.el5_5.23.x86_64.rpm.
Guess I will just have to upgrade my office computer to 64 bit. Oh well ... :') (Got my eye on a Supermicro X8SAX and an i7-930.) :-)
-T
Unless you have old cards you have to retain, PCI-x isn't useful anymore. Too slow.
On 11/14/2010 05:25 PM, compdoc wrote:
Unless you have old cards you have to retain, PCI-x isn't useful anymore. Too slow.
Supermicro X8SAX: 2 (x16) PCI-Express 2.0, 1 (x4) PCI-Express (using X8 slot), 2x 64-bit 133/100MHz PCI-X, 1x 32-bit PCI Slots
I put the video and the RAID card in the PCI-e slots. I use the PCI and PCI-x for things like parallel port cards, which cost double for PCI-e.
-T
On 11/14/2010 05:25 PM, compdoc wrote:
Unless you have old cards you have to retain, PCI-x isn't useful anymore. Too slow.
Depends on what you consider 'too slow'. I just benchmarked an 8 drive software RAID6 (8 x 1.5 TByte Seagate drives) on a PCI-X card (Areca ARC-1120 configured for JBOD operation) at 196 megabytes/second sustained sequential write and 420 megabytes/second sustained sequential read with bonnie++ on a Supermicro PDSMi board.
Just how fast do you need?
It's still useful, but why invest in an older technology when the newer technology is there and doesn't cost more?
100baseT switches are still being sold, but it's a bad idea to buy one...
On 11/15/2010 09:00 AM, compdoc wrote:
It's still useful, but why invest in an older technology when the newer technology is there and doesn't cost more?
Because it *does* cost more and doesn't (in my case) provide anything special I need feature wise. I already had a nice hot swappable 2U case with dual p/s, a not incredibly old server motherboard, dual core CPU, memory et al available. For an incremental cost of about $460 dollars I bought an Areca 1120 PCI-X controller to match my existing hardware rather than buying more like two thousand dollars in new hardware to do exactly the same thing, at pretty much the same performance level.
On 11/13/2010 02:06 AM, Kenni Lund wrote:
2010/11/13 MargoAndToddmargoandtodd@gmail.com:
On 11/11/2010 01:50 PM, Kenni Lund wrote:
No, you're not running an old version of qemu-kvm in CentOS. Like most other packages, Red Hat has selected an (old and stable) version as the baseline version and then backported bugfixes and new features from newer versions of the package, to fulfill the needs of their enterprise customers. kvm-83 in CentOS is NOT equal to upstream kvm-83. That said, as you've probably already read in the docs, KVM is a "technology preview" in RHEL 5.x...6.0 will be the first version with official/stable KVM support by Red Hat.
Best regards Kenni
Hi Kenni,
This is my setup:
$ cat /etc/redhat-release CentOS release 5.5 (Final)
$ uname -r -m 2.6.18-194.26.1.el5 i686
$ rpm -qa *kvm* kvm-36-1 kmod-kvm-36-3
Not even close to 83. :-(
These KVM-packages are from some 3rd party repository, aren't they? I don't think that 5.5 has KVM support on i686 at all...use CentOS 5.5 x86_64 instead.
Best regards Kenni
To do that I will be need a who new computer. Hmmmm. (Got me eyes on a Supermicro X8SAX and an i7-930.)
-T
kvm-83. That said, as you've probably already read in the docs, KVM is a "technology preview" in RHEL 5.x...6.0 will be the first version with official/stable KVM support by Red Hat.
My understanding is that KVM was tech preview in RHEL/CentOS 5.4 and officially supported from RHEL/CentOS 5.5.
Am I mistaken?
2010/11/13 Mathieu Baudier mbaudier@argeo.org:
kvm-83. That said, as you've probably already read in the docs, KVM is a "technology preview" in RHEL 5.x...6.0 will be the first version with official/stable KVM support by Red Hat.
My understanding is that KVM was tech preview in RHEL/CentOS 5.4 and officially supported from RHEL/CentOS 5.5.
Sorry, you're right...nevertheless, you still need RHEL/CentOS 6.0 to get stuff like stable ABI for Windows guests.
Best regards Kenni
-
Benjamin Franz -
compdoc -
jayeola＠gmail.com -
Kenni Lund -
MargoAndTodd -
Mark Pryor -
Mathieu Baudier