xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Fajar A. Nugraha" <fajar@fajar.net>
To: xen-devel@lists.xensource.com
Subject: How to force destroy a vif not connected to any domUs?
Date: Mon, 21 Jun 2010 17:56:15 +0700	[thread overview]
Message-ID: <AANLkTine2Jvei5EhYVdVF1phEkPMHujgLo3f6unsN0ac@mail.gmail.com> (raw)

I'm testing latest SLE11-SP1 kernel from kotd
(2.6.32.13-0.0.0.43.aa5bdc6, built from source). While creating a
domU, I messed up "root" setting on grub command line, so that the
domU exits with

#===================
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
ERROR opening /dev/console: No such file or directory
Trying to use fd 0 instead.
WARNING: can't access (null)
exec of init ((null)) failed!!!: Bad address
Kernel panic - not syncing: Attempted to kill init!
#===================


Okay, fair enough. The problem is that even though the domU is dead,
it's vif remains. And since I assign unique name to each vif, I can't
start the domU again (since an interface with that name already
exists).

The question is, is there a way to FORCE destroy this interface? With
blktap2 I can issue something like

echo 1 > /sys/class/blktap2/blktap3/remove

Is there something similar for vif?

-- 
Fajar

                 reply	other threads:[~2010-06-21 10:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTine2Jvei5EhYVdVF1phEkPMHujgLo3f6unsN0ac@mail.gmail.com \
    --to=fajar@fajar.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).