* "set_link" monitor command
@ 2009-07-15 23:30 Michael Jinks
2009-07-16 0:03 ` Michael Jinks
2009-07-16 5:38 ` Yaniv Kaul
0 siblings, 2 replies; 3+ messages in thread
From: Michael Jinks @ 2009-07-15 23:30 UTC (permalink / raw)
To: kvm
Like I said in my other network puzzlement thread, I have one KVM
guest which is working fine. Or, it was until I tried to add a second
one, and hosed my virtual bridge.
The guest is still running, but since I restarted the bridge interface
that its NIC was attached to, it's no longer attached. I thought that
maybe bringing its network interface down and back up again might
re-attach it to the bridge. (Was I wrong? Is there some other way to
change the network connections for a running guest?)
I found the "set_link" monitor command, but I can't figure out what
the link name should be. I've tried:
(qemu) set_link eth0 up
could not find network device 'eth0'(qemu)
(qemu) set_link tap0 up
could not find network device 'tap0'(qemu)
?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: "set_link" monitor command
2009-07-15 23:30 "set_link" monitor command Michael Jinks
@ 2009-07-16 0:03 ` Michael Jinks
2009-07-16 5:38 ` Yaniv Kaul
1 sibling, 0 replies; 3+ messages in thread
From: Michael Jinks @ 2009-07-16 0:03 UTC (permalink / raw)
To: kvm
Another monitor command question: trying to rescue my de-networked
guest, I thought I'd try connecting to the console, but in its
monitor:
(qemu) info vnc
Server: disabled
According to the command line where I started this kvm instance, vnc
should be enabled. Maybe it died? Is there a way to turn it back on
again from the monitor? I've looked but I can't find anything...
On Wed, Jul 15, 2009 at 6:30 PM, Michael Jinks<michael.jinks@gmail.com> wrote:
> Like I said in my other network puzzlement thread, I have one KVM
> guest which is working fine. Or, it was until I tried to add a second
> one, and hosed my virtual bridge.
>
> The guest is still running, but since I restarted the bridge interface
> that its NIC was attached to, it's no longer attached. I thought that
> maybe bringing its network interface down and back up again might
> re-attach it to the bridge. (Was I wrong? Is there some other way to
> change the network connections for a running guest?)
>
> I found the "set_link" monitor command, but I can't figure out what
> the link name should be. I've tried:
>
> (qemu) set_link eth0 up
> could not find network device 'eth0'(qemu)
> (qemu) set_link tap0 up
> could not find network device 'tap0'(qemu)
>
> ?
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: "set_link" monitor command
2009-07-15 23:30 "set_link" monitor command Michael Jinks
2009-07-16 0:03 ` Michael Jinks
@ 2009-07-16 5:38 ` Yaniv Kaul
1 sibling, 0 replies; 3+ messages in thread
From: Yaniv Kaul @ 2009-07-16 5:38 UTC (permalink / raw)
To: Michael Jinks; +Cc: kvm
On 7/16/2009 2:30 AM, Michael Jinks wrote:
> Like I said in my other network puzzlement thread, I have one KVM
> guest which is working fine. Or, it was until I tried to add a second
> one, and hosed my virtual bridge.
>
> The guest is still running, but since I restarted the bridge interface
> that its NIC was attached to, it's no longer attached. I thought that
> maybe bringing its network interface down and back up again might
> re-attach it to the bridge. (Was I wrong? Is there some other way to
> change the network connections for a running guest?)
>
> I found the "set_link" monitor command, but I can't figure out what
> the link name should be. I've tried:
>
> (qemu) set_link eth0 up
> could not find network device 'eth0'(qemu)
> (qemu) set_link tap0 up
> could not find network device 'tap0'(qemu)
>
Try 'info network'
Y.
> ?
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-07-16 5:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-15 23:30 "set_link" monitor command Michael Jinks
2009-07-16 0:03 ` Michael Jinks
2009-07-16 5:38 ` Yaniv Kaul
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).