You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Raymon van der Meijden <ra...@van-der-meijden.com> on 2018/10/29 13:23:39 UTC
System Template not working on second Zone
I`m running a cloudstack cluster for some time now and i`m getting the
hang of it. So i tried to add an additional Zone (Advanced) but i cannot
get the system VM to start. The VM`s are created and a running according
to cloudstack. But when i check the VM using VNC there is no OS
available ( Bootdisk not found)
I think the generation using the template is not working. But i cannot
figure out the issue. There is a secondary storage defined for this
zone. (And it seems to be working) And i have placed the template on
that storage.
The management log gives me debug logging, but i cannot find an issue.
The creation of the systemtempate when mounted to the new secondary storage.
root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/tank/secondary -u
http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
-h kvm -F
--2018-10-29 14:12:07--
http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
Resolving download.cloudstack.org (download.cloudstack.org)...
185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
Connecting to download.cloudstack.org
(download.cloudstack.org)|185.27.174.49|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 302864294 (289M) [application/x-bzip2]
Saving to:
'/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
100%[================================================================================================================================>]
302,864,294 6.48MB/s in 47s
2018-10-29 14:12:54 (6.18 MB/s) -
'/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
saved [302864294/302864294]
Uncompressing to
/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
(type bz2)...could take a long time
Moving to
/mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
take a while
Successfully installed system VM template to
/mnt/tank/secondary/template/tmpl/1/224/
But i think this should actually be /tmpl/10/224 since the id of the new
Zone is 10 (i have created and deleted some in the past)
Re: System Template not working on second Zone
Posted by Andrija Panic <an...@gmail.com>.
https://rohityadav.cloud/blog/cloudstack-kvm/
this is for most recent 4.11 release and Ubuntu 18.04.
Advanced Zone and NFS on same box etc - all in one box.
For local storage, you need to decide if you really want "Local storage" or
"Shared Storage: (i.e. local storage being by default
/var/lib/libvirt/images/) or just a regular shared NFS storage, but on same
box etc.
On Mon, 29 Oct 2018 at 15:56, Raymon van der Meijden <
raymon@van-der-meijden.com> wrote:
>
> - I have remove the secondary ip from cloudbr0
> - I have added a secondary storage to the zone (from another zone) which
> hold the templates
> - I have removed the server from the zone
> - I have re-added the server to the zone.
> - Disable and reanableld the zone
> - The system vm`s are now working. Deleting them will create working new
> copy`s so the platform itself working
>
> During the reconnection of the server it was still trying to mount to
> the .190 adres. So i briefly added it with ifconfig. This issue now
> seems resolved
>
> I now want to find out how to create a single node zone (which also hold
> the NFS secondary storage) and use local SSD for it primary storage,
> which already works.
>
> This is clearly not working, any thoughts on how to use the KVM server
> als NFS server. I got inspired by
>
> http://www.greenhills.co.uk/2013/08/30/cloudstack-single-server-on-ubuntu-with-kvm.html
>
> auto cloudbr0
> iface cloudbr0 inet static
> #iface cloudbr0 inet manual
> bridge_ports em1.160
> #bridge_ports em1
> address 192.168.160.241
> netmask 255.255.255.0
> gateway 192.168.160.1
> dns-nameservers 8.8.8.8 8.8.4.4
> dns-domain domain.com
> bridge_fd 5
> bridge_stp off
> bridge_maxwait 1
>
> #auto cloudbr0:1
> #iface cloudbr0:1 inet static
> # address 192.168.160.190
> # netmask 255.255.255.0
>
>
> This server is a single sever located in a DC, so i cannot add another
> box to be NFS storage
>
>
>
> On 29-10-18 15:37, Andrija Panic wrote:
> > It would help if you would explain networking on the KVM side - how many
> > interfaces, bonds or not, vlans or not, bridge names, etc and how did
> you
> > setup your differetn Traffic across Physical Network inside CloudStack
> (did
> > you place red circle "Storage" on the right part on Physical Network, or
> > not, etc - I'm talking about UI setup of Zone here)
> >
> > Each Traffic Type (Management, Guest, Storage, Public) can and should
> have
> > a KVM traffic label set to it. i.e. it's not "label of the Management
> > Zone", it's label for each Network Traffic Type that you placed (drag and
> > drop via UI, if created via UI...) on the Physical Network during
> creating
> > the Advanced Zone.
> >
> > Networking (for Advanced Zone specifically) can be a bit of challenge to
> > master and understand how it works, why to define traffic labels, and it
> > works in general - but once that is all mastered, it's pretty
> > straightforward...
> >
> >
> >
> >
> > On Mon, 29 Oct 2018 at 15:23, Raymon van der Meijden <
> > raymon@van-der-meijden.com> wrote:
> >
> >> The labels of the Management Zone are cloudbr0 on all KVM Hypervisors.
> >> The difference with this hypervisor is that i tried running a cloudbr0:1
> >> subinterface for the hypervisor to also act as NFS storage on the
> >> secondary IP.
> >>
> >> This secondary IP is also making the connection to the management
> >> server, maybe this is providing the issue.
> >>
> >> I have removed the secondary ip and will try again
> >>
> >>
> >> On 29-10-18 14:51, Andrija Panic wrote:
> >>> Go to Infrastructure --> Zones --> ZONE_NAME --> Physical Networks -->
> >>> NAME_of_SECONDARY_STORAGE_NETWORK - if you used dedicated STORAGE
> >> network,
> >>> otherwise it's shared with the Management Network, so go to this one,
> and
> >>> than again click on "Storage" button again and make sure KVM traffic
> >> label
> >>> is set to the correct name of the BRIDGE.
> >>>
> >>> as in images:
> >>> https://pasteboard.co/HKHvTZF.png
> >>> https://pasteboard.co/HKHuK5r.png
> >>>
> >>> KVM traffic labels = name of the physical interface on KVM host
> (usually
> >>> name of the bridge) - so CloudStack will know to which bridge to join
> the
> >>> SSVM vNIC...so SSVM can contact secondary storage...
> >>>
> >>>
> >>>
> >>>
> >>> On Mon, 29 Oct 2018 at 14:44, Raymon van der Meijden <
> >>> raymon@van-der-meijden.com> wrote:
> >>>
> >>>> Where did you find out these naming issues, so i can double check.
> >>>> Because the places i have found look simular to me
> >>>>
> >>>>
> >>>> On 29-10-18 14:37, Yordan Kostov wrote:
> >>>>> Hello Raymon,
> >>>>>
> >>>>> I had the same issue (SSVMs booting but no OS existing).
> >>>>> At the end I found out that this happened because my network
> >>>> labels were not set correctly so the networks were not allocated
> >> properly
> >>>> no proper connection to the secondary storage was available. This
> means
> >>>> that the system creates the VM metdata (compute, ram, network
> >> interfaces)
> >>>> but could not fetch the system disks from the secondary storage (so
> you
> >> see
> >>>> the vms but they are actually empty).
> >>>>> I hope that helps!
> >>>>>
> >>>>> Best regards,
> >>>>> Jordan
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
> >>>>> Sent: Monday, October 29, 2018 3:24 PM
> >>>>> To: users@cloudstack.apache.org
> >>>>> Subject: System Template not working on second Zone
> >>>>>
> >>>>>
> >>>>> I`m running a cloudstack cluster for some time now and i`m getting
> the
> >>>> hang of it. So i tried to add an additional Zone (Advanced) but i
> cannot
> >>>> get the system VM to start. The VM`s are created and a running
> >> according to
> >>>> cloudstack. But when i check the VM using VNC there is no OS
> available (
> >>>> Bootdisk not found)
> >>>>> I think the generation using the template is not working. But i
> cannot
> >>>> figure out the issue. There is a secondary storage defined for this
> >> zone.
> >>>> (And it seems to be working) And i have placed the template on that
> >> storage.
> >>>>> The management log gives me debug logging, but i cannot find an
> issue.
> >>>>>
> >>>>>
> >>>>> The creation of the systemtempate when mounted to the new secondary
> >>>> storage.
> >>>>> root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
> >>>>>
> >>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> >>>>> -m /mnt/tank/secondary -u
> >>>>>
> >>
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> >>>>> -h kvm -F
> >>>>> --2018-10-29 14:12:07--
> >>>>>
> >>
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> >>>>> Resolving download.cloudstack.org (download.cloudstack.org)...
> >>>>> 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
> >>>>> Connecting to download.cloudstack.org
> >>>>> (download.cloudstack.org)|185.27.174.49|:80... connected.
> >>>>> HTTP request sent, awaiting response... 200 OK
> >>>>> Length: 302864294 (289M) [application/x-bzip2] Saving to:
> >>>>>
> >>
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> >>
> 100%[================================================================================================================================>]
> >>>>> 302,864,294 6.48MB/s in 47s
> >>>>>
> >>>>> 2018-10-29 14:12:54 (6.18 MB/s) -
> >>>>>
> >>
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> >>>>> saved [302864294/302864294]
> >>>>>
> >>>>> Uncompressing to
> >>>>>
> >>
> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
> >>>>> (type bz2)...could take a long time
> >>>>> Moving to
> >>>>>
> >>
> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
> >>>>> take a while
> >>>>> Successfully installed system VM template to
> >>>> /mnt/tank/secondary/template/tmpl/1/224/
> >>>>> But i think this should actually be /tmpl/10/224 since the id of the
> >> new
> >>>> Zone is 10 (i have created and deleted some in the past)
> >>>>>
> >>>>>
> >
>
--
Andrija Panić
Re: System Template not working on second Zone
Posted by Raymon van der Meijden <ra...@van-der-meijden.com>.
- I have remove the secondary ip from cloudbr0
- I have added a secondary storage to the zone (from another zone) which
hold the templates
- I have removed the server from the zone
- I have re-added the server to the zone.
- Disable and reanableld the zone
- The system vm`s are now working. Deleting them will create working new
copy`s so the platform itself working
During the reconnection of the server it was still trying to mount to
the .190 adres. So i briefly added it with ifconfig. This issue now
seems resolved
I now want to find out how to create a single node zone (which also hold
the NFS secondary storage) and use local SSD for it primary storage,
which already works.
This is clearly not working, any thoughts on how to use the KVM server
als NFS server. I got inspired by
http://www.greenhills.co.uk/2013/08/30/cloudstack-single-server-on-ubuntu-with-kvm.html
auto cloudbr0
iface cloudbr0 inet static
#iface cloudbr0 inet manual
bridge_ports em1.160
#bridge_ports em1
address 192.168.160.241
netmask 255.255.255.0
gateway 192.168.160.1
dns-nameservers 8.8.8.8 8.8.4.4
dns-domain domain.com
bridge_fd 5
bridge_stp off
bridge_maxwait 1
#auto cloudbr0:1
#iface cloudbr0:1 inet static
# address 192.168.160.190
# netmask 255.255.255.0
This server is a single sever located in a DC, so i cannot add another
box to be NFS storage
On 29-10-18 15:37, Andrija Panic wrote:
> It would help if you would explain networking on the KVM side - how many
> interfaces, bonds or not, vlans or not, bridge names, etc and how did you
> setup your differetn Traffic across Physical Network inside CloudStack (did
> you place red circle "Storage" on the right part on Physical Network, or
> not, etc - I'm talking about UI setup of Zone here)
>
> Each Traffic Type (Management, Guest, Storage, Public) can and should have
> a KVM traffic label set to it. i.e. it's not "label of the Management
> Zone", it's label for each Network Traffic Type that you placed (drag and
> drop via UI, if created via UI...) on the Physical Network during creating
> the Advanced Zone.
>
> Networking (for Advanced Zone specifically) can be a bit of challenge to
> master and understand how it works, why to define traffic labels, and it
> works in general - but once that is all mastered, it's pretty
> straightforward...
>
>
>
>
> On Mon, 29 Oct 2018 at 15:23, Raymon van der Meijden <
> raymon@van-der-meijden.com> wrote:
>
>> The labels of the Management Zone are cloudbr0 on all KVM Hypervisors.
>> The difference with this hypervisor is that i tried running a cloudbr0:1
>> subinterface for the hypervisor to also act as NFS storage on the
>> secondary IP.
>>
>> This secondary IP is also making the connection to the management
>> server, maybe this is providing the issue.
>>
>> I have removed the secondary ip and will try again
>>
>>
>> On 29-10-18 14:51, Andrija Panic wrote:
>>> Go to Infrastructure --> Zones --> ZONE_NAME --> Physical Networks -->
>>> NAME_of_SECONDARY_STORAGE_NETWORK - if you used dedicated STORAGE
>> network,
>>> otherwise it's shared with the Management Network, so go to this one, and
>>> than again click on "Storage" button again and make sure KVM traffic
>> label
>>> is set to the correct name of the BRIDGE.
>>>
>>> as in images:
>>> https://pasteboard.co/HKHvTZF.png
>>> https://pasteboard.co/HKHuK5r.png
>>>
>>> KVM traffic labels = name of the physical interface on KVM host (usually
>>> name of the bridge) - so CloudStack will know to which bridge to join the
>>> SSVM vNIC...so SSVM can contact secondary storage...
>>>
>>>
>>>
>>>
>>> On Mon, 29 Oct 2018 at 14:44, Raymon van der Meijden <
>>> raymon@van-der-meijden.com> wrote:
>>>
>>>> Where did you find out these naming issues, so i can double check.
>>>> Because the places i have found look simular to me
>>>>
>>>>
>>>> On 29-10-18 14:37, Yordan Kostov wrote:
>>>>> Hello Raymon,
>>>>>
>>>>> I had the same issue (SSVMs booting but no OS existing).
>>>>> At the end I found out that this happened because my network
>>>> labels were not set correctly so the networks were not allocated
>> properly
>>>> no proper connection to the secondary storage was available. This means
>>>> that the system creates the VM metdata (compute, ram, network
>> interfaces)
>>>> but could not fetch the system disks from the secondary storage (so you
>> see
>>>> the vms but they are actually empty).
>>>>> I hope that helps!
>>>>>
>>>>> Best regards,
>>>>> Jordan
>>>>>
>>>>> -----Original Message-----
>>>>> From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
>>>>> Sent: Monday, October 29, 2018 3:24 PM
>>>>> To: users@cloudstack.apache.org
>>>>> Subject: System Template not working on second Zone
>>>>>
>>>>>
>>>>> I`m running a cloudstack cluster for some time now and i`m getting the
>>>> hang of it. So i tried to add an additional Zone (Advanced) but i cannot
>>>> get the system VM to start. The VM`s are created and a running
>> according to
>>>> cloudstack. But when i check the VM using VNC there is no OS available (
>>>> Bootdisk not found)
>>>>> I think the generation using the template is not working. But i cannot
>>>> figure out the issue. There is a secondary storage defined for this
>> zone.
>>>> (And it seems to be working) And i have placed the template on that
>> storage.
>>>>> The management log gives me debug logging, but i cannot find an issue.
>>>>>
>>>>>
>>>>> The creation of the systemtempate when mounted to the new secondary
>>>> storage.
>>>>> root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
>>>>>
>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>>>> -m /mnt/tank/secondary -u
>>>>>
>> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
>>>>> -h kvm -F
>>>>> --2018-10-29 14:12:07--
>>>>>
>> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
>>>>> Resolving download.cloudstack.org (download.cloudstack.org)...
>>>>> 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
>>>>> Connecting to download.cloudstack.org
>>>>> (download.cloudstack.org)|185.27.174.49|:80... connected.
>>>>> HTTP request sent, awaiting response... 200 OK
>>>>> Length: 302864294 (289M) [application/x-bzip2] Saving to:
>>>>>
>> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>> 100%[================================================================================================================================>]
>>>>> 302,864,294 6.48MB/s in 47s
>>>>>
>>>>> 2018-10-29 14:12:54 (6.18 MB/s) -
>>>>>
>> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>>>>> saved [302864294/302864294]
>>>>>
>>>>> Uncompressing to
>>>>>
>> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
>>>>> (type bz2)...could take a long time
>>>>> Moving to
>>>>>
>> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
>>>>> take a while
>>>>> Successfully installed system VM template to
>>>> /mnt/tank/secondary/template/tmpl/1/224/
>>>>> But i think this should actually be /tmpl/10/224 since the id of the
>> new
>>>> Zone is 10 (i have created and deleted some in the past)
>>>>>
>>>>>
>
Re: System Template not working on second Zone
Posted by Andrija Panic <an...@gmail.com>.
It would help if you would explain networking on the KVM side - how many
interfaces, bonds or not, vlans or not, bridge names, etc and how did you
setup your differetn Traffic across Physical Network inside CloudStack (did
you place red circle "Storage" on the right part on Physical Network, or
not, etc - I'm talking about UI setup of Zone here)
Each Traffic Type (Management, Guest, Storage, Public) can and should have
a KVM traffic label set to it. i.e. it's not "label of the Management
Zone", it's label for each Network Traffic Type that you placed (drag and
drop via UI, if created via UI...) on the Physical Network during creating
the Advanced Zone.
Networking (for Advanced Zone specifically) can be a bit of challenge to
master and understand how it works, why to define traffic labels, and it
works in general - but once that is all mastered, it's pretty
straightforward...
On Mon, 29 Oct 2018 at 15:23, Raymon van der Meijden <
raymon@van-der-meijden.com> wrote:
>
> The labels of the Management Zone are cloudbr0 on all KVM Hypervisors.
> The difference with this hypervisor is that i tried running a cloudbr0:1
> subinterface for the hypervisor to also act as NFS storage on the
> secondary IP.
>
> This secondary IP is also making the connection to the management
> server, maybe this is providing the issue.
>
> I have removed the secondary ip and will try again
>
>
> On 29-10-18 14:51, Andrija Panic wrote:
> > Go to Infrastructure --> Zones --> ZONE_NAME --> Physical Networks -->
> > NAME_of_SECONDARY_STORAGE_NETWORK - if you used dedicated STORAGE
> network,
> > otherwise it's shared with the Management Network, so go to this one, and
> > than again click on "Storage" button again and make sure KVM traffic
> label
> > is set to the correct name of the BRIDGE.
> >
> > as in images:
> > https://pasteboard.co/HKHvTZF.png
> > https://pasteboard.co/HKHuK5r.png
> >
> > KVM traffic labels = name of the physical interface on KVM host (usually
> > name of the bridge) - so CloudStack will know to which bridge to join the
> > SSVM vNIC...so SSVM can contact secondary storage...
> >
> >
> >
> >
> > On Mon, 29 Oct 2018 at 14:44, Raymon van der Meijden <
> > raymon@van-der-meijden.com> wrote:
> >
> >> Where did you find out these naming issues, so i can double check.
> >> Because the places i have found look simular to me
> >>
> >>
> >> On 29-10-18 14:37, Yordan Kostov wrote:
> >>> Hello Raymon,
> >>>
> >>> I had the same issue (SSVMs booting but no OS existing).
> >>> At the end I found out that this happened because my network
> >> labels were not set correctly so the networks were not allocated
> properly
> >> no proper connection to the secondary storage was available. This means
> >> that the system creates the VM metdata (compute, ram, network
> interfaces)
> >> but could not fetch the system disks from the secondary storage (so you
> see
> >> the vms but they are actually empty).
> >>> I hope that helps!
> >>>
> >>> Best regards,
> >>> Jordan
> >>>
> >>> -----Original Message-----
> >>> From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
> >>> Sent: Monday, October 29, 2018 3:24 PM
> >>> To: users@cloudstack.apache.org
> >>> Subject: System Template not working on second Zone
> >>>
> >>>
> >>> I`m running a cloudstack cluster for some time now and i`m getting the
> >> hang of it. So i tried to add an additional Zone (Advanced) but i cannot
> >> get the system VM to start. The VM`s are created and a running
> according to
> >> cloudstack. But when i check the VM using VNC there is no OS available (
> >> Bootdisk not found)
> >>>
> >>> I think the generation using the template is not working. But i cannot
> >> figure out the issue. There is a secondary storage defined for this
> zone.
> >> (And it seems to be working) And i have placed the template on that
> storage.
> >>> The management log gives me debug logging, but i cannot find an issue.
> >>>
> >>>
> >>> The creation of the systemtempate when mounted to the new secondary
> >> storage.
> >>> root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
> >>>
> >>
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> >>> -m /mnt/tank/secondary -u
> >>>
> >>
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> >>> -h kvm -F
> >>> --2018-10-29 14:12:07--
> >>>
> >>
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> >>> Resolving download.cloudstack.org (download.cloudstack.org)...
> >>> 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
> >>> Connecting to download.cloudstack.org
> >>> (download.cloudstack.org)|185.27.174.49|:80... connected.
> >>> HTTP request sent, awaiting response... 200 OK
> >>> Length: 302864294 (289M) [application/x-bzip2] Saving to:
> >>>
> >>
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> >>>
> >>
> 100%[================================================================================================================================>]
> >>> 302,864,294 6.48MB/s in 47s
> >>>
> >>> 2018-10-29 14:12:54 (6.18 MB/s) -
> >>>
> >>
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> >>> saved [302864294/302864294]
> >>>
> >>> Uncompressing to
> >>>
> >>
> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
> >>> (type bz2)...could take a long time
> >>> Moving to
> >>>
> >>
> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
> >>> take a while
> >>> Successfully installed system VM template to
> >> /mnt/tank/secondary/template/tmpl/1/224/
> >>>
> >>> But i think this should actually be /tmpl/10/224 since the id of the
> new
> >> Zone is 10 (i have created and deleted some in the past)
> >>>
> >>>
> >>>
> >
>
--
Andrija Panić
Re: System Template not working on second Zone
Posted by Raymon van der Meijden <ra...@van-der-meijden.com>.
The labels of the Management Zone are cloudbr0 on all KVM Hypervisors.
The difference with this hypervisor is that i tried running a cloudbr0:1
subinterface for the hypervisor to also act as NFS storage on the
secondary IP.
This secondary IP is also making the connection to the management
server, maybe this is providing the issue.
I have removed the secondary ip and will try again
On 29-10-18 14:51, Andrija Panic wrote:
> Go to Infrastructure --> Zones --> ZONE_NAME --> Physical Networks -->
> NAME_of_SECONDARY_STORAGE_NETWORK - if you used dedicated STORAGE network,
> otherwise it's shared with the Management Network, so go to this one, and
> than again click on "Storage" button again and make sure KVM traffic label
> is set to the correct name of the BRIDGE.
>
> as in images:
> https://pasteboard.co/HKHvTZF.png
> https://pasteboard.co/HKHuK5r.png
>
> KVM traffic labels = name of the physical interface on KVM host (usually
> name of the bridge) - so CloudStack will know to which bridge to join the
> SSVM vNIC...so SSVM can contact secondary storage...
>
>
>
>
> On Mon, 29 Oct 2018 at 14:44, Raymon van der Meijden <
> raymon@van-der-meijden.com> wrote:
>
>> Where did you find out these naming issues, so i can double check.
>> Because the places i have found look simular to me
>>
>>
>> On 29-10-18 14:37, Yordan Kostov wrote:
>>> Hello Raymon,
>>>
>>> I had the same issue (SSVMs booting but no OS existing).
>>> At the end I found out that this happened because my network
>> labels were not set correctly so the networks were not allocated properly
>> no proper connection to the secondary storage was available. This means
>> that the system creates the VM metdata (compute, ram, network interfaces)
>> but could not fetch the system disks from the secondary storage (so you see
>> the vms but they are actually empty).
>>> I hope that helps!
>>>
>>> Best regards,
>>> Jordan
>>>
>>> -----Original Message-----
>>> From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
>>> Sent: Monday, October 29, 2018 3:24 PM
>>> To: users@cloudstack.apache.org
>>> Subject: System Template not working on second Zone
>>>
>>>
>>> I`m running a cloudstack cluster for some time now and i`m getting the
>> hang of it. So i tried to add an additional Zone (Advanced) but i cannot
>> get the system VM to start. The VM`s are created and a running according to
>> cloudstack. But when i check the VM using VNC there is no OS available (
>> Bootdisk not found)
>>>
>>> I think the generation using the template is not working. But i cannot
>> figure out the issue. There is a secondary storage defined for this zone.
>> (And it seems to be working) And i have placed the template on that storage.
>>> The management log gives me debug logging, but i cannot find an issue.
>>>
>>>
>>> The creation of the systemtempate when mounted to the new secondary
>> storage.
>>> root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
>>>
>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>>> -m /mnt/tank/secondary -u
>>>
>> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
>>> -h kvm -F
>>> --2018-10-29 14:12:07--
>>>
>> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
>>> Resolving download.cloudstack.org (download.cloudstack.org)...
>>> 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
>>> Connecting to download.cloudstack.org
>>> (download.cloudstack.org)|185.27.174.49|:80... connected.
>>> HTTP request sent, awaiting response... 200 OK
>>> Length: 302864294 (289M) [application/x-bzip2] Saving to:
>>>
>> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>>>
>> 100%[================================================================================================================================>]
>>> 302,864,294 6.48MB/s in 47s
>>>
>>> 2018-10-29 14:12:54 (6.18 MB/s) -
>>>
>> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>>> saved [302864294/302864294]
>>>
>>> Uncompressing to
>>>
>> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
>>> (type bz2)...could take a long time
>>> Moving to
>>>
>> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
>>> take a while
>>> Successfully installed system VM template to
>> /mnt/tank/secondary/template/tmpl/1/224/
>>>
>>> But i think this should actually be /tmpl/10/224 since the id of the new
>> Zone is 10 (i have created and deleted some in the past)
>>>
>>>
>>>
>
Re: System Template not working on second Zone
Posted by Andrija Panic <an...@gmail.com>.
(after that, disable Zone, destroy SSVM/CPVM, enable Zone and they will be
recreated again...)
btw /template/1/224/ translates to
/template/Account_ID/template_ID/ (similar path is used for snapshots and
upoaded volumes) - so your path is OK - template/1 is system account,
while i.e. template/2 is the cloud admin account, and so on...
cheers
On Mon, 29 Oct 2018 at 14:51, Andrija Panic <an...@gmail.com> wrote:
> Go to Infrastructure --> Zones --> ZONE_NAME --> Physical Networks -->
> NAME_of_SECONDARY_STORAGE_NETWORK - if you used dedicated STORAGE network,
> otherwise it's shared with the Management Network, so go to this one, and
> than again click on "Storage" button again and make sure KVM traffic label
> is set to the correct name of the BRIDGE.
>
> as in images:
> https://pasteboard.co/HKHvTZF.png
> https://pasteboard.co/HKHuK5r.png
>
> KVM traffic labels = name of the physical interface on KVM host (usually
> name of the bridge) - so CloudStack will know to which bridge to join the
> SSVM vNIC...so SSVM can contact secondary storage...
>
>
>
>
> On Mon, 29 Oct 2018 at 14:44, Raymon van der Meijden <
> raymon@van-der-meijden.com> wrote:
>
>> Where did you find out these naming issues, so i can double check.
>> Because the places i have found look simular to me
>>
>>
>> On 29-10-18 14:37, Yordan Kostov wrote:
>> > Hello Raymon,
>> >
>> > I had the same issue (SSVMs booting but no OS existing).
>> > At the end I found out that this happened because my network
>> labels were not set correctly so the networks were not allocated properly
>> no proper connection to the secondary storage was available. This means
>> that the system creates the VM metdata (compute, ram, network interfaces)
>> but could not fetch the system disks from the secondary storage (so you see
>> the vms but they are actually empty).
>> >
>> > I hope that helps!
>> >
>> > Best regards,
>> > Jordan
>> >
>> > -----Original Message-----
>> > From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
>> > Sent: Monday, October 29, 2018 3:24 PM
>> > To: users@cloudstack.apache.org
>> > Subject: System Template not working on second Zone
>> >
>> >
>> > I`m running a cloudstack cluster for some time now and i`m getting the
>> hang of it. So i tried to add an additional Zone (Advanced) but i cannot
>> get the system VM to start. The VM`s are created and a running according to
>> cloudstack. But when i check the VM using VNC there is no OS available (
>> Bootdisk not found)
>> >
>> >
>> > I think the generation using the template is not working. But i cannot
>> figure out the issue. There is a secondary storage defined for this zone.
>> (And it seems to be working) And i have placed the template on that storage.
>> >
>> > The management log gives me debug logging, but i cannot find an issue.
>> >
>> >
>> > The creation of the systemtempate when mounted to the new secondary
>> storage.
>> >
>> > root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
>> >
>> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>> > -m /mnt/tank/secondary -u
>> >
>> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
>> > -h kvm -F
>> > --2018-10-29 14:12:07--
>> >
>> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
>> > Resolving download.cloudstack.org (download.cloudstack.org)...
>> > 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
>> > Connecting to download.cloudstack.org
>> > (download.cloudstack.org)|185.27.174.49|:80... connected.
>> > HTTP request sent, awaiting response... 200 OK
>> > Length: 302864294 (289M) [application/x-bzip2] Saving to:
>> >
>> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>> >
>> >
>> 100%[================================================================================================================================>]
>> > 302,864,294 6.48MB/s in 47s
>> >
>> > 2018-10-29 14:12:54 (6.18 MB/s) -
>> >
>> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>> > saved [302864294/302864294]
>> >
>> > Uncompressing to
>> >
>> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
>> > (type bz2)...could take a long time
>> > Moving to
>> >
>> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
>> > take a while
>> > Successfully installed system VM template to
>> /mnt/tank/secondary/template/tmpl/1/224/
>> >
>> >
>> > But i think this should actually be /tmpl/10/224 since the id of the
>> new Zone is 10 (i have created and deleted some in the past)
>> >
>> >
>> >
>> >
>>
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
Re: System Template not working on second Zone
Posted by Andrija Panic <an...@gmail.com>.
Go to Infrastructure --> Zones --> ZONE_NAME --> Physical Networks -->
NAME_of_SECONDARY_STORAGE_NETWORK - if you used dedicated STORAGE network,
otherwise it's shared with the Management Network, so go to this one, and
than again click on "Storage" button again and make sure KVM traffic label
is set to the correct name of the BRIDGE.
as in images:
https://pasteboard.co/HKHvTZF.png
https://pasteboard.co/HKHuK5r.png
KVM traffic labels = name of the physical interface on KVM host (usually
name of the bridge) - so CloudStack will know to which bridge to join the
SSVM vNIC...so SSVM can contact secondary storage...
On Mon, 29 Oct 2018 at 14:44, Raymon van der Meijden <
raymon@van-der-meijden.com> wrote:
> Where did you find out these naming issues, so i can double check.
> Because the places i have found look simular to me
>
>
> On 29-10-18 14:37, Yordan Kostov wrote:
> > Hello Raymon,
> >
> > I had the same issue (SSVMs booting but no OS existing).
> > At the end I found out that this happened because my network
> labels were not set correctly so the networks were not allocated properly
> no proper connection to the secondary storage was available. This means
> that the system creates the VM metdata (compute, ram, network interfaces)
> but could not fetch the system disks from the secondary storage (so you see
> the vms but they are actually empty).
> >
> > I hope that helps!
> >
> > Best regards,
> > Jordan
> >
> > -----Original Message-----
> > From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
> > Sent: Monday, October 29, 2018 3:24 PM
> > To: users@cloudstack.apache.org
> > Subject: System Template not working on second Zone
> >
> >
> > I`m running a cloudstack cluster for some time now and i`m getting the
> hang of it. So i tried to add an additional Zone (Advanced) but i cannot
> get the system VM to start. The VM`s are created and a running according to
> cloudstack. But when i check the VM using VNC there is no OS available (
> Bootdisk not found)
> >
> >
> > I think the generation using the template is not working. But i cannot
> figure out the issue. There is a secondary storage defined for this zone.
> (And it seems to be working) And i have placed the template on that storage.
> >
> > The management log gives me debug logging, but i cannot find an issue.
> >
> >
> > The creation of the systemtempate when mounted to the new secondary
> storage.
> >
> > root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
> >
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> > -m /mnt/tank/secondary -u
> >
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> > -h kvm -F
> > --2018-10-29 14:12:07--
> >
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> > Resolving download.cloudstack.org (download.cloudstack.org)...
> > 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
> > Connecting to download.cloudstack.org
> > (download.cloudstack.org)|185.27.174.49|:80... connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 302864294 (289M) [application/x-bzip2] Saving to:
> >
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> >
> >
> 100%[================================================================================================================================>]
> > 302,864,294 6.48MB/s in 47s
> >
> > 2018-10-29 14:12:54 (6.18 MB/s) -
> >
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> > saved [302864294/302864294]
> >
> > Uncompressing to
> >
> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
> > (type bz2)...could take a long time
> > Moving to
> >
> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
> > take a while
> > Successfully installed system VM template to
> /mnt/tank/secondary/template/tmpl/1/224/
> >
> >
> > But i think this should actually be /tmpl/10/224 since the id of the new
> Zone is 10 (i have created and deleted some in the past)
> >
> >
> >
> >
>
--
Andrija Panić
Re: System Template not working on second Zone
Posted by Raymon van der Meijden <ra...@van-der-meijden.com>.
Where did you find out these naming issues, so i can double check.
Because the places i have found look simular to me
On 29-10-18 14:37, Yordan Kostov wrote:
> Hello Raymon,
>
> I had the same issue (SSVMs booting but no OS existing).
> At the end I found out that this happened because my network labels were not set correctly so the networks were not allocated properly no proper connection to the secondary storage was available. This means that the system creates the VM metdata (compute, ram, network interfaces) but could not fetch the system disks from the secondary storage (so you see the vms but they are actually empty).
>
> I hope that helps!
>
> Best regards,
> Jordan
>
> -----Original Message-----
> From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
> Sent: Monday, October 29, 2018 3:24 PM
> To: users@cloudstack.apache.org
> Subject: System Template not working on second Zone
>
>
> I`m running a cloudstack cluster for some time now and i`m getting the hang of it. So i tried to add an additional Zone (Advanced) but i cannot get the system VM to start. The VM`s are created and a running according to cloudstack. But when i check the VM using VNC there is no OS available ( Bootdisk not found)
>
>
> I think the generation using the template is not working. But i cannot figure out the issue. There is a secondary storage defined for this zone. (And it seems to be working) And i have placed the template on that storage.
>
> The management log gives me debug logging, but i cannot find an issue.
>
>
> The creation of the systemtempate when mounted to the new secondary storage.
>
> root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
> -m /mnt/tank/secondary -u
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> -h kvm -F
> --2018-10-29 14:12:07--
> http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
> Resolving download.cloudstack.org (download.cloudstack.org)...
> 185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
> Connecting to download.cloudstack.org
> (download.cloudstack.org)|185.27.174.49|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 302864294 (289M) [application/x-bzip2] Saving to:
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
>
> 100%[================================================================================================================================>]
> 302,864,294 6.48MB/s in 47s
>
> 2018-10-29 14:12:54 (6.18 MB/s) -
> '/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
> saved [302864294/302864294]
>
> Uncompressing to
> /usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
> (type bz2)...could take a long time
> Moving to
> /mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
> take a while
> Successfully installed system VM template to /mnt/tank/secondary/template/tmpl/1/224/
>
>
> But i think this should actually be /tmpl/10/224 since the id of the new Zone is 10 (i have created and deleted some in the past)
>
>
>
>
RE: System Template not working on second Zone
Posted by Yordan Kostov <Yo...@worldsupport.info>.
Hello Raymon,
I had the same issue (SSVMs booting but no OS existing).
At the end I found out that this happened because my network labels were not set correctly so the networks were not allocated properly no proper connection to the secondary storage was available. This means that the system creates the VM metdata (compute, ram, network interfaces) but could not fetch the system disks from the secondary storage (so you see the vms but they are actually empty).
I hope that helps!
Best regards,
Jordan
-----Original Message-----
From: Raymon van der Meijden [mailto:raymon@van-der-meijden.com]
Sent: Monday, October 29, 2018 3:24 PM
To: users@cloudstack.apache.org
Subject: System Template not working on second Zone
I`m running a cloudstack cluster for some time now and i`m getting the hang of it. So i tried to add an additional Zone (Advanced) but i cannot get the system VM to start. The VM`s are created and a running according to cloudstack. But when i check the VM using VNC there is no OS available ( Bootdisk not found)
I think the generation using the template is not working. But i cannot figure out the issue. There is a secondary storage defined for this zone. (And it seems to be working) And i have placed the template on that storage.
The management log gives me debug logging, but i cannot find an issue.
The creation of the systemtempate when mounted to the new secondary storage.
root@cloud:/mnt/tank/secondary/template/tmpl/1/222#
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/tank/secondary -u
http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
-h kvm -F
--2018-10-29 14:12:07--
http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
Resolving download.cloudstack.org (download.cloudstack.org)...
185.27.174.49, 2a00:f10:121:400:403:9cff:fe00:37f
Connecting to download.cloudstack.org
(download.cloudstack.org)|185.27.174.49|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 302864294 (289M) [application/x-bzip2] Saving to:
'/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
100%[================================================================================================================================>]
302,864,294 6.48MB/s in 47s
2018-10-29 14:12:54 (6.18 MB/s) -
'/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2'
saved [302864294/302864294]
Uncompressing to
/usr/share/cloudstack-common/scripts/storage/secondary/4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2.tmp
(type bz2)...could take a long time
Moving to
/mnt/tank/secondary/template/tmpl/1/224///4edec9f7-b516-4bcc-adf8-27d61e01a3d7.qcow2...could
take a while
Successfully installed system VM template to /mnt/tank/secondary/template/tmpl/1/224/
But i think this should actually be /tmpl/10/224 since the id of the new Zone is 10 (i have created and deleted some in the past)