[
https://issues.apache.org/jira/browse/CLOUDSTACK-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422054#comment-16422054
]
ASF GitHub Bot commented on CLOUDSTACK-10348:
---------------------------------------------
blueorangutan commented on issue #2518: CLOUDSTACK-10348: Don't specify cache
mode for empty cdrom device
URL: https://github.com/apache/cloudstack/pull/2518#issuecomment-377894166
@borisstoyanov I understand these words: "help", "hello", "thanks",
"package", "test"
Test command usage: test [mgmt os] [hypervisor] [additional tests]
Mgmt OS options: ['centos6', 'centos7', 'ubuntu']
Hypervisor options: ['kvm-centos6', 'kvm-centos7', 'kvm-ubuntu',
'xenserver-71', 'xenserver-65sp1', 'xenserver-62sp1', 'vmware-65',
'vmware-60u2', 'vmware-55u3', 'vmware-51u1', 'vmware-50u1']
Additional tests: list of space separated tests with paths relative to the
`test/integration` directory, for example: component/test_acl_listvm.py
component/test_volumes.py
Note: when additional tests are passed, you need to specify mgmt server os
and hypervisor or use the `matrix` command.
Blessed contributors for kicking Trillian test jobs: ['rhtyd', 'nvazquez',
'PaulAngus', 'borisstoyanov', 'DaanHoogland', 'ernjvr', 'dhlaluku', 'houthuis',
'charles-phiri']
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> VMs fail to deploy on Ubuntu 17.10/18.04 KVM host
> -------------------------------------------------
>
> Key: CLOUDSTACK-10348
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10348
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Priority: Blocker
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> Issue observed:
> 2018-04-01 00:44:19,735 WARN [resource.wrapper.LibvirtStartCommandWrapper]
> (agentRequest-Handler-2:null) (logid:29139943) LibvirtException
> org.libvirt.LibvirtException: internal error: process exited while connecting
> to monitor: 2018-03-31T19:14:19.559497Z qemu-system-x86_64: -chardev
> pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0)
> 2018-03-31T19:14:19.560574Z qemu-system-x86_64: -drive
> file=/mnt/fd7d94b4-1672-3337-89f2-7dbc82e716f2/27d4b539-7dfd-4307-9d43-033d7c0a83bf,format=qcow2,if=none,id=drive-virtio-disk0,serial=27d4b5397dfd43079d43,cache=none:
> 'serial' is deprecated, please use the corresponding option of '-device'
> instead
> 2018-03-31T19:14:19.606326Z qemu-system-x86_64: -drive
> if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver
> or file
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.domainCreateXML(Unknown Source)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1414)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:92)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:47)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:75)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1438)
> at com.cloud.agent.Agent.processRequest(Agent.java:563)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:976)
> at com.cloud.utils.nio.Task.call(Task.java:83)
> at com.cloud.utils.nio.Task.call(Task.java:29)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
