Bug 485568
Summary: | Starting a KVM virtual machine does not always succeed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jasper Capel <capel> |
Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | berrange, clalance, crobinso, ehabkost, gcosta, markmc, quintela, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-17 00:54:01 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
Jasper Capel
2009-02-14 16:21:05 UTC
do you have anything in logs? dmesg and libvirt logs at /var/log/libvirt are appreciated (specially the later) For a failed attempt, dmesg shows: device vnet0 entered promiscuous mode virbr0: topology change detected, propagating virbr0: port 1(vnet0) entering forwarding state virbr0: port 1(vnet0) entering disabled state device vnet0 left promiscuous mode virbr0: port 1(vnet0) entering disabled state /var/log/libvirt/qemu/lenny.log (where lenny is the name of my VM) shows: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 512 -smp 1 -name lenny -uuid d6649746-f5bf-bc08-1b35-9515ed70ed04 -monitor pty -pidfile /var/run/libvirt/qemu//lenny.pid -boot c -drive file=,if=ide,media=cdrom,index=2 -drive file=/data/VMWARE/lenny-disk0,if=virtio,index=0,boot=on -net nic,macaddr=54:52:00:45:e6:e3,vlan=0,model=virtio -net tap,fd=17,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us I don't think these are particularly useful, could I somehow raise the log level a bit? I got some more info, although probably still not very helpful (after starting libvirtd, the VM started at the 5th attempt): [root@farnsworth ~]# libvirtd --verbose 20:02:54.452: info : Received unexpected signal 17 20:02:54.452: info : Received unexpected signal 17 20:02:54.453: info : Received unexpected signal 17 20:03:06.309: info : Checking PID 23388 running as 500 20:03:06.347: info : Policy allowed action org.libvirt.unix.manage from pid 23388, uid 500, result yes 20:03:06.348: info : Received unexpected signal 17 20:03:12.835: info : Received unexpected signal 17 20:03:12.837: info : Enabling IFF_VNET_HDR 20:03:12.918: info : Received unexpected signal 17 20:03:13.018: error : internal error unable to start guest: libvir: QEMU error : internal error unable to start guest: Shutting down VM 'lenny' 20:03:26.579: info : Enabling IFF_VNET_HDR 20:03:26.585: info : Received unexpected signal 17 20:03:26.637: info : Received unexpected signal 17 20:03:26.638: error : internal error unable to start guest: libvir: QEMU error : internal error unable to start guest: Shutting down VM 'lenny' 20:03:30.649: info : Received unexpected signal 17 20:03:30.650: info : Enabling IFF_VNET_HDR 20:03:30.692: error : internal error unable to start guest: libvir: QEMU error : internal error unable to start guest: Shutting down VM 'lenny' 20:03:30.693: info : Received unexpected signal 17 20:03:33.220: info : Received unexpected signal 17 20:03:33.222: info : Enabling IFF_VNET_HDR 20:03:33.276: info : Received unexpected signal 17 20:03:33.277: error : internal error unable to start guest: libvir: QEMU error : internal error unable to start guest: Shutting down VM 'lenny' 20:03:36.603: info : Received unexpected signal 17 20:03:36.606: info : Enabling IFF_VNET_HDR 20:03:36.630: info : Received unexpected signal 17 ^ And here it's running. Thanks for the report, it looks like a dup of an already reported bug with 0.6.0 *** This bug has been marked as a duplicate of bug 484649 *** |