From: Daniel Berrange <1659267@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1659267] Re: It's not possible to start a VM with a network cable unplugged
Date: Mon, 08 Jun 2020 09:21:53 -0000 [thread overview]
Message-ID: <159160811377.31406.15781999925012732811.malone@gac.canonical.com> (raw)
In-Reply-To: 20170125113730.12494.46970.malonedeb@gac.canonical.com
Note that you can start QEMU with the "-S" flag which means CPUS are
paused. This gives you ability to run the "set_link" monitor command
above, and then run "cont" to actually start the VM. Less convenient
that a CLI flag, but functionally it is eqivalent.
--
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
next prev parent reply other threads:[~2020-06-08 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 11:37 [Qemu-devel] [Bug 1659267] [NEW] It's not possible to start a VM with a network cable unplugged Uqbar
2020-01-23 6:04 ` [Bug 1659267] " Thomas Huth
2020-06-06 11:24 ` timsoft
2020-06-08 9:21 ` Daniel Berrange [this message]
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=159160811377.31406.15781999925012732811.malone@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.