Hi, Just remove the <source> element from cdrom device and it should work even for xen. This will work, but is this the correct way? I din't remove soure attribute from config file for esx and kvm after installation, but there i had no issues. Can we control citrix xen server with libvirt ? If so, can you provide me the links for documents. Thanks, Vivek On Fri, Sep 7, 2012 at 2:42 PM, Jiri Denemark <jdenemar@redhat.com> wrote:
On Thu, Sep 06, 2012 at 19:47:27 +0530, vivek hari wrote:
Hi,
Yes, it failed to boot from hard disk, instead booted from cd. I made a simple modification to the domain xml config file attached before. I replaced "target='xvda' with target='hda'" and removed per boot option. This time, installation was successful and booted from hd. Since installation was successful i deleted the iso file, then rebooted the machine, but it failed with the error.
virsh # start vm-2 error: Failed to start domain vm-2 error: POST operation failed: xend_post: error from xen daemon: (xend.err 'Disk image does not exist: /var/lib/libvirt/images/Rhel53.iso')
I hope this is not the proper behaviour. Below is my config file i used this time.
...
<disk type='file' device='cdrom'> <source file='/var/lib/libvirt/images/Rhel53.iso'/> <target dev='hdc' bus='ide' /> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0' /> </disk>
...
Similar config file I used on kvm and esxi, i din't face any issue there. Can you let me know how libvirt sorts the boot device ?
Just remove the <source> element from cdrom device and it should work even for xen.
Jirka