[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-14 Thread Rayees Namathponnan (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060913#comment-14060913
 ] 

Rayees Namathponnan commented on CLOUDSTACK-7051:
-

Still getting below error 

2014-07-13 11:00:48,362 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-3:null) Trying to fetch storage pool 
4f3ad80a-b796-3db3-b126-9c12b5b5eafc from libvirt
2014-07-13 11:00:48,408 DEBUG [kvm.resource.BridgeVifDriver] 
(agentRequest-Handler-3:null) nic=[Nic:Control-169.254.1.157-null]
2014-07-13 11:00:48,410 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-3:null) InternalErrorException
com.cloud.exception.InternalErrorException: plug: protocol or vNetId value is 
null
at 
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:106)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4046)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3777)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3814)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1337)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-07-13 11:00:48,410 DEBUG [kvm.storage.KVMStoragePoolManager] 
(agentRequest-Handler-3:null) Disconnecting disk 
75816019-6cf8-499a-8de4-0f2176dca198
2014-07-13 11:00:48,410 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-3:null) Trying to fetch storage pool 
4f3ad80a-b796-3db3-b126-9c12b5b5eafc from libvirt
2014-07-13 11:00:48,414 DEBUG [kvm.resource.KVMGuestOsMapper] 
(agentRequest-Handler-5:null) Can't find the mapping of guest os: Debian 
GNU/Linux 5.0 (64-bit)
2014-07-13 11:00:48,414 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-5:null) Trying to fetch storage pool 
e9b0d73b-9890-3aae-8934-44bd194592e0 from libvirt
2014-07-13 11:00:48,478 DEBUG [kvm.resource.BridgeVifDriver] 
(agentRequest-Handler-5:null) nic=[Nic:Control-169.254.0.12-null]
2014-07-13 11:00:48,478 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) InternalErrorException
com.cloud.exception.InternalErrorException: plug: protocol or vNetId value is 
null
at 
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:106)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4046)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3777)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3814)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1337)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
2014-07-13 11:00:48,479 DEBUG [kvm.storage.KVMStoragePoolManager] 
(agentRequest-Handler-5:null) Disconnecting disk 
4c11d2b8-7a6d-41c5-98e8-ea275f593ca0
2014-07-13 11:00:48,479 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-5:null) Trying to fetch storage pool 
e9b0d73b-9890-3aae-8934-44bd194592e0 from libvirt
2014-07-13 11:00:48,489 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) 
Seq 1-288230376151711765:  { Ans: , MgmtId: 29066118877352, via: 1, Ver: v1, 
Flags: 10, [{com.cloud.agent.api.StartAnswer

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating 

[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-13 Thread Yoshikazu Nojima (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060019#comment-14060019
 ] 

Yoshikazu Nojima commented on CLOUDSTACK-7051:
--

I pushed a commit to fix the qemu-img info related bug.
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=e7392cdac63f1fb835599ef1545139bf6165a078

I confirmed qemu-img no longer throw errors in CentOS 6.3 environment, but we 
still see virtual NIC issue I mentioned above.

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating with latest 4.5 build,  copy command failing form 
 agent  observed below error in agent log, 
 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Execution is successful.
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7
 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 
 size=262144 encryption=off clus
 ter_size=65536 preallocation='off'
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Executing: qemu-img info --o
 utput json 
 /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Exit value is 1
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) info: invalid option -- '-'q
 emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: 
 qemu-img command [command options]QEMU d
 isk image utilityCommand syntax:  check [-f fmt] filename  create [-f fmt] 
 [-o options] filename [size]  commi
 t [-f fmt] [-t cache] filename  convert [-c] [-p] [-f fmt] [-t cache] [-O 
 output_fmt] [-o options] [-S sparse_
 size] filename [filename2 [...]] output_filename  info [-f fmt] filename  
 snapshot [-l | -a snapshot | -c snap
 shot | -d snapshot] filename  rebase [-f fmt] [-t cache] [-p] [-u] -b 
 backing_file [-F backing_fmt] filename
 resize filename [+ | -]sizeCommand parameters:  'filename' is a disk image 
 filename  'fmt' is the disk image f
 ormat. It is guessed automatically in most cases  'cache' is the cache mode 
 used to write the output disk imag
 e, the validoptions are: 'none', 'writeback' (default), 'writethrough' 
 and 'unsafe'  'size' is the disk im
 age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' 
 (megabyte, 1024k), 'G' (gigabyte, 102
 4M)and T (terabyte, 1024G) are supported. 'b' is ignored.  
 'output_filename' is the destination disk image
  filename  'output_fmt' is the destination format  'options' is a comma 
 separated list of format specific opti
 ons in aname=value format. Use -o ? for an overview of the options 
 supported by theused format  '-c' i
 ndicates that target image must be compressed (qcow format only)  '-u' 
 enables unsafe rebasing. It is assumed
 that old and new backing file   match exactly. The image doesn't need a 
 working backing file before
 rebasing in this case (useful for renaming the backing file)  '-h' with or 
 without a command shows this help a
 nd lists the supported formats  '-p' show progress of command (only certain 
 commands)  '-S' indicates the cons
 ecutive number of bytes that must contain only zeros   for qemu-img to 
 create a sparse image during conver
 sionParameters to snapshot subcommand:  'snapshot' is the name of the 
 snapshot to create, apply or delete  '-a
 ' applies a snapshot (revert disk to saved state)  '-c' creates a snapshot  
 '-d' deletes a snapshot  '-l' lists all snapshots in the given imageSupported 
 formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels 
 nbd blkdebug host_cdrom host_floppy host_device file



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-11 Thread Sudha Ponnaganti (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14058710#comment-14058710
 ] 

Sudha Ponnaganti commented on CLOUDSTACK-7051:
--

Any update n this ticket. 

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating with latest 4.5 build,  copy command failing form 
 agent  observed below error in agent log, 
 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Execution is successful.
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7
 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 
 size=262144 encryption=off clus
 ter_size=65536 preallocation='off'
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Executing: qemu-img info --o
 utput json 
 /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Exit value is 1
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) info: invalid option -- '-'q
 emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: 
 qemu-img command [command options]QEMU d
 isk image utilityCommand syntax:  check [-f fmt] filename  create [-f fmt] 
 [-o options] filename [size]  commi
 t [-f fmt] [-t cache] filename  convert [-c] [-p] [-f fmt] [-t cache] [-O 
 output_fmt] [-o options] [-S sparse_
 size] filename [filename2 [...]] output_filename  info [-f fmt] filename  
 snapshot [-l | -a snapshot | -c snap
 shot | -d snapshot] filename  rebase [-f fmt] [-t cache] [-p] [-u] -b 
 backing_file [-F backing_fmt] filename
 resize filename [+ | -]sizeCommand parameters:  'filename' is a disk image 
 filename  'fmt' is the disk image f
 ormat. It is guessed automatically in most cases  'cache' is the cache mode 
 used to write the output disk imag
 e, the validoptions are: 'none', 'writeback' (default), 'writethrough' 
 and 'unsafe'  'size' is the disk im
 age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' 
 (megabyte, 1024k), 'G' (gigabyte, 102
 4M)and T (terabyte, 1024G) are supported. 'b' is ignored.  
 'output_filename' is the destination disk image
  filename  'output_fmt' is the destination format  'options' is a comma 
 separated list of format specific opti
 ons in aname=value format. Use -o ? for an overview of the options 
 supported by theused format  '-c' i
 ndicates that target image must be compressed (qcow format only)  '-u' 
 enables unsafe rebasing. It is assumed
 that old and new backing file   match exactly. The image doesn't need a 
 working backing file before
 rebasing in this case (useful for renaming the backing file)  '-h' with or 
 without a command shows this help a
 nd lists the supported formats  '-p' show progress of command (only certain 
 commands)  '-S' indicates the cons
 ecutive number of bytes that must contain only zeros   for qemu-img to 
 create a sparse image during conver
 sionParameters to snapshot subcommand:  'snapshot' is the name of the 
 snapshot to create, apply or delete  '-a
 ' applies a snapshot (revert disk to saved state)  '-c' creates a snapshot  
 '-d' deletes a snapshot  '-l' lists all snapshots in the given imageSupported 
 formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels 
 nbd blkdebug host_cdrom host_floppy host_device file



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-11 Thread Kishan Kavala (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14058899#comment-14058899
 ] 

Kishan Kavala commented on CLOUDSTACK-7051:
---

Issue is blocked by CLOUDSTACK-6191. Marked CLOUDSTACK-6191 as blocker

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating with latest 4.5 build,  copy command failing form 
 agent  observed below error in agent log, 
 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Execution is successful.
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7
 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 
 size=262144 encryption=off clus
 ter_size=65536 preallocation='off'
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Executing: qemu-img info --o
 utput json 
 /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Exit value is 1
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) info: invalid option -- '-'q
 emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: 
 qemu-img command [command options]QEMU d
 isk image utilityCommand syntax:  check [-f fmt] filename  create [-f fmt] 
 [-o options] filename [size]  commi
 t [-f fmt] [-t cache] filename  convert [-c] [-p] [-f fmt] [-t cache] [-O 
 output_fmt] [-o options] [-S sparse_
 size] filename [filename2 [...]] output_filename  info [-f fmt] filename  
 snapshot [-l | -a snapshot | -c snap
 shot | -d snapshot] filename  rebase [-f fmt] [-t cache] [-p] [-u] -b 
 backing_file [-F backing_fmt] filename
 resize filename [+ | -]sizeCommand parameters:  'filename' is a disk image 
 filename  'fmt' is the disk image f
 ormat. It is guessed automatically in most cases  'cache' is the cache mode 
 used to write the output disk imag
 e, the validoptions are: 'none', 'writeback' (default), 'writethrough' 
 and 'unsafe'  'size' is the disk im
 age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' 
 (megabyte, 1024k), 'G' (gigabyte, 102
 4M)and T (terabyte, 1024G) are supported. 'b' is ignored.  
 'output_filename' is the destination disk image
  filename  'output_fmt' is the destination format  'options' is a comma 
 separated list of format specific opti
 ons in aname=value format. Use -o ? for an overview of the options 
 supported by theused format  '-c' i
 ndicates that target image must be compressed (qcow format only)  '-u' 
 enables unsafe rebasing. It is assumed
 that old and new backing file   match exactly. The image doesn't need a 
 working backing file before
 rebasing in this case (useful for renaming the backing file)  '-h' with or 
 without a command shows this help a
 nd lists the supported formats  '-p' show progress of command (only certain 
 commands)  '-S' indicates the cons
 ecutive number of bytes that must contain only zeros   for qemu-img to 
 create a sparse image during conver
 sionParameters to snapshot subcommand:  'snapshot' is the name of the 
 snapshot to create, apply or delete  '-a
 ' applies a snapshot (revert disk to saved state)  '-c' creates a snapshot  
 '-d' deletes a snapshot  '-l' lists all snapshots in the given imageSupported 
 formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels 
 nbd blkdebug host_cdrom host_floppy host_device file



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-11 Thread Yoshikazu Nojima (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059505#comment-14059505
 ] 

Yoshikazu Nojima commented on CLOUDSTACK-7051:
--

I couldn't reproduce the bug you experienced in my environment (CentOS 6.5, 
build: 4.5 (as of aab6e1222fc75a37f8015ba1d2c7bc923c1cf614)).
But I face another issue during plugging a nic to CPVM (off-topic).

2014-07-11 19:30:04,768 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) 
Request:Seq 1-3713780842720395322:  { Cmd , MgmtId: 161330501388, via: 1, Ver: 
v1, Flags: 100011, 
[{com.cloud.agent.api.StartCommand:{vm:{id:2,name:v-2-VM,type:ConsoleProxy,cpus:1,minSpeed:500,maxSpeed:500,minRam:1073741824,maxRam:1073741824,arch:x86_64,os:Debian
 GNU/Linux 5.0 (64-bit),bootArgs: template=domP type=consoleproxy 
host=198.172.18.40 port=8250 name=v-2-VM zone=1 pod=1 guid=Proxy.2 proxy_vm=2 
disable_rp_filter=true eth2ip=198.172.17.178 eth2mask=255.255.255.0 
gateway=198.172.17.1 eth0ip=169.254.0.133 eth0mask=255.255.0.0 
eth1ip=10.1.36.106 eth1mask=255.255.0.0 mgmtcidr=198.172.18.0/24 
localgw=10.1.2.17 internaldns1=8.8.8.8 
dns1=8.8.8.8,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:d398dba089ca9227,params:{},uuid:155d8eb0-180f-430f-8c21-b9721ddf262b,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:7653829b-52b1-4d0b-9087-e526d1de30ac,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ef9d8d36-ef60-321f-a2c3-7a74371293d7,id:3,poolType:NetworkFilesystem,host:10.1.3.46,path:/exports/stack8-primary1,port:2049,url:NetworkFilesystem://10.1.3.46/exports/stack8-primary1/?ROLE=PrimarySTOREUUID=ef9d8d36-ef60-321f-a2c3-7a74371293d7}},name:ROOT-2,size:0,path:7653829b-52b1-4d0b-9087-e526d1de30ac,volumeId:2,vmName:v-2-VM,accountId:1,format:QCOW2,provisioningType:THIN,id:2,deviceId:0,hypervisorType:KVM}},diskSeq:0,path:7653829b-52b1-4d0b-9087-e526d1de30ac,type:ROOT,_details:{managed:false,storagePort:2049,storageHost:10.1.3.46,volumeSize:0}}],nics:[{deviceId:2,networkRateMbps:-1,defaultNic:true,pxeDisable:true,uuid:606da644-6f88-4257-8b50-2875c7cdb9d3,ip:198.172.17.178,netmask:255.255.255.0,gateway:198.172.17.1,mac:06:fe:a4:00:00:0c,dns1:8.8.8.8,broadcastType:Vlan,type:Public,broadcastUri:vlan://untagged,isolationUri:vlan://untagged,isSecurityGroupEnabled:false,name:cloudbr1},{deviceId:0,networkRateMbps:-1,defaultNic:false,pxeDisable:true,uuid:66998599-dd25-426a-a080-b152ab732183,ip:169.254.0.133,netmask:255.255.0.0,gateway:169.254.0.1,mac:0e:00:a9:fe:00:85,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false},{deviceId:1,networkRateMbps:-1,defaultNic:false,pxeDisable:true,uuid:01b5e274-fb46-406b-a253-f1292d420ccd,ip:10.1.36.106,netmask:255.255.0.0,gateway:10.1.2.17,mac:06:f2:88:00:00:06,broadcastType:Native,type:Management,isSecurityGroupEnabled:false,name:cloudbr0}]},hostIp:10.1.2.41,executeInSequence:false,wait:0}},{com.cloud.agent.api.check.CheckSshCommand:{ip:169.254.0.133,port:3922,interval:6,retries:100,name:v-2-VM,wait:0}}]
 }
2014-07-11 19:30:04,769 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) 
Processing command: com.cloud.agent.api.StartCommand
2014-07-11 19:30:04,770 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-3:null) Trying to fetch storage pool 
ef9d8d36-ef60-321f-a2c3-7a74371293d7 from libvirt
2014-07-11 19:30:04,807 DEBUG [kvm.resource.KVMGuestOsMapper] 
(agentRequest-Handler-3:null) Can't find the mapping of guest os: Debian 
GNU/Linux 5.0 (64-bit)
2014-07-11 19:30:04,807 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-3:null) Trying to fetch storage pool 
ef9d8d36-ef60-321f-a2c3-7a74371293d7 from libvirt
2014-07-11 19:30:04,829 DEBUG [kvm.resource.BridgeVifDriver] 
(agentRequest-Handler-3:null) nic=[Nic:Control-169.254.0.133-null]
2014-07-11 19:30:04,829 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-3:null) InternalErrorException
com.cloud.exception.InternalErrorException: plug: protocol or vNetId value is 
null
at 
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:106)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4046)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3777)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3814)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1337)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 

[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-11 Thread Rayees Namathponnan (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059510#comment-14059510
 ] 

Rayees Namathponnan commented on CLOUDSTACK-7051:
-

I am using RHEL 6.3

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating with latest 4.5 build,  copy command failing form 
 agent  observed below error in agent log, 
 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Execution is successful.
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7
 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 
 size=262144 encryption=off clus
 ter_size=65536 preallocation='off'
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Executing: qemu-img info --o
 utput json 
 /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Exit value is 1
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) info: invalid option -- '-'q
 emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: 
 qemu-img command [command options]QEMU d
 isk image utilityCommand syntax:  check [-f fmt] filename  create [-f fmt] 
 [-o options] filename [size]  commi
 t [-f fmt] [-t cache] filename  convert [-c] [-p] [-f fmt] [-t cache] [-O 
 output_fmt] [-o options] [-S sparse_
 size] filename [filename2 [...]] output_filename  info [-f fmt] filename  
 snapshot [-l | -a snapshot | -c snap
 shot | -d snapshot] filename  rebase [-f fmt] [-t cache] [-p] [-u] -b 
 backing_file [-F backing_fmt] filename
 resize filename [+ | -]sizeCommand parameters:  'filename' is a disk image 
 filename  'fmt' is the disk image f
 ormat. It is guessed automatically in most cases  'cache' is the cache mode 
 used to write the output disk imag
 e, the validoptions are: 'none', 'writeback' (default), 'writethrough' 
 and 'unsafe'  'size' is the disk im
 age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' 
 (megabyte, 1024k), 'G' (gigabyte, 102
 4M)and T (terabyte, 1024G) are supported. 'b' is ignored.  
 'output_filename' is the destination disk image
  filename  'output_fmt' is the destination format  'options' is a comma 
 separated list of format specific opti
 ons in aname=value format. Use -o ? for an overview of the options 
 supported by theused format  '-c' i
 ndicates that target image must be compressed (qcow format only)  '-u' 
 enables unsafe rebasing. It is assumed
 that old and new backing file   match exactly. The image doesn't need a 
 working backing file before
 rebasing in this case (useful for renaming the backing file)  '-h' with or 
 without a command shows this help a
 nd lists the supported formats  '-p' show progress of command (only certain 
 commands)  '-S' indicates the cons
 ecutive number of bytes that must contain only zeros   for qemu-img to 
 create a sparse image during conver
 sionParameters to snapshot subcommand:  'snapshot' is the name of the 
 snapshot to create, apply or delete  '-a
 ' applies a snapshot (revert disk to saved state)  '-c' creates a snapshot  
 '-d' deletes a snapshot  '-l' lists all snapshots in the given imageSupported 
 formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels 
 nbd blkdebug host_cdrom host_floppy host_device file



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-11 Thread Yoshikazu Nojima (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059513#comment-14059513
 ] 

Yoshikazu Nojima commented on CLOUDSTACK-7051:
--

Here is a log CopyCommand works for my environment.

2014-07-11 19:44:12,774 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Request:Seq 1-6160642815266127881:  { Cmd , MgmtId: 161330501388, via: 1, Ver: 
v1, Flags: 100011, 
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:8764e810-094f-11e4-905f-0025900c170c,origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.bz2,uuid:8764e810-094f-11e4-905f-0025900c170c,id:3,format:QCOW2,accountId:1,checksum:85a1bed07bf43cbf022451cb2ecae4ff,hvm:false,displayText:SystemVM
 Template 
(KVM),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ef9d8d36-ef60-321f-a2c3-7a74371293d7,id:3,poolType:NetworkFilesystem,host:10.1.3.46,path:/exports/stack8-primary1,port:2049,url:NetworkFilesystem://10.1.3.46/exports/stack8-primary1/?ROLE=PrimarySTOREUUID=ef9d8d36-ef60-321f-a2c3-7a74371293d7}},name:routing-3,hypervisorType:KVM}},destTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:7f71939b-77bd-4917-9e3b-0fa3378cdfce,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ef9d8d36-ef60-321f-a2c3-7a74371293d7,id:3,poolType:NetworkFilesystem,host:10.1.3.46,path:/exports/stack8-primary1,port:2049,url:NetworkFilesystem://10.1.3.46/exports/stack8-primary1/?ROLE=PrimarySTOREUUID=ef9d8d36-ef60-321f-a2c3-7a74371293d7}},name:ROOT-19,size:0,volumeId:19,vmName:s-19-VM,accountId:1,format:QCOW2,provisioningType:THIN,id:19,deviceId:0,hypervisorType:KVM}},executeInSequence:false,options:{},wait:0}}]
 }
2014-07-11 19:44:12,774 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Processing command: org.apache.cloudstack.storage.command.CopyCommand
2014-07-11 19:44:12,775 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Trying to fetch storage pool 
ef9d8d36-ef60-321f-a2c3-7a74371293d7 from libvirt
2014-07-11 19:44:12,804 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Trying to fetch storage pool 
ef9d8d36-ef60-321f-a2c3-7a74371293d7 from libvirt
2014-07-11 19:44:12,845 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Creating volume 
7f71939b-77bd-4917-9e3b-0fa3378cdfce from template 
8764e810-094f-11e4-905f-0025900c170c in pool 
ef9d8d36-ef60-321f-a2c3-7a74371293d7 (NetworkFilesystem) with size 0
2014-07-11 19:44:12,845 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Attempting to create volume 
7f71939b-77bd-4917-9e3b-0fa3378cdfce (NetworkFilesystem) in pool 
ef9d8d36-ef60-321f-a2c3-7a74371293d7 with size 262144
2014-07-11 19:44:12,845 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Executing: qemu-img create -o preallocation=off, 
-f qcow2 
/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/7f71939b-77bd-4917-9e3b-0fa3378cdfce 
262144
2014-07-11 19:44:12,868 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Execution is successful.
2014-07-11 19:44:12,869 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Formatting 
'/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/7f71939b-77bd-4917-9e3b-0fa3378cdfce',
 fmt=qcow2 size=262144 encryption=off cluster_size=65536 preallocation='off'

2014-07-11 19:44:17,225 INFO  [cloud.agent.Agent] (UgentTask-4:null) Connected 
to the server
2014-07-11 19:44:17,225 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Executing: qemu-img info --output json 
/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/7f71939b-77bd-4917-9e3b-0fa3378cdfce
2014-07-11 19:44:17,233 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Execution is successful.
2014-07-11 19:44:17,234 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Executing: qemu-img create -o preallocation=off, 
-f qcow2 -b 
/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/8764e810-094f-11e4-905f-0025900c170c 
/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/7f71939b-77bd-4917-9e3b-0fa3378cdfce 
262144
2014-07-11 19:44:17,266 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Execution is successful.
2014-07-11 19:44:17,266 DEBUG [utils.script.Script] 
(agentRequest-Handler-1:null) Formatting 
'/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/7f71939b-77bd-4917-9e3b-0fa3378cdfce',
 fmt=qcow2 size=262144 
backing_file='/mnt/ef9d8d36-ef60-321f-a2c3-7a74371293d7/8764e810-094f-11e4-905f-0025900c170c'
 encryption=off cluster_size=65536 preallocation='off'

2014-07-11 19:44:17,267 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Seq 1-6160642815266127881:  { Ans: , MgmtId: 161330501388, via: 1, Ver: v1, 
Flags: 10, 

[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-11 Thread Yoshikazu Nojima (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059634#comment-14059634
 ] 

Yoshikazu Nojima commented on CLOUDSTACK-7051:
--

I reproduced the bug with CentOS 6.3. Since qemu-img provided by CentOS 6.3 
doesn't support --ourput option, this error raised.
I'll try to remove the --output option.

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating with latest 4.5 build,  copy command failing form 
 agent  observed below error in agent log, 
 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Execution is successful.
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7
 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 
 size=262144 encryption=off clus
 ter_size=65536 preallocation='off'
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Executing: qemu-img info --o
 utput json 
 /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Exit value is 1
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) info: invalid option -- '-'q
 emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: 
 qemu-img command [command options]QEMU d
 isk image utilityCommand syntax:  check [-f fmt] filename  create [-f fmt] 
 [-o options] filename [size]  commi
 t [-f fmt] [-t cache] filename  convert [-c] [-p] [-f fmt] [-t cache] [-O 
 output_fmt] [-o options] [-S sparse_
 size] filename [filename2 [...]] output_filename  info [-f fmt] filename  
 snapshot [-l | -a snapshot | -c snap
 shot | -d snapshot] filename  rebase [-f fmt] [-t cache] [-p] [-u] -b 
 backing_file [-F backing_fmt] filename
 resize filename [+ | -]sizeCommand parameters:  'filename' is a disk image 
 filename  'fmt' is the disk image f
 ormat. It is guessed automatically in most cases  'cache' is the cache mode 
 used to write the output disk imag
 e, the validoptions are: 'none', 'writeback' (default), 'writethrough' 
 and 'unsafe'  'size' is the disk im
 age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' 
 (megabyte, 1024k), 'G' (gigabyte, 102
 4M)and T (terabyte, 1024G) are supported. 'b' is ignored.  
 'output_filename' is the destination disk image
  filename  'output_fmt' is the destination format  'options' is a comma 
 separated list of format specific opti
 ons in aname=value format. Use -o ? for an overview of the options 
 supported by theused format  '-c' i
 ndicates that target image must be compressed (qcow format only)  '-u' 
 enables unsafe rebasing. It is assumed
 that old and new backing file   match exactly. The image doesn't need a 
 working backing file before
 rebasing in this case (useful for renaming the backing file)  '-h' with or 
 without a command shows this help a
 nd lists the supported formats  '-p' show progress of command (only certain 
 commands)  '-S' indicates the cons
 ecutive number of bytes that must contain only zeros   for qemu-img to 
 create a sparse image during conver
 sionParameters to snapshot subcommand:  'snapshot' is the name of the 
 snapshot to create, apply or delete  '-a
 ' applies a snapshot (revert disk to saved state)  '-c' creates a snapshot  
 '-d' deletes a snapshot  '-l' lists all snapshots in the given imageSupported 
 formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels 
 nbd blkdebug host_cdrom host_floppy host_device file



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,

2014-07-10 Thread Abhinandan Prateek (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14057366#comment-14057366
 ] 

Abhinandan Prateek commented on CLOUDSTACK-7051:


Kishan can you update the ticket with the progress.

 [Automation] Failed to create SSVM and CPVM in KVM, 
 

 Key: CLOUDSTACK-7051
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: RHEL : 6.3
 build : 4.5
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: agent.rar, management-server.rar


 SSVM and CPVM not creating with latest 4.5 build,  copy command failing form 
 agent  observed below error in agent log, 
 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Execution is successful.
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7
 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 
 size=262144 encryption=off clus
 ter_size=65536 preallocation='off'
 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Executing: qemu-img info --o
 utput json 
 /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) Exit value is 1
 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] 
 (agentRequest-Handler-1:null) info: invalid option -- '-'q
 emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: 
 qemu-img command [command options]QEMU d
 isk image utilityCommand syntax:  check [-f fmt] filename  create [-f fmt] 
 [-o options] filename [size]  commi
 t [-f fmt] [-t cache] filename  convert [-c] [-p] [-f fmt] [-t cache] [-O 
 output_fmt] [-o options] [-S sparse_
 size] filename [filename2 [...]] output_filename  info [-f fmt] filename  
 snapshot [-l | -a snapshot | -c snap
 shot | -d snapshot] filename  rebase [-f fmt] [-t cache] [-p] [-u] -b 
 backing_file [-F backing_fmt] filename
 resize filename [+ | -]sizeCommand parameters:  'filename' is a disk image 
 filename  'fmt' is the disk image f
 ormat. It is guessed automatically in most cases  'cache' is the cache mode 
 used to write the output disk imag
 e, the validoptions are: 'none', 'writeback' (default), 'writethrough' 
 and 'unsafe'  'size' is the disk im
 age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' 
 (megabyte, 1024k), 'G' (gigabyte, 102
 4M)and T (terabyte, 1024G) are supported. 'b' is ignored.  
 'output_filename' is the destination disk image
  filename  'output_fmt' is the destination format  'options' is a comma 
 separated list of format specific opti
 ons in aname=value format. Use -o ? for an overview of the options 
 supported by theused format  '-c' i
 ndicates that target image must be compressed (qcow format only)  '-u' 
 enables unsafe rebasing. It is assumed
 that old and new backing file   match exactly. The image doesn't need a 
 working backing file before
 rebasing in this case (useful for renaming the backing file)  '-h' with or 
 without a command shows this help a
 nd lists the supported formats  '-p' show progress of command (only certain 
 commands)  '-S' indicates the cons
 ecutive number of bytes that must contain only zeros   for qemu-img to 
 create a sparse image during conver
 sionParameters to snapshot subcommand:  'snapshot' is the name of the 
 snapshot to create, apply or delete  '-a
 ' applies a snapshot (revert disk to saved state)  '-c' creates a snapshot  
 '-d' deletes a snapshot  '-l' lists all snapshots in the given imageSupported 
 formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels 
 nbd blkdebug host_cdrom host_floppy host_device file



--
This message was sent by Atlassian JIRA
(v6.2#6252)