Re: Migrate migrated instance to another host
Hm I've not seen this template name before but in the code I see it's to do
with instances coming from vmware. To determine what the template is you
can execute this on the mysql server:
select * from vm_template where id = 212;
On Sun, Mar 24, 2024 at 10:25 PM Jimmy Huybrechts
wrote:
> Hi Ruben,
>
> I did not, seems like that is because of how migrated vm’s work, they all
> get the template named “kvm-default-vm-import-dummy-template”, I haven’t
> removed any templates.
>
> Not sure how I can see what template 212 is but I guess it’s that dummy
> template, which I guess does not exist since it’s called dummy?
>
> --
> Jimmy
>
> Van: Ruben Bosch
> Datum: zondag, 24 maart 2024 om 20:24
> Aan: users@cloudstack.apache.org
> Onderwerp: Re: Migrate migrated instance to another host
> Did you delete the template? "template 212 is not in store:2"
>
> On Sun, Mar 24, 2024 at 12:47 AM Jimmy Huybrechts
> wrote:
>
> > Hi Wei,
> >
> >
> >
> > See attached error log from when trying to migrate a vm that was migrated
> > before from the standalone host.
> >
> >
> >
> > --
> >
> > Jimmy
> >
> >
> >
> > *Van: *Wei ZHOU
> > *Datum: *zaterdag, 23 maart 2024 om 10:14
> > *Aan: *users@cloudstack.apache.org
> > *Onderwerp: *Re: Migrate migrated instance to another host
> >
> > Hi,
> >
> > /var/log/cloudstack/management/management-server.log
> > please note the log file is rotated everyday.
> >
> > -Wei
> >
> > On Sat, Mar 23, 2024 at 9:34 AM Jimmy Huybrechts
> > wrote:
> > >
> > > Hi Wei,
> > >
> > > I can, if you tell me where to look as I couldn’t find anything on them
> > in the logs.
> > >
> > > --
> > > Jimmy
> > >
> > > Van: Wei ZHOU
> > > Datum: vrijdag, 22 maart 2024 om 16:15
> > > Aan: users@cloudstack.apache.org
> > > Onderwerp: Re: Migrate migrated instance to another host
> > > Can you share the logs of vm migration and vm import ?
> > >
> > >
> > > On Fri, Mar 22, 2024 at 3:55 PM Jimmy Huybrechts >
> > wrote:
> > > >
> > > > I’ve migrated vm’s from a remote KVM host which worked fine and they
> > run on Cloudstack now.
> > > >
> > > > However, I just tried migrating one from one cloudstack host to
> > another, just like with instances made from a cloudstack host and it’s
> not
> > moving but ending up with an error.
> > > >
> > > > This is displayed in the webgui:
> > > > Failed to migrate VM [VM instance
> >
> {"id":109,"instanceName":"i-8-108-VM","type":"User","uuid":"2fbb0d84-7ea2-4092-aa5d-25a53eb3cda2"}]
> > along with its volumes due to [java.lang.NullPointerException].
> > > >
> > > > Now I’m trying to see in what log the complete error would be but I’m
> > coming up blank on which log I need.
> > > >
> > > > Instances created natively in Cloudstack are migrating just fine,
> it’s
> > only the ones that came from the remote KVM host before.
> > > >
> > > > --
> > > > Jimmy
> >
>
Re: Still struggling for steps to build pls help
Finally got it. It was a combination of loopback and router switch filter redirecting to a separate channel going to separate mac. Much thanks to all who helped. My next attempt is to dp a source compile. So far it is stuck only on the 70* directory, spitting out some jar related issues. I will TS on it and if there are questions, I will ask. How can we improve the documentation a little bit ? Great products need great documentation. Thank you once again to all Regards, RSK On Sat, Mar 23, 2024 at 2:10 AM Wei ZHOU wrote: > a. You do not need to configure it (nobody configures manually). Your > issue is unrelated to the beans. The bean errors are misleading. > > b. Jetty, not tomcat > > c. the default http port is 8080 in > /etc/cloudstack/management/server.properties > > > > -Wei > > > On Sat, Mar 23, 2024 at 7:59 AM Wingrunt Platform > wrote: > > > > Just a few more questions. > > a. You seem to have webApplicationContext.xml directive in your web.xml. > Is > > this to be available somewhere ? IF so where should it be ? if we install > > directory apt install ? > > b. The run time is an app server which I believe is tomcat for CS 4.19 . > Is > > this correct ? > > c. My understanding is that you have embedded this within your CS which > > opens port 8080. Right ? > > > > Thank you > > Best > > RSK > > [Opensource will never die, even if you stab a thousand times; or place a > > blue mirror to reflect the make believe sky] > > > > > > > > On Fri, Mar 22, 2024 at 5:54 PM Wingrunt Platform > > wrote: > > > > > @Pearl d'Silva Thank you. > > > Yes Db host same as management server both pointing to localhost. Also > > > tried specifically pointing to cloud management ip No luck > > > @Wei ZHOU Thanks to you too. > > > > > > Thank you so much. Hopefully I will get there soon. > > > > > > Best > > > RSK > > > > > > > > > On Fri, Mar 22, 2024 at 8:45 AM Pearl d'Silva < > pearl.dsi...@shapeblue.com> > > > wrote: > > > > > >> Is your database running on the same server / host on which you are > > >> trying to deploy the CloudStack setup? Can you verify the values of : > > >> db.cloud.host - this should point to the DB host > > >> cluster.node.IP - should point to the Management server (or the proper > > >> loopback address) > > >> > > >> in the ./client/conf/db.properties.in file and rebuild the code if > > >> you've built and deployed CloudStack from source. If you've set it up > using > > >> packages, verify the above mentioned values in > > >> /etc/cloudstack/management/db.properties and restart the Management > server > > >> if anything is changed in the file. > > >> > > >> Regards, > > >> > > >> > > >> > > >> > > >> From: Wingrunt Platform > > >> Sent: March 21, 2024 4:06 PM > > >> To: users@cloudstack.apache.org > > >> Subject: Re: Still struggling for steps to build pls help > > >> > > >> A friendly reminder. Racing against time :) > > >> Thank you so much. > > >> RSK > > >> > > >> On Wed, Mar 20, 2024 at 5:37 PM Wingrunt Platform > > > >> wrote: > > >> > > >> > Copied below - th management-server.log. > > >> > Looking forward to hearing from you. > > >> > > > >> > > > >> > 2024-03-20 17:17:18,407 DEBUG > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Trying to obtain module [nested-cloudstack] > > >> context. > > >> > 2024-03-20 17:17:18,407 DEBUG > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Trying to load module [nested-cloudstack] > context. > > >> > 2024-03-20 17:17:18,407 INFO > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Loading module context [nested-cloudstack] > from URL > > >> > > > >> > [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/nested-cloudstack/spring-nested-cloudstack-context.xml] > > >> > 2024-03-20 17:17:18,407 INFO > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Loading module context [nested-cloudstack] > from URL > > >> > > > >> > [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/outofbandmanagement/spring-core-lifecycle-outofbandmanagement-context-inheritable.xml] > > >> > 2024-03-20 17:17:18,407 INFO > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Loading module context [nested-cloudstack] > from URL > > >> > > > >> > [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/core/spring-core-lifecycle-core-context-inheritable.xml] > > >> > 2024-03-20 17:17:18,407 INFO > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Loading module context [nested-cloudstack] > from URL > > >> > > > >> > [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/system/spring-core-system-context-inheritable.xml] > > >> > 2024-03-20 17:17:18,407 INFO > [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] > > >> > (main:null) (logid:) Loading module
Re: Migrate migrated instance to another host
Hi Ruben,
I did not, seems like that is because of how migrated vm’s work, they all get
the template named “kvm-default-vm-import-dummy-template”, I haven’t removed
any templates.
Not sure how I can see what template 212 is but I guess it’s that dummy
template, which I guess does not exist since it’s called dummy?
--
Jimmy
Van: Ruben Bosch
Datum: zondag, 24 maart 2024 om 20:24
Aan: users@cloudstack.apache.org
Onderwerp: Re: Migrate migrated instance to another host
Did you delete the template? "template 212 is not in store:2"
On Sun, Mar 24, 2024 at 12:47 AM Jimmy Huybrechts
wrote:
> Hi Wei,
>
>
>
> See attached error log from when trying to migrate a vm that was migrated
> before from the standalone host.
>
>
>
> --
>
> Jimmy
>
>
>
> *Van: *Wei ZHOU
> *Datum: *zaterdag, 23 maart 2024 om 10:14
> *Aan: *users@cloudstack.apache.org
> *Onderwerp: *Re: Migrate migrated instance to another host
>
> Hi,
>
> /var/log/cloudstack/management/management-server.log
> please note the log file is rotated everyday.
>
> -Wei
>
> On Sat, Mar 23, 2024 at 9:34 AM Jimmy Huybrechts
> wrote:
> >
> > Hi Wei,
> >
> > I can, if you tell me where to look as I couldn’t find anything on them
> in the logs.
> >
> > --
> > Jimmy
> >
> > Van: Wei ZHOU
> > Datum: vrijdag, 22 maart 2024 om 16:15
> > Aan: users@cloudstack.apache.org
> > Onderwerp: Re: Migrate migrated instance to another host
> > Can you share the logs of vm migration and vm import ?
> >
> >
> > On Fri, Mar 22, 2024 at 3:55 PM Jimmy Huybrechts
> wrote:
> > >
> > > I’ve migrated vm’s from a remote KVM host which worked fine and they
> run on Cloudstack now.
> > >
> > > However, I just tried migrating one from one cloudstack host to
> another, just like with instances made from a cloudstack host and it’s not
> moving but ending up with an error.
> > >
> > > This is displayed in the webgui:
> > > Failed to migrate VM [VM instance
> {"id":109,"instanceName":"i-8-108-VM","type":"User","uuid":"2fbb0d84-7ea2-4092-aa5d-25a53eb3cda2"}]
> along with its volumes due to [java.lang.NullPointerException].
> > >
> > > Now I’m trying to see in what log the complete error would be but I’m
> coming up blank on which log I need.
> > >
> > > Instances created natively in Cloudstack are migrating just fine, it’s
> only the ones that came from the remote KVM host before.
> > >
> > > --
> > > Jimmy
>
Re: Migrate migrated instance to another host
Did you delete the template? "template 212 is not in store:2"
On Sun, Mar 24, 2024 at 12:47 AM Jimmy Huybrechts
wrote:
> Hi Wei,
>
>
>
> See attached error log from when trying to migrate a vm that was migrated
> before from the standalone host.
>
>
>
> --
>
> Jimmy
>
>
>
> *Van: *Wei ZHOU
> *Datum: *zaterdag, 23 maart 2024 om 10:14
> *Aan: *users@cloudstack.apache.org
> *Onderwerp: *Re: Migrate migrated instance to another host
>
> Hi,
>
> /var/log/cloudstack/management/management-server.log
> please note the log file is rotated everyday.
>
> -Wei
>
> On Sat, Mar 23, 2024 at 9:34 AM Jimmy Huybrechts
> wrote:
> >
> > Hi Wei,
> >
> > I can, if you tell me where to look as I couldn’t find anything on them
> in the logs.
> >
> > --
> > Jimmy
> >
> > Van: Wei ZHOU
> > Datum: vrijdag, 22 maart 2024 om 16:15
> > Aan: users@cloudstack.apache.org
> > Onderwerp: Re: Migrate migrated instance to another host
> > Can you share the logs of vm migration and vm import ?
> >
> >
> > On Fri, Mar 22, 2024 at 3:55 PM Jimmy Huybrechts
> wrote:
> > >
> > > I’ve migrated vm’s from a remote KVM host which worked fine and they
> run on Cloudstack now.
> > >
> > > However, I just tried migrating one from one cloudstack host to
> another, just like with instances made from a cloudstack host and it’s not
> moving but ending up with an error.
> > >
> > > This is displayed in the webgui:
> > > Failed to migrate VM [VM instance
> {"id":109,"instanceName":"i-8-108-VM","type":"User","uuid":"2fbb0d84-7ea2-4092-aa5d-25a53eb3cda2"}]
> along with its volumes due to [java.lang.NullPointerException].
> > >
> > > Now I’m trying to see in what log the complete error would be but I’m
> coming up blank on which log I need.
> > >
> > > Instances created natively in Cloudstack are migrating just fine, it’s
> only the ones that came from the remote KVM host before.
> > >
> > > --
> > > Jimmy
>
ISO Mount NFS Version Cloudstack 4.18 + xcpng 8.2.1
Hi Community,
My cloudstack deployment has NFS server that support NFS V4 only. The
Secondary Storage is attached successfully and we are able to deploy VM's.
Its Getting Mounted to XenServer as Ver=4.1.
The Actual issue is happening when we try to mount an ISO to a deployed VM.
It's always trying with NFS v3 and the ISO mount is failing.
Tried to setting the *secstorage.nfs.version to 4 and it does not have a
effect*
Xen logs:
Mar 24 16:34:51 xcp01 SM: [13233] sr_create {'sr_uuid':
'e16d9494-dd48-85e2-9166-6cbb12ffbdd4', 'subtask_of':
'DummyRef:|f271073d-ba31-4127-b375-dc78301167cf|SR.create', 'args': ['0'],
'host_ref': 'OpaqueRef:1f4335df-4651-4fa7-b249-9b97f770801d',
'session_ref': 'OpaqueRef:e9724b23-9f13-49cc-a582-b25978e23390',
'device_config': {'SRmaster': 'true', 'location':
'10.30.11.43:/Secondary/template/tmpl/1/207'},
'command': 'sr_create', 'sr_ref':
'OpaqueRef:c9453484-6e40-4d3c-a942-7098fae868e3'}
Mar 24 16:34:51 xcp01 SM: [13233] _testHost: Testing host/port:
10.30.11.43,2049
Mar 24 16:34:51 xcp01 SM: [13233] ['/usr/sbin/rpcinfo', '-s', '10.30.11.43']
Mar 24 16:34:51 xcp01 SM: [13233] pread SUCCESS
Mar 24 16:34:51 xcp01 SM: [13233] ['mount.nfs',
'10.30.11.43:/Secondary/template/tmpl/1/207',
'/var/run/sr-mount/e16d9494-dd48-85e2-9166-6cbb12ffbdd4', '-o',
'soft,proto=tcp,vers=3,acdirmin=0,acdirmax=0']
Mar 24 16:34:51 xcp01 SM: [13233] FAILED in util.pread: (rc 32) stdout: '',
stderr: 'mount.nfs: Protocol not supported
Mar 24 16:34:51 xcp01 SM: [13233] '
Mar 24 16:34:52 xcp01 SM: [13233] ['mount.nfs',
'10.30.11.43:/Secondary/template/tmpl/1/207',
'/var/run/sr-mount/e16d9494-dd48-85e2-9166-6cbb12ffbdd4', '-o',
'soft,proto=tcp,vers=3,acdirmin=0,acdirmax=0']
Mar 24 16:34:52 xcp01 SM: [13233] FAILED in util.pread: (rc 32) stdout: '',
stderr: 'mount.nfs: Protocol not supported
Any Guidance on this
Joan
Re: [ANNOUNCE] New PMC Chair & VP Apache CloudStack Project - Daniel Salvador
thanks Rohit, go Daniel On Thu, Mar 21, 2024 at 2:45 PM Rohit Yadav wrote: > > All, > > It gives me great pleasure to announce that the ASF board has accepted > CloudStack PMC resolution of Daniel Augusto Veronezi Salvador as the next PMC > Chair / VP of the Apache CloudStack project. > > I would like to thank everyone for the support I've received over the past > year. > > Please join me in congratulating Daniel, the new CloudStack PMC Chair / VP. > > Best Regards, > Rohit Yadav -- Daan
