[Users] Starting VM cloned from Template fails

Karli Sjöberg Karli.Sjoberg at slu.se
Fri Oct 26 08:01:11 UTC 2012


Hey all!

Error message is:
VM ginn-drive2-2 is down. Exit message: unsupported configuration: virtio only support device address type 'PCI'.

full engine.log:
http://pastebin.com/hscTPTkr

The first section in log is a successfull start of the original VM "ginn-drive2-1". That VM was made into a template and from that, a new VM called "ginn-drive2-2" was made. The other section is a failed attempt to start that VM. The lines I thought was most interesting is the different "CreateVDSCommand" that differs greatly between them:

ginn-drive2-1, starts:
2012-10-26 09:28:31,289 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand] (pool-3-thread-46) [5f41418d] org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand spiceSslCipherSuite=DEFAULT,memSize=1024,kvmEnable=true,smp=1,emulatedMachine=pc-0.14,vmType=kvm,keyboardLayout=en-us,nice=0,display=qxl,smpCoresPerSocket=1,spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,displayNetwork=Public_96,timeOffset=7202,transparentHugePages=true,vmId=1579e123-b311-469c-b9b0-502f730d9d50,devices=[Ljava.util.Map;@2651422d,acpiEnable=true,vmName=ginn-drive2-1,cpuType=Conroe,custom={device_286eebb5-40b8-439a-8835-584874a0f1d0device_98e1a25b-e626-4a5c-a067-c103be9909c1=VmId=1579e123-b311-469c-b9b0-502f730d9d50,DeviceId=98e1a25b-e626-4a5c-a067-c103be9909c1,Device=virtio-serial,Type=controller,BootOrder=0,SpecParams={},Address={bus=0x00, domain=0x0000, type=pci, slot=0x06, function=0x0},IsManaged=false,IsPlugged=true,IsReadOnly=false,alias=virtio-serial0, device_286eebb5-40b8-439a-8835-584874a0f1d0device_98e1a25b-e626-4a5c-a067-c103be9909c1device_0b6b20a6-f785-4e01-9875-b31687213648device_2a94a352-6848-4f04-89b1-b5419616f9b0device_516656d7-da1c-4e78-a843-4a0a609d3592=VmId=1579e123-b311-469c-b9b0-502f730d9d50,DeviceId=516656d7-da1c-4e78-a843-4a0a609d3592,Device=usb,Type=controller,BootOrder=0,SpecParams={},Address={bus=0x00, domain=0x0000, type=pci, slot=0x01, function=0x2},IsManaged=false,IsPlugged=true,IsReadOnly=false,alias=usb0, device_286eebb5-40b8-439a-8835-584874a0f1d0=VmId=1579e123-b311-469c-b9b0-502f730d9d50,DeviceId=286eebb5-40b8-439a-8835-584874a0f1d0,Device=ide,Type=controller,BootOrder=0,SpecParams={},Address={bus=0x00, domain=0x0000, type=pci, slot=0x01, function=0x1},IsManaged=false,IsPlugged=true,IsReadOnly=false,alias=ide0, device_286eebb5-40b8-439a-8835-584874a0f1d0device_98e1a25b-e626-4a5c-a067-c103be9909c1device_0b6b20a6-f785-4e01-9875-b31687213648device_2a94a352-6848-4f04-89b1-b5419616f9b0=VmId=1579e123-b311-469c-b9b0-502f730d9d50,DeviceId=2a94a352-6848-4f04-89b1-b5419616f9b0,Device=spicevmc,Type=channel,BootOrder=0,SpecParams={},Address={port=2, bus=0, controller=0, type=virtio-serial},IsManaged=false,IsPlugged=true,IsReadOnly=false,alias=channel1, device_286eebb5-40b8-439a-8835-584874a0f1d0device_98e1a25b-e626-4a5c-a067-c103be9909c1device_0b6b20a6-f785-4e01-9875-b31687213648=VmId=1579e123-b311-469c-b9b0-502f730d9d50,DeviceId=0b6b20a6-f785-4e01-9875-b31687213648,Device=unix,Type=channel,BootOrder=0,SpecParams={},Address={port=1, bus=0, controller=0, type=virtio-serial},IsManaged=false,IsPlugged=true,IsReadOnly=false,alias=channel0}
...
START, FullListVdsCommand
FINISH, FullListVdsCommand
VM ginn-drive2-1 moved from WaitForLaunch --> PoweringUp
START, FullListVdsCommand
FINISH, FullListVdsCommand

ginn-drive2-2, fails:
2012-10-26 09:31:32,843 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand] (pool-3-thread-47) [1d7bb724] org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand spiceSslCipherSuite=DEFAULT,memSize=1024,kvmEnable=true,smp=1,emulatedMachine=pc-0.14,vmType=kvm,keyboardLayout=en-us,nice=0,display=qxl,smpCoresPerSocket=1,spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,displayNetwork=Public_96,timeOffset=0,transparentHugePages=true,vmId=a93b4f54-077c-45ec-90d6-1233a0046bcf,devices=[Ljava.util.Map;@7f6354f9,acpiEnable=true,vmName=ginn-drive2-2,cpuType=Conroe,custom={device_f6da1f37-f102-4fd2-9f71-acbfda41d086=VmId=a93b4f54-077c-45ec-90d6-1233a0046bcf,DeviceId=f6da1f37-f102-4fd2-9f71-acbfda41d086,Device=usb,Type=controller,BootOrder=0,SpecParams={},Address={ domain=0x0000, bus=0x00,  type=pci,  function=0x2,  slot=0x01},IsManaged=false,IsPlugged=true,IsReadOnly=false,alias=}
...
START, DestroyVDSCommand
FINISH, DestroyVDSCommand
Running on vds during rerun failed vm: null
vm ginn-drive2-2 running in db and not running in vds - add to rerun treatment. vds Cirrus2-4
Rerun vm. Called from vds Cirrus2-4

And then it proceeds with trying to start the VM up on the rest of the Hosts in the Cluster, which fails the same way.

What´s up with that?


Med Vänliga Hälsningar
-------------------------------------------------------------------------------
Karli Sjöberg
Swedish University of Agricultural Sciences
Box 7079 (Visiting Address Kronåsvägen 8)
S-750 07 Uppsala, Sweden
Phone:  +46-(0)18-67 15 66
karli.sjoberg at slu.se<mailto:karli.sjoberg at adm.slu.se>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20121026/b19faade/attachment-0001.html>


More information about the Users mailing list