KVM Forum 2010 scheduled for August 9-10 2010

Wednesday, January 27, 2010 - 22:13 Haydn Solomon

Today Chris Wright, Principal Software Engineer at Red Hat, sent out a message on the kvm development mailing list stating that the annual KVM forum is scheduled for August 9-10 2010. The message was not a formal announcement but only a save the date announcement. So far the plan is to co-locate this forum alongside the Linux Foundation's LinuxCon 2010 which will be held in Boston. A call for papers will come later with a more formal announcement. To date there have been two previous kvm forums held in 2007 and 2008. You can find presentations from these past events at the following links.

http://www.linux-kvm.org/page/KvmForum2007

http://www.linux-kvm.org/page/KvmForum2008

The list of talks scheduled at the kvm forum 2010 can be found at the following link

http://www.linux-kvm.org/page/KvmForum2010

Events

Comments

Windows 7 on KVM problems

Thursday, May 6, 2010 - 12:13 Jim (not verified)

FC12/X86_64

I'm trying to install Windows7 on FC12-X86_64 and the install will get to Windows7 Desktop Setup the crashes and doesn't give any messages as to why,
It just says "Stop" no error as to hardware problem.

I have installed this Windows7 on this computer without any troubles, but can't get Virtual setup in Fedora 12.

/etc/var/messages below

# tail -f /var/log/messages
May 6 07:27:22 localhost ntpd_initres[1667]: host name not found: 2.fedora.pool.ntp.org
May 6 07:27:31 localhost kernel: br0: port 2(vnet0) entering forwarding state
May 6 07:28:52 localhost avahi-daemon[1426]: Withdrawing address record for fe80::e8bb:b9ff:fe37:e99d on vnet0.
May 6 07:28:52 localhost kernel: br0: port 2(vnet0) entering disabled state
May 6 07:28:52 localhost kernel: device vnet0 left promiscuous mode
May 6 07:28:52 localhost kernel: br0: port 2(vnet0) entering disabled state
May 6 07:28:53 localhost ntpd[1645]: Deleting interface #16 vnet0, fe80::e8bb:b9ff:fe37:e99d#123, interface stats: received=0, sent=0, dropped=0, active_time=93 secs
May 6 07:31:46 localhost dhclient[16433]: DHCPREQUEST on br0 to 172.16.0.1 port 67
May 6 07:31:46 localhost dhclient[16433]: DHCPACK from 172.16.0.1
May 6 07:31:46 localhost dhclient[16433]: bound to 172.16.1.34 -- renewal in 1443 seconds.
May 6 07:39:58 localhost libvirtd: 07:39:58.139: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:40:13 localhost libvirtd: 07:40:13.003: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:40:50 localhost libvirtd: 07:40:50.590: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:40:50 localhost libvirtd: 07:40:50.596: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:40:50 localhost libvirtd: 07:40:50.626: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 6 07:40:50 localhost libvirtd: 07:40:50.633: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 6 07:40:50 localhost libvirtd: 07:40:50.634: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 6 07:40:50 localhost libvirtd: 07:40:50.635: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 6 07:41:24 localhost libvirtd: 07:41:24.709: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:41:24 localhost libvirtd: 07:41:24.714: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:41:24 localhost libvirtd: 07:41:24.740: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 6 07:41:24 localhost libvirtd: 07:41:24.751: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 6 07:41:24 localhost libvirtd: 07:41:24.752: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 6 07:41:24 localhost libvirtd: 07:41:24.753: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 6 07:41:24 localhost libvirtd: 07:41:24.847: error : qemudDomainLookupByUUID:3055 : Domain not found: no domain with matching uuid '65a94622-9617-db28-3463-c98eb7d1d782'
May 6 07:41:24 localhost libvirtd: 07:41:24.857: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 6 07:41:24 localhost libvirtd: 07:41:24.860: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 6 07:41:24 localhost kernel: device vnet0 entered promiscuous mode
May 6 07:41:24 localhost kernel: br0: port 2(vnet0) entering learning state
May 6 07:41:26 localhost avahi-daemon[1426]: Registering new address record for fe80::3c26:b0ff:feaa:e587 on vnet0.*.
May 6 07:41:27 localhost ntpd[1645]: Listening on interface #17 vnet0, fe80::3c26:b0ff:feaa:e587#123 Enabled
May 6 07:41:29 localhost setroubleshoot: SELinux is preventing /usr/bin/qemu-system-x86_64 "write" access on sr0. For complete SELinux messages. run sealert -l 312c4cde-a82c-48ba-b68c-efc300b28313
May 6 07:41:29 localhost ntpd_initres[1667]: host name not found: 0.fedora.pool.ntp.org
May 6 07:41:29 localhost ntpd_initres[1667]: host name not found: 1.fedora.pool.ntp.org
May 6 07:41:30 localhost ntpd_initres[1667]: host name not found: 2.fedora.pool.ntp.org
May 6 07:41:39 localhost kernel: br0: port 2(vnet0) entering forwarding state

Re: Windows 7 on KVM problems

Thursday, May 6, 2010 - 18:48 Haydn Solomon

This looks like a problem with your libvirt configration file. I see that libvirt isn't able to find your virtual disk image.

Intermittently fails to start VM.

Friday, August 20, 2010 - 08:36 Anonymous (not verified)

kernek version : 2.6.18-164.el5

command used to start VM:
virsh start vhost0088

std out:

error: Failed to start domain vhost0088
error: internal error unable to start guest: char device redirected to
/dev/pts/10.

Description:

Actually I have automated the provisioning and when it fails to start the vm it
removes the vm.img and vm.xml file. So there's no chance of trying a reboot
again.
Grepping logs is also not easy as the error is too intermittent.