Hi Chris, We need to migrate more than one hundred Windows VM into CloudStack. All of these VMs have a LSI Logic SAS SCSI controller. To avoid the blue screen, we need to add manually in vCenter a disk controller LSI Logic parallel manually and reboot the VM. If we can have the correct disk controller, it should be faster.
Regards, Fabrice -- Fabrice Brazier Apalia™ FR: +33-632-73-53-00 http://www.apalia.net fabrice.braz...@apalia.net -----Message d'origine----- De : Chris Sears [mailto:chris.x.se...@sungard.com] Envoyé : mardi 5 février 2013 18:04 À : cloudstack-users@incubator.apache.org Objet : Re: Blue screen appear if using the template uploaded Hi Fabrice, I'm not aware of any such feature, but there have been other situations where people have needed ways to customize the virtual hardware or VMX file gat CloudStack creates, so it might be an improvement worth exploring. In your case, I'm curious why you would need/prefer LSI Logic SAS over LSI Logic Parallel. I've found the performance to be roughly identical and I've found it easier to do guest-level automation with the LSI Parallel controller (due to how disks are detected). Thanks, - Chris On Tue, Feb 5, 2013 at 11:49 AM, Fabrice Brazier <fabrice.braz...@apalia.net> wrote: > Hi Kirk, > > Do you know if a new feature to change the disk controller used by the > guest VM will be available in CloudStack soon ? e.g (for VMware): LSI > Logic SAS Controller instead of LSI Logic Parallel > > Thanks, > Fabrice > > -----Original Message----- > From: Kirk Kosinski [mailto:kirkkosin...@gmail.com] > Sent: 2013年2月1日 15:12 > To: cloudstack-users@incubator.apache.org > Subject: Re: Blue screen appear if using the template uploaded > > Hi, Xintao. What disk controller did you configure on your uploaded > template? CloudStack only uses lsilogic and will ignore any special > configuration in the OVF of an uploaded OVA template, so make sure > that any VMs to be imported to CloudStack use the lsilogic disk > controller. > > This should be simple if you are creating the template yourself, but > might be a problem if you are using a virtual appliance from a vendor. > I saw someone recently who wanted to use a Juniper virtual appliance, > but it was configured with the buslogic controller for some reason and > wouldn't boot when deployed via CloudStack with lsilogic. In that > case Juniper built a new version that used lsilogic, but some vendors > might not be so helpful. > > Another possible problem would be if the uploaded template includes > multiple VMDKs and needs them all to boot. CloudStack doesn't support > OVAs with multiple VMDKs (or with ISOs) and it will only use one VMDK > from the OVA. > > I'm not sure what else would cause the BSOD you're seeing. If the > above doesn't help, share a screen shot of the BSOD or at least the > error code since it may help narrow down the problem. > > Kirk > > On 01/31/2013 07:02 PM, Xintao Song wrote: >> Hello, >> >> >> I had some trouble to create instance by template. But I could not >> know > how to solve it. >> >> >> >> Problems as below: >> >> I uploaded OVA template to cloudstack, and then create instance by >> this > template, but the bluescreen appears when the instance start. >> >> I am sure this template uploaded is well. But I did not know why the > bluescreen appeared by using this template uploaded to create instance > on cloudstack. >> If I used ISO to create instance and convert it to template, and then > create instance again by this template, it is very well. >> >> My environment: >> Cloudstack4.0+Vcenter5+Esxi5 >> >> Regards, >> Xintao Song >> >
