I have my newly installed fedora 11 x86_64 system on an Intel Core 2 Duo with virtualization hardware support, so I thought I'd give KVM a whirl.
I started virt-manager as root, defined a new machine which I made be an i686 and pointed at the Fedora 11 i386 DVD iso image. I also told it to allocate space immediately for a 12GB image file.
It has now been running anaconda's cylon eyeball format progress bar for about an hour.
How long should it take to format the silly disk image?
Other points:
I can't believe virt-manager insists on placing image files under /var. They take lots of space. I'd expect to be able to pick a place to put the disk image.
This fedora-virt mailing list doesn't have a pointer in the list of mailing lists on the fedora mailing list web page at: http://fedoraproject.org/wiki/Communicate
On Fri, Jun 12, 2009 at 01:20:20PM -0400, Tom Horsley wrote:
I have my newly installed fedora 11 x86_64 system on an Intel Core 2 Duo with virtualization hardware support, so I thought I'd give KVM a whirl.
I started virt-manager as root, defined a new machine which I made be an i686 and pointed at the Fedora 11 i386 DVD iso image. I also told it to allocate space immediately for a 12GB image file.
Why are you using ix86 on x86_64? KVM can't make 32bit systems on 64bit and vice versa yet.
But you can install 32bit OS on 64bit guest. Only leave default architecture settings. If you change defaults, KVM virtualization is automatically replaced by qemu, which can emulate different architectures, but has no hardware acceleration support.
It has now been running anaconda's cylon eyeball format progress bar for about an hour.
How long should it take to format the silly disk image?
No comment. :-)
SAL
On Fri, 12 Jun 2009 19:59:00 +0200 Ján ONDREJ (SAL) wrote:
How long should it take to format the silly disk image?
No comment. :-)
I think I found my real problem. I've just been on a trip through the BIOS settings where I found the BIOS had disabled the hardware acceleration stuff. I'll try again, I bet it works better this time...
On Fri, Jun 12, 2009 at 02:46:35PM -0400, Tom Horsley wrote:
On Fri, 12 Jun 2009 19:59:00 +0200 Ján ONDREJ (SAL) wrote:
How long should it take to format the silly disk image?
No comment. :-)
I think I found my real problem. I've just been on a trip through the BIOS settings where I found the BIOS had disabled the hardware acceleration stuff. I'll try again, I bet it works better this time...
I vaguely recall that virt-manager was going to give a warning about this case. There is probably one in the system logfiles (from when kvm-intel.ko was loaded).
Rich.
On Sat, 13 Jun 2009 10:51:36 +0100 Richard W.M. Jones wrote:
I think I found my real problem. I've just been on a trip through the BIOS settings where I found the BIOS had disabled the hardware acceleration stuff. I'll try again, I bet it works better this time...
I vaguely recall that virt-manager was going to give a warning about this case. There is probably one in the system logfiles (from when kvm-intel.ko was loaded).
Actually, it turns out the BIOS setting was for something else. Apparently this machine does not have virtualization support (even though I was under the impression it was specifically purchased with that as one of the required features, which was why I didn't look into it earlier - Mordac is messing with me again :-).
It certainly isn't at all obvious from virt-manager that no hardware support is available (not if you don't already know what hardware support looks like in virt-manager, anyway).
On Fri, 2009-06-12 at 13:20 -0400, Tom Horsley wrote:
I can't believe virt-manager insists on placing image files under /var. They take lots of space. I'd expect to be able to pick a place to put the disk image.
If you'd prefer not to use /var you can create a new storage pool to hold guest image volumes.
Right click on your host (localhost qemu) in the virt manager interface. Select "Details". In the dialog which pops up select the "Storage" tab. In the lower left corner there is a "+" sign for adding a storage pool. Select a device or a directory like /home/you/Guests perhaps.
This process could probably be more obvious. The plus sign could be a "Add Storage Pool" button instead for example.
See also: * `virsh help | grep pool` * http://www.libvirt.org/formatstorage.html
Also, if you are using selinux, be aware it expects images to live in /var/lib/libvirt/images by default. http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
This fedora-virt mailing list doesn't have a pointer in the list of mailing lists on the fedora mailing list web page at: http://fedoraproject.org/wiki/Communicate
It does now. Thanks.