[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] guest creation problem on pv dom0 kernel


  • To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
  • Date: Thu, 10 Mar 2011 11:06:04 +0530
  • Delivery-date: Wed, 09 Mar 2011 21:37:08 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=O2Cp5DyQS3e5Neyr3mvlixLdlTDPU99iIMm8cTwZwQjvyE325W6StCbcmE//H1N+AR 8S8NRRgYd/+7ojzsFNC2aj96Xpv1QmRPWdqEgkgObemKBjn8rUS+rEvyCIN8vLogutZW aOIvkox7vTZ6bA0XPmJpHrZSIQICLx0wWHKjE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Mar 10, 2011 at 3:56 AM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> On Thu, Mar 10, 2011 at 3:26 AM, Tapas Mishra <mightydreams@xxxxxxxxx> wrote:
>> here is my /etc/xen/ubuntu.vm
>>
>>
>> ===============================================
>> memory = "512"
>> vif = [ 'mac=00:16:3E:BD:96:42, bridge=xenbr0, vifname=u-e0' ]
>
> Back to the basics. Xen has two basic networking methods, the default
> being bridge. You may have a bridge called "eth0" or "eth1" (depending
> on what interface you currently use) created by Xen during its startup
> phase (the original eth0 and eth1 is renamed to peth0 and peth1).

Actually  I have read it in Xen books and even on Xen networking wiki
the same thing that you mentioned.
That original eth0 and eth1 are renamed to peth0 and peth1 but
practically I never found this happening never.

I had tried this in Xen 3.*  a long time back on Ubuntu 9.04 and now I
am trying on 10.04 but any time this never happened.

>If
> you have virt-manager installed then you should already have a bridge
> called virbr0.

Ok I do have a bridge name virbr0.

> If you have no idea what I'm talking about just remove the
> "bridge=xenbr0," section.
After reading your message here I did that
so now my line looks as
vif = [ 'mac=00:16:3E:BD:96:42,vifname=u-e0' ]

if this is what you meant.

>
>> dhcp ="off"
>> ip="192.168.1.7"
>> netmask="255.255.255.0"
>> gateway="192.168.1.1"
>> hostname="vm01.ubuntu"
>
> Those entries will be useless by default in bridge setup. DomU will be
> on the same network as dom0, and you need to setup networking from
> inside domU (e.g. setup DHCP or static IP)
Ok this makes it clear.
>> ===============================================
>> Now when I do
>> xm create -c /etc/xen/ubuntu.vm
>> Two things
>>
>> 1) Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
>
> Cause you're not listening. I specifically said
>
> "
> Note the "bridge" parameter. It might be eth0, xenbr0, or some other
> bridge that you create manually (try runnning "brctl show").


Since my wifi does not work when I boot with xen.gz and pv-ops dom0
combination so I switch to a
the kernel which was installed along with Ubuntu installation for all
work purposes
and brctl show


bridge name     bridge id               STP enabled     interfaces

pan0            8000.000000000000       no              
virbr0          8000.000000000000       yes     

but I for the sake of using Xen I  reboot to pv-ops Dom0 kernel in
combination with xen.gz (which is where I am trying every thing)
and here brctl show

bridge name     bridge id               STP enabled     interfaces
pan0            8000.000000000000       no
tmpbridge               8000.000000000000       no
virbr0          8000.000000000000       yes


but this time I had removed the bridge=xenbr0 parameter and I get the same error

Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

when I do a xm create -c /etc/xen/ubuntu.vm
--

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.