Bug 248305
Summary: | Unable to install qemu-kvm guest machine | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jonathan Underwood <jonathan.underwood> |
Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-07-15 20:31:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonathan Underwood
2007-07-15 18:48:31 UTC
I think this may have something to do with the fact that I unchecked the box to allocate the whole disk storeage now - it succeeds if I leave that checked. Oh, scrap my previous comment. If I leave the box to create the whole disk image now checked, the file is crated, but then once that completes I get the same error message as previously. Yep, I won't expect the pre-allocation to make any functional difference - though I have noticed that sometimes the kernel is so overwhealmed with I/O from pre-allocating the disk, that the VM startup takes longer than normal & times out. I'll try and reproduce this problem. What kernel are you on, btw ? uname -ar: 2.6.21-1.3255.fc7 #1 SMP Thu Jul 5 18:03:06 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux I tried with pretty much same install parameters as your logs show and it succeeded for me. So there must be something in host environment that is different for me vs you which we need to track down & resolve. So a couple more questions - What does 'virsh --conect qemu:///system net-list --all' show when run as root ? - Did you get a /var/log/libvirt/qemu/WindowsXPProSP2.log file created, and if so is there any info in it ? - How much physical RAM have you got & how much is free - output of /proc/meminfo would be useful (In reply to comment #5) > I tried with pretty much same install parameters as your logs show and it > succeeded for me. So there must be something in host environment that is > different for me vs you which we need to track down & resolve. So a couple more > questions > > - What does 'virsh --conect qemu:///system net-list --all' show when run as > root ? ]# virsh --conect qemu:///system net-list --all virsh: unrecognized option `--conect' virsh: error: unsupported option '-?'. See --help. [root@renton jgu]# virsh --connect qemu:///system net-list --all Name State Autostart ----------------------------------------- default active yes > - Did you get a /var/log/libvirt/qemu/WindowsXPProSP2.log file created, and if > so is there any info in it ? It is created, but has zero length I am afraid. > - How much physical RAM have you got & how much is free - output of > /proc/meminfo would be useful # cat /proc/meminfo MemTotal: 2050300 kB MemFree: 962172 kB Buffers: 30028 kB Cached: 444152 kB SwapCached: 0 kB Active: 546304 kB Inactive: 345976 kB SwapTotal: 4096564 kB SwapFree: 4096564 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 418224 kB Mapped: 114508 kB Slab: 40280 kB SReclaimable: 16528 kB SUnreclaim: 23752 kB PageTables: 26844 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 5121712 kB Committed_AS: 913300 kB VmallocTotal: 34359738367 kB VmallocUsed: 4836 kB VmallocChunk: 34359733031 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 Hugepagesize: 2048 kB > > - Did you get a /var/log/libvirt/qemu/WindowsXPProSP2.log file created, and if > > so is there any info in it ? > > It is created, but has zero length I am afraid. Excellant - that gives me a critically useful bit of info. There is only one function called between time of opening the log file & time the first data is written to it, so this must be what is failing. Based on this I think the 'qemu' binary is missing - can you tell me if you have the 'qemu' RPM installed ? And, yes, this is needed even for KVM installs. There's a missing RPM dependancy which I think could be the cause of the trouble. Aha, yes, I checked, and indeed qemu wasn't installed. Naively I had assumed that yum install kvm would pull in any qemu requirement - I had actually thought that kvm shipped with a modified qemu and so wouldn't need the "normal" one. Now I feel really dumb. I have installed qemu, and everything works. Very sorry for the noise and wasting your time. I'll check for a BZ for the missing dependency and make one if there isn't already one. Have opened bug 248312 against kvm for the missing dependency. Will close this as NOTABUG. |