[Fedora-xen] Fedora 7 - missing dummy interfaces

[Per Hjartoy]

Is "test_vm" your guest?  If not, that is what you need to use as an
argument to virsh and not the Domain-0 (vm container).  --  Per

-----Original Message-----
From: David Mueller [mailto:dsm717 at gmail.com] 
Sent: Wednesday, August 22, 2007 2:03 PM
To: Per Hjartoy
Cc: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] Fedora 7 - missing dummy interfaces

Per,

Ok.  I was hoping there was something realatively straightforward to change.

I've also been working on a new approach to use KVM with Fedora 7.
I've been able to use Revisor to create a custom Install CD image and
used that with virt-manager to create a virtual machine.  However,
I've run into a wall with virt-manager's insistance on using only
private IP address space.  Your suggestion to dump the result to xml
and modify that seems like it might work, except I can't get virsh to
work:

# virsh dumpxml test_vm
error: failed to connect to the hypervisor
error: no valid connection

Where test_vm is the name of my virtual machine in the Name column of
the virt-manager GUI.  It doesn't make a difference whether or not the
virtual machine is running at the time.

- David

On 8/22/07, Per Hjartoy <per at actius.com> wrote:
> David, The configuration has changed quite a bit between F5 and F7.  I've
> found that there is not much you can do unless you go "virsh dumpxml ...".
> In my experimentation, I made the most progress when I defined the device
> with dummy data in the GUI version. I could then dump the result out and
> make changes in the xml template I got. Finally I would reload by "virsh
> define ...". Hope this helps. -- Per
>
> -----Original Message-----
> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com]
> On Behalf Of David Mueller
> Sent: Tuesday, August 21, 2007 10:07 AM
> To: fedora-xen at redhat.com
> Subject: [Fedora-xen] Fedora 7 - missing dummy interfaces
>
> I'm trying to move from Fedora Core 5 to Fedora 7.  I've run into an
> issue where the xen guests, which need several bridged interfaces
> bound to dummy devices so they can communicate with each other
> (similar to host-only networking with VMWare), won't boot.  I think
> I've traced the problem to a lack of the dummy1, dummy2, and dummy3
> devices, and I'm not sure how to fix it.  What I'll describe below is
> the setup that worked in Fedora Core 5:
>
> I used the following custom network-bridge script:
>
> #!/bin/sh
> dir=$(dirname "$0")
> "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0
> "$dir/network-bridge" "$@" vifnum=1 netdev=dummy1
> "$dir/network-bridge" "$@" vifnum=2 netdev=dummy2
> "$dir/network-bridge" "$@" vifnum=3 netdev=dummy3
>
> And the following line was used in the .xen files passed to xm create:
>
> vif = ['mac=2E:22:22:22:22:20,bridge=xenbr1',
> 'mac=2E:22:22:22:22:21,bridge=xenbr2',
> 'mac=2E:22:22:22:22:22,bridge=xenbr3']
>
> Running the script resulted in the following:
>
> Using config file "./guest1.xen".
> Error: Device 0 (vif) could not be connected. Could not find bridge
> device xenbr1
>
> If I try to run the custom network-bridge script manually passing the
> "start" command I get several errors:
>
> Device "dummy1" does not exist.
> usage: ifdown <device name>
> Device "dummy1" does not exist.
> Cannot find device "dummy1"
> SIOCGIFFLAGS: No such device
> Device "dummy2" does not exist.
> usage: ifdown <device name>
> Device "dummy2" does not exist.
> Cannot find device "dummy2"
> SIOCGIFFLAGS: No such device
> Device "dummy3" does not exist.
> usage: ifdown <device name>
> Device "dummy3" does not exist.
> Cannot find device "dummy3"
> SIOCGIFFLAGS: No such device
>
> Any ideas on how to get this working would be greatly appreciated.
>
> - David
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>