On Tue, Feb 26, 2013 at 08:34:08PM -0600, Doug Goldstein wrote:
> On Sat, Feb 23, 2013 at 11:43 PM, Marwan Tanager
> wrote:
> > I used to run many VMs on my Ubuntu 10.04 box. However, after upgrading to
> > Ubuntu 12.10 (and thus, libvirt 0.9.13), The VMs can't be
I used to run many VMs on my Ubuntu 10.04 box. However, after upgrading to
Ubuntu 12.10 (and thus, libvirt 0.9.13), The VMs can't be recognized anymore.
Nothing appears in the output of 'virsh list --all', nor in virt-manager.
When I created a new VM based on a disk image of one of the
not-rec
On Mon, Nov 19, 2012 at 08:35:18AM -0500, Rudy Godoy wrote:
> On Mon, Nov 19, 2012 at 12:09:53PM +0530, mallapadi niranjan wrote:
> > Hi all,
> >
> > I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding
> > networking between them. The 2 RHEL4 system's use default bridge virbr0 and
On Mon, Nov 19, 2012 at 12:09:53PM +0530, mallapadi niranjan wrote:
> Hi all,
>
> I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding
> networking between them. The 2 RHEL4 system's use default bridge virbr0 and
> get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.1
On Thu, Sep 27, 2012 at 03:24:17AM -0400, Alex Jia wrote:
> Hi Marwan,
> I remember libvirt has a similar bug, but I forgot bug number, Laine can help
> confirm this, could you provide your libvirt version? thanks.
I am using libvirt 0.7.5. I know it's fairly outdated by now, but this may
still
Hi everyone.
Those are the iptables forwarding rules associated with the two virtual
networks
on my machine:
-
-A FORWARD -d 192.168.100.0/24 -o virbr1 -m state --state RELATED,ESTABLISHED
-j ACCEPT
-A FORW
On Thu, Sep 13, 2012 at 04:14:30PM +0800, Osier Yang wrote:
>
> Okay, finally I understood, that's because the default network use
> "nat" forward mode, and dnsmasq is the only one supported DHCP
> server libvirt supports for DHCPv4.
>
> If you want to use the default NAT network, but to use your
On Thu, Sep 13, 2012 at 03:54:30PM +0800, Osier Yang wrote:
> On 2012年09月13日 15:50, Marwan Tanager wrote:
> >On Thu, Sep 13, 2012 at 03:17:14PM +0800, Osier Yang wrote:
> >>On 2012年09月13日 14:55, Marwan Tanager wrote:
> >>>On Thu, Sep 13, 2012 at 01:04:58PM +0800, Osie
On Thu, Sep 13, 2012 at 03:17:14PM +0800, Osier Yang wrote:
> On 2012年09月13日 14:55, Marwan Tanager wrote:
> >On Thu, Sep 13, 2012 at 01:04:58PM +0800, Osier Yang wrote:
> >>On 2012年09月13日 11:23, Marwan Tanager wrote:
> >>
> >>No, to disable the autostarting
On Thu, Sep 13, 2012 at 01:04:58PM +0800, Osier Yang wrote:
> On 2012年09月13日 11:23, Marwan Tanager wrote:
>
> No, to disable the autostarting of dnsmasq, you need to disable the
> autostart of network which drives dnsmasq (named 'default' by default).
>
> % virsh net
Hi.
I have a machine with a local DHCP server and a couple of virtual networks and
I've configured the server for each virtual interface, so that I would be able
to install VMs on the corresponding subnets using PXE.
The problem is that the two DHCP servers (my local server and dnsmasq) are
co
11 matches
Mail list logo