With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
sean
On Mon, Apr 27, 2009 at 12:00 AM, sean darcy seandarcy2@gmail.com wrote:
With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
is the kvm-amd module loaded?
lsmod | grep kvm should show it. if not try to load it by doing modprobe kvm-amd
drago01 wrote:
On Mon, Apr 27, 2009 at 12:00 AM, sean darcy seandarcy2@gmail.com wrote:
With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
is the kvm-amd module loaded?
lsmod | grep kvm should show it. if not try to load it by doing modprobe kvm-amd
Yes it is:
lsmod | grep kvm kvm_amd 30940 3 kvm 153112 1 kvm_amd
The problem was that not enough of the qemu stack was installed. I had qemu-common, qemu-x86, qemu-system-x86 installed by yum. I'd assumed they pull in whatever was necessary. Silly me. Installed all qemu, now I get the new machine box.
But where do I choose paravirtual? I don't see any choice in the new machine dialog.
sean
On Mon, 27 Apr 2009, sean darcy wrote:
drago01 wrote:
On Mon, Apr 27, 2009 at 12:00 AM, sean darcy seandarcy2@gmail.com wrote:
With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
is the kvm-amd module loaded?
lsmod | grep kvm should show it. if not try to load it by doing modprobe kvm-amd
Yes it is:
lsmod | grep kvm kvm_amd 30940 3 kvm 153112 1 kvm_amd
The problem was that not enough of the qemu stack was installed. I had qemu-common, qemu-x86, qemu-system-x86 installed by yum. I'd assumed they pull in whatever was necessary. Silly me. Installed all qemu, now I get the new machine box.
hang on ... so which qemu-related package was missing? i'm thinking qemu-user but it would be nice to clarify that.
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
Robert P. J. Day wrote:
On Mon, 27 Apr 2009, sean darcy wrote:
drago01 wrote:
On Mon, Apr 27, 2009 at 12:00 AM, sean darcy seandarcy2@gmail.com wrote:
With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
is the kvm-amd module loaded?
lsmod | grep kvm should show it. if not try to load it by doing modprobe kvm-amd
Yes it is:
lsmod | grep kvm kvm_amd 30940 3 kvm 153112 1 kvm_amd
The problem was that not enough of the qemu stack was installed. I had qemu-common, qemu-x86, qemu-system-x86 installed by yum. I'd assumed they pull in whatever was necessary. Silly me. Installed all qemu, now I get the new machine box.
hang on ... so which qemu-related package was missing? i'm thinking qemu-user but it would be nice to clarify that.
rday
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Any clues on paravirtualization?
sean
sean darcy wrote:
Robert P. J. Day wrote:
On Mon, 27 Apr 2009, sean darcy wrote:
drago01 wrote:
On Mon, Apr 27, 2009 at 12:00 AM, sean darcy seandarcy2@gmail.com wrote:
With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
is the kvm-amd module loaded?
lsmod | grep kvm should show it. if not try to load it by doing modprobe kvm-amd
Yes it is:
lsmod | grep kvm kvm_amd 30940 3 kvm 153112 1 kvm_amd
The problem was that not enough of the qemu stack was installed. I had qemu-common, qemu-x86, qemu-system-x86 installed by yum. I'd assumed they pull in whatever was necessary. Silly me. Installed all qemu, now I get the new machine box.
hang on ... so which qemu-related package was missing? i'm thinking qemu-user but it would be nice to clarify that.
rday
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Any clues on paravirtualization?
sean
I probably found the reason installing qemu*86 is not enough:
http://www.linux-kvm.org/page/Running_libvirt_with_KVM
sean
On Mon, Apr 27, 2009 at 05:58:24PM -0400, sean darcy wrote:
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Any clues on paravirtualization?
QEMU and KVM are both fullvirt technologies. Xen is paravirt.
I probably found the reason installing qemu*86 is not enough:
That page is just plain wrong for Fedora users. The binaries as installed by the qemu (or qemu-system-x86) RPMs are setup correctly. There is no need setup symlinks in that way. If you installed the qemu/qemu-system* RPMs after the initial install, you should reboot to make sure all the kernel modules are loaded, and features detected. If you don't want to reboot, then manually check the kernel modules are loaded, and also restart the libvirtd daemon (service libvirtd restart)
Daniel
Daniel P. Berrange wrote:
On Mon, Apr 27, 2009 at 05:58:24PM -0400, sean darcy wrote:
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Any clues on paravirtualization?
QEMU and KVM are both fullvirt technologies. Xen is paravirt.
I probably found the reason installing qemu*86 is not enough:
That page is just plain wrong for Fedora users. The binaries as installed by the qemu (or qemu-system-x86) RPMs are setup correctly. There is no need setup symlinks in that way. If you installed the qemu/qemu-system* RPMs after the initial install, you should reboot to make sure all the kernel modules are loaded, and features detected. If you don't want to reboot, then manually check the kernel modules are loaded, and also restart the libvirtd daemon (service libvirtd restart)
Daniel
Okay. I know I restarted libvirtd, but I didn't check if the kernel modules were loaded.
In any event, your point about the page being wrong for fedora users is well taken. As I've been messing around with this the past couple of days, I've had trouble finding resources for fedora kvm users. And the resources I have found don't match how F11 has set things up. See, for instance, my comment today to http://www.linux-kvm.com/content/using-bridged-networking-virt-manager.
Are there kvm resources for fedora users? I've seen the ubuntu howto's, but I've been leery, because F11 may be set up differently. Is there a list or forum for fedora kvm users?
sean
sean
sean darcy said the following on 04/27/2009 04:34 PM Pacific Time:
Okay. I know I restarted libvirtd, but I didn't check if the kernel modules were loaded.
In any event, your point about the page being wrong for fedora users is well taken. As I've been messing around with this the past couple of days, I've had trouble finding resources for fedora kvm users. And the resources I have found don't match how F11 has set things up. See, for instance, my comment today to http://www.linux-kvm.com/content/using-bridged-networking-virt-manager.
Are there kvm resources for fedora users? I've seen the ubuntu howto's, but I've been leery, because F11 may be set up differently. Is there a list or forum for fedora kvm users?
sean
http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
John
On Mon, Apr 27, 2009 at 07:34:03PM -0400, sean darcy wrote:
Daniel P. Berrange wrote:
On Mon, Apr 27, 2009 at 05:58:24PM -0400, sean darcy wrote:
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Any clues on paravirtualization?
QEMU and KVM are both fullvirt technologies. Xen is paravirt.
I probably found the reason installing qemu*86 is not enough:
That page is just plain wrong for Fedora users. The binaries as installed by the qemu (or qemu-system-x86) RPMs are setup correctly. There is no need setup symlinks in that way. If you installed the qemu/qemu-system* RPMs after the initial install, you should reboot to make sure all the kernel modules are loaded, and features detected. If you don't want to reboot, then manually check the kernel modules are loaded, and also restart the libvirtd daemon (service libvirtd restart)
Daniel
Okay. I know I restarted libvirtd, but I didn't check if the kernel modules were loaded.
In any event, your point about the page being wrong for fedora users is well taken. As I've been messing around with this the past couple of days, I've had trouble finding resources for fedora kvm users. And the resources I have found don't match how F11 has set things up. See, for instance, my comment today to http://www.linux-kvm.com/content/using-bridged-networking-virt-manager.
For networking we have a page describing our 2 recommended configs here:
http://wiki.libvirt.org/page/Networking
Are there kvm resources for fedora users? I've seen the ubuntu howto's, but I've been leery, because F11 may be set up differently. Is there a list or forum for fedora kvm users?
For discussions we encourage people to join the fedora-virt mailing list
http://www.redhat.com/archives/fedora-virt/
There is a intro on the fedora wiki too
http://fedoraproject.org/wiki/Getting_started_with_virtualization
Daniel
Daniel P. Berrange wrote:
For networking we have a page describing our 2 recommended configs here:
Those both need quite some configuration. What's wrong with the userspace network stack? You can talk from QEMU out with no configuration and just need a -redir switch to forward a QEMU port to an arbitrary host port (which can also be used to connect from the host to the VM by connecting to localhost). That should be working with KVM too, shouldn't it?
Kevin Kofler
On Wed, Apr 29, 2009 at 02:19:39AM +0200, Kevin Kofler wrote:
Daniel P. Berrange wrote:
For networking we have a page describing our 2 recommended configs here:
Those both need quite some configuration. What's wrong with the userspace network stack? You can talk from QEMU out with no configuration and just need a -redir switch to forward a QEMU port to an arbitrary host port (which can also be used to connect from the host to the VM by connecting to localhost). That should be working with KVM too, shouldn't it?
The userspace stack is horrible junk that barely works and until very recently was frequently SEGV'ing on x86_64.
Daniel
Kevin Kofler wrote:
Daniel P. Berrange wrote:
For networking we have a page describing our 2 recommended configs here:
Those both need quite some configuration. What's wrong with the userspace network stack? You can talk from QEMU out with no configuration and just need a -redir switch to forward a QEMU port to an arbitrary host port (which can also be used to connect from the host to the VM by connecting to localhost). That should be working with KVM too, shouldn't it?
You can ssh out and redirect back in, or any of several things, but then the host need to open it's firewall to allow other machines in, and do forwarding (IIRC), it only takes a few lines of script to setup the bridge, then the guest is independent, as much as it can be.
I'm on such a guest now, I have multiple severs running on the host, we all have our own connections.
What you said is totally correct, but there are advantages to tap.
sean darcy wrote, On 04/27/2009 08:55 AM:
Robert P. J. Day wrote:
hang on ... so which qemu-related package was missing? i'm thinking qemu-user but it would be nice to clarify that.
rday
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Assuming all installation was done with yum, you could look at the /var/log/yum.log and get the info.
On Mon, 27 Apr 2009, Todd Denniston wrote:
sean darcy wrote, On 04/27/2009 08:55 AM:
Robert P. J. Day wrote:
hang on ... so which qemu-related package was missing? i'm thinking qemu-user but it would be nice to clarify that.
rday
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Assuming all installation was done with yum, you could look at the /var/log/yum.log and get the info.
the "qemu" package is simply a meta-package that pulls in a host of other packages:
$ rpm -qR qemu qemu-user = 2:0.10-12.fc11 qemu-system-x86 = 2:0.10-12.fc11 qemu-system-sparc = 2:0.10-12.fc11 qemu-system-arm = 2:0.10-12.fc11 qemu-system-cris = 2:0.10-12.fc11 qemu-system-sh4 = 2:0.10-12.fc11 qemu-system-m68k = 2:0.10-12.fc11 qemu-system-mips = 2:0.10-12.fc11 qemu-system-ppc = 2:0.10-12.fc11 qemu-img = 2:0.10-12.fc11 ... etc ... $
rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
sean darcy wrote:
Robert P. J. Day wrote:
On Mon, 27 Apr 2009, sean darcy wrote:
drago01 wrote:
On Mon, Apr 27, 2009 at 12:00 AM, sean darcy seandarcy2@gmail.com wrote:
With all the changes in F11, I'm trying to set up a Windows XP virtual machine with kvm/qemu. But not joy:
virt-install ERROR Host does not support any virtualization options
but /proc/cpuinfo shows svm (this is AMD).
What am I missing?
is the kvm-amd module loaded?
lsmod | grep kvm should show it. if not try to load it by doing modprobe kvm-amd
Yes it is:
lsmod | grep kvm kvm_amd 30940 3 kvm 153112 1 kvm_amd
The problem was that not enough of the qemu stack was installed. I had qemu-common, qemu-x86, qemu-system-x86 installed by yum. I'd assumed they pull in whatever was necessary. Silly me. Installed all qemu, now I get the new machine box.
hang on ... so which qemu-related package was missing? i'm thinking qemu-user but it would be nice to clarify that.
rday
I don't know. I'd first done yum groupinstall virtualization. As I remember, that only brought in qemu-img. When that didn't work I installed qemu*x86. I may have installed qemu-user also. Finally yum install qemu*. Then it worked.
Any clues on paravirtualization?
To test stuff running paravirt mode you can run a CentOS-5.3 machine under KVM and then use xen in that. Useful for proof of concept, not so much for production, although I have a light duty web server running that way, because I got tired of upgrading.