cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Joseph <thomas.jo...@gmail.com>
Subject Re: Windows Template & Multiple SCSI Controllers
Date Wed, 29 Jul 2020 01:55:37 GMT
To add few more troubleshooting tips:
1. In template/VM settings tab, add entries for  Vnic (vmxnet3) and root &
data disk controllers (osdefault) from the dropdown menu.
2. You would need to have vmtools in the template.

Regards
Thomas

On Wed, 29 Jul 2020, 6:50 am Marc-Andre Jutras, <marcus@marcuspocus.com>
wrote:

> Hey Mike,
>
> On 2020-07-28 3:37 PM, Corey, Mike wrote:
> > I could use some advice on this.  I completely recreated my Window10
> VM/Template and imported it into ACS.  Deploying an instance runs; however
> a couple things are out of the normal and I could use some guidance on
> troubleshooting.
> >
> > 1 - The ASC template that ASC deploys does not include the network
> adapter that my imported OVA has.  Is this expected behavior of the
> template?
>
>
> Yes, It's expected, vNIC will be added to your VM only when you will
> start your VM...
>
>
> >
> > 2 - Booting the deployed Instance VM to UEFI can't see the system volume
> (device 0:0) and fails to boot up Windows.
> make sure you boot up your vm from cloudstack and not from vmware...
> >
> > 3 - Booting the deployed Instance VM to BIOS gets a Windows
> unrecoverable error - fails to boot up Windows correctly.
> same... make sure you boot up your vm from cloudstack and not from
> vmware...
> >
> > Cloning a VM from the ASC Deployed Template VM (adding a vnic after)
> works and the VM loads as expected.
>
> whoa, party on dude ;)
>
> to use vmxnet3 driver or any others specific settings in your template,
> on acs, select your template and under settings, add :
>
> nicAdapter = Vmxnet3
> and define any others settings there... ( keyboard, root scsi driver,
> etc... )
>
> >
> > So my question to the greater forum is what is ASC doing under the
> covers to the VM hardware that could prevent the OS / System Volume /
> primary partition from loading in the ASC deployed VM Instance?
> ACS drives vmware through API calls, ACS will push configuration to your
> vm only when needed : always manage your VM via Cloudstack and don't do
> anything directly on vmware ;)
> >
> >
> > Anyone with a VMware & CloudStack deployment running out here that can
> shed some light?
> yup, me ;)  6 ACS regions with vmware 5.5, 6.0 and 6.7 ( upgrade to 6.7
> on all regions on hold for now // covid... )
> >
> > Thanks!
> >
> > Mike
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Corey, Mike <mike.corey@sap.com>
> > Sent: Monday, July 27, 2020 11:48 AM
> > To: users@cloudstack.apache.org
> > Subject: [CAUTION] RE: Windows Template & Multiple SCSI Controllers
> >
> > Why would you hardcode the addition of unrequired/unnecessary "hardware"
> to the VM instance?  This wasn't the case for the CentOS deployment so why
> do it with Windows OS?
> >
> > I can't say for certain, but the VM instance that ACS creates doesn't
> start the OS (blue screen recovery console).  However, cloning from the
> template ACS creates in vCenter through the tradition vCenter method, the
> VM loads as normal.
> >
> > Can this be changed via a global setting or other config file edit?
> >
> >
> >
> > -----Original Message-----
> > From: Andrija Panic <andrija.panic@gmail.com>
> > Sent: Saturday, July 25, 2020 2:44 PM
> > To: users <users@cloudstack.apache.org>
> > Subject: Re: Windows Template & Multiple SCSI Controllers
> >
> > Hardcoded behavior of having 4 identical controllers, with all the
> volumes
> > attached to the first one.
> >
> > Why is this a problem for you?
> >
> > Best,
> >
> > On Fri, 24 Jul 2020, 19:55 Corey, Mike, <mike.corey@sap.com> wrote:
> >
> >> Hi,
> >>
> >>
> >>
> >> As I progress with my ACS & VMware setup I seem to hit a bump at every
> >> turn.  I’ve gotten to the point where I’m now able to upload a Windows
> 10
> >> template that we use in production (VMware) into ACS.  However, when I
> >> create a new instance through the GUI it is deployed with a total of 4
> SCSI
> >> controllers when it should only have ONE.
> >>
> >>
> >>
> >> What is strange is that the clone of the template that ACS copies into
> >> vCenter only has a single SCSI controller (as expected).  In fact, when
> I
> >> clone a VM (traditional vCenter method) from the ACS template that was
> >> create – that VM only has the single controller and boots to the OS
> fine.
> >>
> >>
> >>
> >> Any ideas are welcome as to why this behavior is occurring.
> >>
> >>
> >>
> >> Thanks!
> >>
> >> Mike
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> *Mike Corey*
> >>
> >>
> >> Technology Senior Consultant, IT CS CTW Operation & Virtualization
> Service
> >> US
> >>
> >>
> >> *SAP AMERICA, INC.* 3999 West Chester Pike, Newtown Square, 19073 United
> >> States
> >>
> >>
> >> T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message