Hi guys, I posted this question at virt list on Fedora Project but I guess its a best place to ask help for my problem.
I'm trying to set up two kvm/libvirt hosts, I installed the set of packages contained in @kvm and @clustering groups, downloaded and installed glusterfs version 3.1.2, configured the cluster ( all working ), configured the gluster volume and mounted it on /var/lib/libvirt/images.
The problem is when I try to create the VM, after click in finish(virt-manager) it returns the following error:
Unable to complete install 'libvirt.libvirtError internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 724, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
# /var/log/messages
Jan 18 05:36:05 kvmsrv001 libvirtd: 05:36:05.227: error : internal error Timed out while reading console log output Jan 18 05:36:05 kvmsrv001 libvirtd: 05:36:05.227: error : internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
the image disk was created, but the domain(vm) is not. does someone experienced with this error? If I umount the gluster partition and use local disk the vm creation works fine.
Any suggestion will be appreciated.
- - iarlyy selbir
:wq!
debug I get using virt-install instead virt-manager
[root@kvmsrv001 ~]# virt-install -d --prompt Wed, 19 Jan 2011 11:59:59 DEBUG Requesting libvirt URI default Wed, 19 Jan 2011 11:59:59 DEBUG Received libvirt URI 'qemu:///system' Would you like to use KVM acceleration? (yes or no) yes Wed, 19 Jan 2011 12:00:03 DEBUG Requesting virt method 'hvm' Wed, 19 Jan 2011 12:00:03 DEBUG Received virt method 'hvm' Wed, 19 Jan 2011 12:00:03 DEBUG Hypervisor name is 'kvm' What is the name of your virtual machine? test How much RAM should be allocated (in megabytes)? 8192 What would you like to use as the disk (file path)? /var/lib/libvirt/images/test.img Wed, 19 Jan 2011 12:00:26 DEBUG Setting size for existing storage to '300.0' Wed, 19 Jan 2011 12:00:26 DEBUG Detected storage as type 'file' Wed, 19 Jan 2011 12:00:26 DEBUG Setting size for existing storage to '300.0' Wed, 19 Jan 2011 12:00:26 DEBUG Detected storage as type 'file' Wed, 19 Jan 2011 12:00:26 DEBUG Setting size for existing storage to '300.0' Wed, 19 Jan 2011 12:00:26 DEBUG Detected storage as type 'file' Wed, 19 Jan 2011 12:00:26 DEBUG DISPLAY is set: graphics defaulting to VNC. What is the install CD-ROM/ISO or URL? /var/lib/libvirt/images/win2003en.iso Wed, 19 Jan 2011 12:00:43 DEBUG DistroInstaller location is a local file/path: /var/lib/libvirt/images/win2003en.iso Wed, 19 Jan 2011 12:00:43 DEBUG Setting size for existing storage to '0.530550003052' Wed, 19 Jan 2011 12:00:43 DEBUG Detected storage as type 'file'
Starting install... Wed, 19 Jan 2011 12:00:43 DEBUG Setting size for existing storage to '0.530550003052' Wed, 19 Jan 2011 12:00:43 DEBUG Detected storage as type 'file' Wed, 19 Jan 2011 12:00:43 DEBUG Creating guest from: <domain type='kvm'> <name>test</name> <currentMemory>8388608</currentMemory> <memory>8388608</memory> <uuid>5c1f79ad-3a6c-f93c-2785-c5f49b182066</uuid> <os> <type arch='x86_64'>hvm</type> <boot dev='cdrom'/> </os> <features> <acpi/><apic/><pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <vcpu>1</vcpu> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <console type='pty'/> <disk type='file' device='disk'> <driver name='qemu' cache='none'/> <source file='/var/lib/libvirt/images/test.img'/> <target dev='hda' bus='ide'/> </disk> <disk type='file' device='cdrom'> <source file='/var/lib/libvirt/images/win2003en.iso'/> <target dev='hdc' bus='ide'/> <readonly/> </disk> <interface type='bridge'> <source bridge='br0'/> <mac address='54:52:00:42:8c:20'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' keymap='en-us'/> </devices> </domain>
Wed, 19 Jan 2011 12:01:13 ERROR internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start test'; otherwise, please restart your installation. Wed, 19 Jan 2011 12:01:13 ERROR internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img Traceback (most recent call last): File "/usr/sbin/virt-install", line 889, in ? main() File "/usr/sbin/virt-install", line 751, in main start_time, guest.start_install) File "/usr/sbin/virt-install", line 813, in do_install dom = install_func(conscb, progresscb, wait=(not wait)) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
Thanks for any help.
- - iarlyy selbir
:wq!
On Tue, Jan 18, 2011 at 12:53 PM, iarly selbir iarlyy@gmail.com wrote:
Hi guys, I posted this question at virt list on Fedora Project but I guess its a best place to ask help for my problem.
I'm trying to set up two kvm/libvirt hosts, I installed the set of packages contained in @kvm and @clustering groups, downloaded and installed glusterfs version 3.1.2, configured the cluster ( all working ), configured the gluster volume and mounted it on /var/lib/libvirt/images.
The problem is when I try to create the VM, after click in finish(virt-manager) it returns the following error:
Unable to complete install 'libvirt.libvirtError internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 724, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
# /var/log/messages
Jan 18 05:36:05 kvmsrv001 libvirtd: 05:36:05.227: error : internal error Timed out while reading console log output Jan 18 05:36:05 kvmsrv001 libvirtd: 05:36:05.227: error : internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/test.img
the image disk was created, but the domain(vm) is not. does someone experienced with this error? If I umount the gluster partition and use local disk the vm creation works fine.
Any suggestion will be appreciated.
iarlyy selbir
:wq!
I once tried moving my qcow2 VM guest files to a zfs-fuse volume, and the VMs refused to boot after. They only ran while on ext3 or ext4.
Although I wasn't trying at that time, I understand that in order migrate VMs between servers, you need a shared file system.
Maybe NFS is the answer?
On 01/19/2011 05:48 PM, compdoc wrote:
I once tried moving my qcow2 VM guest files to a zfs-fuse volume, and the VMs refused to boot after. They only ran while on ext3 or ext4.
I saw something similar when I put some images on an NTFS volume. This worked under Fedora 11 but when I switched to Fedora 14 the virt-manager refused to read the images. In the end I copied them onto the root ext4 system and then everything was fine.
Regards, Dennis
I gave up to use gluster as storage, now using gfs2+storage everything is working fine... now a question came up, after alter /etc/cluster/cluster.conf, what services need I to reload/restart after add a new vm resource?
Thanks
- - iarlyy selbir
:wq!
On Wed, Jan 19, 2011 at 9:49 PM, Dennis Jacobfeuerborn < dennisml@conversis.de> wrote:
On 01/19/2011 05:48 PM, compdoc wrote:
I once tried moving my qcow2 VM guest files to a zfs-fuse volume, and the VMs refused to boot after. They only ran while on ext3 or ext4.
I saw something similar when I put some images on an NTFS volume. This worked under Fedora 11 but when I switched to Fedora 14 the virt-manager refused to read the images. In the end I copied them onto the root ext4 system and then everything was fine.
Regards, Dennis _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Not sure I understand your question. You'd need to use "ccs_tool update /etc/cluster/cluster.conf.new" to propagate your modifications through the cluster.
(You'd need ccsd and cman, ofc.)
----
Florian
From: centos-virt-bounces@centos.org [mailto:centos-virt-bounces@centos.org] On Behalf Of iarly selbir Sent: Wednesday, January 26, 2011 4:40 PM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] cluster of virtual machines using libvirt/kvm + Gluster
I gave up to use gluster as storage, now using gfs2+storage everything is working fine... now a question came up, after alter /etc/cluster/cluster.conf, what services need I to reload/restart after add a new vm resource?
Thanks
- - iarlyy selbir
:wq!
On Wed, Jan 19, 2011 at 9:49 PM, Dennis Jacobfeuerborn < mailto:dennisml@conversis.de dennisml@conversis.de> wrote:
On 01/19/2011 05:48 PM, compdoc wrote:
I once tried moving my qcow2 VM guest files to a zfs-fuse volume, and the VMs refused to boot after. They only ran while on ext3 or ext4.
I saw something similar when I put some images on an NTFS volume. This worked under Fedora 11 but when I switched to Fedora 14 the virt-manager refused to read the images. In the end I copied them onto the root ext4 system and then everything was fine.
Regards, Dennis _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt