Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Aug 2012 12:42:45 GMT
From:      Mark Felder <feld@feld.me>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/171138: [panic] Deactivating network interface produces panic on XENHVM
Message-ID:  <201208281242.q7SCgjja067770@red.freebsd.org>
Resent-Message-ID: <201208281250.q7SCo1la076926@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         171138
>Category:       misc
>Synopsis:       [panic] Deactivating network interface produces panic on XENHVM
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 28 12:50:01 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Mark Felder
>Release:        FreeBSD 9.0-RELEASE
>Organization:
>Environment:
>Description:
Using XenCenter on both XCP and XenServer hypervisors you can choose to deactivate (simulate unplugged interface) any interface assigned to a VM. On Linux VMs this seems to work without issue. The option to Deactivate an interface is not available unless the FreeBSD XENHVM server is also reporting network interface data to the hypervisor with the following scripts (which require sysutils/xen-tools)

https://github.com/felderado/freebsd-xen-tools-scripts
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208281242.q7SCgjja067770>