All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uqbar <1659267@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1659267] [NEW] It's not possible to start a VM with a network cable unplugged
Date: Wed, 25 Jan 2017 11:37:30 -0000	[thread overview]
Message-ID: <20170125113730.12494.46970.malonedeb@gac.canonical.com> (raw)

Public bug reported:

There should be a command line (sub)option to unplug a network cable.
While from the monitor interface I can issue:

set_link virtio-net-pci.0 off

There's no way to fire a VM from command line with that cable already unplugged.
As an example, virtualbox can do it.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1659267

Title:
  It's not possible to start a VM with a network cable unplugged

Status in QEMU:
  New

Bug description:
  There should be a command line (sub)option to unplug a network cable.
  While from the monitor interface I can issue:

  set_link virtio-net-pci.0 off

  There's no way to fire a VM from command line with that cable already unplugged.
  As an example, virtualbox can do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1659267/+subscriptions

             reply	other threads:[~2017-01-25 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 11:37 Uqbar [this message]
2020-01-23  6:04 ` [Bug 1659267] Re: It's not possible to start a VM with a network cable unplugged Thomas Huth
2020-06-06 11:24 ` timsoft
2020-06-08  9:21 ` Daniel Berrange
2021-04-22  4:06 ` Thomas Huth
2021-06-21  4:17 ` Launchpad Bug Tracker

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=20170125113730.12494.46970.malonedeb@gac.canonical.com \
    --to=1659267@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.