[libvirt-users] 回复: Re: virsh create error : monitor socket did not show up

[Osier Yang]

On 03/07/2012 06:44 PM, 张光鹏 wrote:
> ok,here is my log:
> Using CPU model "cpu64-rhel6"
> kvm: -device lsi,id=scsi0,bus=pci.0,addr=0x4: Parameter 'driver' expects 
> a driver name
> Try with argument '?' for a list.

This tells the "lsi" device is not supported by
your qemu. You must configured scsi device in
domain XML, and "lsilogic" is the default controller
model if you don't configure it. see

http://libvirt.org/formatdomain.html#elementsControllers

> I had to admit that my template is error ,this is my error part:
> 
>                 <disk type='file' device='disk' >
>                 xxx
>                 <target dev='hda'>
>                 xxx
>                 </disk>
>                 <disk type='file' device='cdrom' >
>                 <target dev='sdc'/>
>                 </disk> 
> 
> Althroug i had handled this error ,bug i didnot quite understand .
> ------------------------------------------------------------------------
> 张光鹏
> *发件人：* Osier Yang <mailto:jyang at redhat.com>
> *发送时间：* 2012-03-07 19:18
> *收件人：* 张光鹏 <mailto:zhanggp at neusoft.com>
> *抄送：* libvirt-users <mailto:libvirt-users at redhat.com>
> *主题：* Re: [libvirt-users] virsh create error : monitor socket did not 
> show up
> On 03/07/2012 06:22 PM, 张光鹏 wrote:
>  > Hi,all
>  > i get a problem as below when i create a vm:
>  > virsh create deployment.0
>  > error: Failed to create domain from deployment.0
>  > error: monitor socket did not show up.: No such file or directory
> Generally it tells the qemu failed to start,
> could you check if there is error log in
> guest log (e.g. /var/log/libvirt/qemu/$guest.log)
> Osier
> ---------------------------------------------------------------------------------------------------
> Confidentiality Notice: The information contained in this e-mail and any 
> accompanying attachment(s)
> is intended only for the use of the intended recipient and may be 
> confidential and/or privileged of
> Neusoft Corporation, its subsidiaries and/or its affiliates. If any 
> reader of this communication is
> not the intended recipient, unauthorized use, forwarding, printing, 
> storing, disclosure or copying
> is strictly prohibited, and may be unlawful.If you have received this 
> communication in error,please
> immediately notify the sender by return e-mail, and delete the original 
> message and all copies from
> your system. Thank you.
> ---------------------------------------------------------------------------------------------------