From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yaniv Kaul Subject: Re: "set_link" monitor command Date: Thu, 16 Jul 2009 08:38:05 +0300 Message-ID: <4A5EBCBD.9070106@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Michael Jinks Return-path: Received: from mx2.redhat.com ([66.187.237.31]:37648 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757471AbZGPFiI (ORCPT ); Thu, 16 Jul 2009 01:38:08 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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 >