You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/02/26 13:12:12 UTC

[jira] [Comment Edited] (CLOUDSTACK-1264) System VM does not have default route.

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587060#comment-13587060 ] 

Abhinandan Prateek edited comment on CLOUDSTACK-1264 at 2/26/13 12:10 PM:
--------------------------------------------------------------------------

Xen system VM are programmed with right default route. 

Parth,

Can you be more specific on what Hypervisor it did not work ? 
                
      was (Author: aprateek):
    Xen system VM are programmed with right default route. 

Can you be more specific on what Hypervisor it did not work ? 
                  
> System VM does not have default route.
> --------------------------------------
>
>                 Key: CLOUDSTACK-1264
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1264
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup, Network Devices, XenServer
>    Affects Versions: 4.1.0
>         Environment: Build #15, rhel 6.3
>            Reporter: Parth Jagirdar
>            Assignee: Jayapal Reddy
>            Priority: Blocker
>
> While troubleshooting it was found that System VM doesnt have default route.
> Management sever logs that contains n/w info are attached. Which shows that N/W info including G/W being passed. (May be the script on VM failed to configure?) 
> Other Hypervisor (VMWARE) didnt have this issue.
> This was confirmed on the setup mentioned in bug #1252. We were able to ping external world.
> https://issues.apache.org/jira/browse/CLOUDSTACK-1252
> Please contact if more info is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira