I installed Ubuntu Feisty successfully, then I configured the network (static IP) and things worked well. Then I installed Xen using "apt-get install ubuntu-xen-desktop". I could boot the xen kernel, and booted succesfully to dom0, however, there''s no network for dom0. According to network manager, I saw that Ubuntu recognizes now 4 unconfigured adapters (veth0, veth1, veth2, veth3). I''m not sure how I need to configure them to: 1> have network for dom0 2> later, have network for other domains Thanks, Dror _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
---------- Forwarded message ---------- From: dror shenkar <dror.shenkar@gmail.com> Date: May 13, 2007 10:39 PM Subject: no network for dom0 To: xen-users@lists.xensource.com I installed Ubuntu Feisty successfully, then I configured the network (static IP) and things worked well. Then I installed Xen using "apt-get install ubuntu-xen-desktop". I could boot the xen kernel, and booted succesfully to dom0, however, there''s no network for dom0. According to network manager, I saw that Ubuntu recognizes now 4 unconfigured adapters (veth0, veth1, veth2, veth3). I''m not sure how I need to configure them to: 1> have network for dom0 2> later, have network for other domains Thanks, Dror _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > dror shenkar > Sent: 15 May 2007 10:59 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Fwd: no network for dom0 > > > > ---------- Forwarded message ---------- > From: dror shenkar <dror.shenkar@gmail.com> > Date: May 13, 2007 10:39 PM > Subject: no network for dom0 > To: xen-users@lists.xensource.com > > > I installed Ubuntu Feisty successfully, then I configured the > network (static IP) and things worked well. > Then I installed Xen using "apt-get install ubuntu-xen-desktop". > I could boot the xen kernel, and booted succesfully to dom0, > however, there''s no network for dom0. > According to network manager, I saw that Ubuntu recognizes > now 4 unconfigured adapters (veth0, veth1, veth2, veth3). > I''m not sure how I need to configure them to: > 1> have network for dom0It''s probably because your network setup script is using "eth0" rather than the xen new-name of "peth0" (as in "physical eth0"). I can''t guarantee this, but I suspect that''s what it is. [It depends on the startup-sequence between Xen and IP address setup if this is the case or not].> 2> later, have network for other domainsThat is a different problem, and it depends on how you want to set up your guest network. If you have a range of IP-addresses, you could set Dom0 to use "dhcp" to issue addresses to your guest-domains, or you can set them to static addresses there too. For para-virtual domains, you do this by adding "ip=x.y.z.w" to your "vif=..." line in the configuration. For HVM (fully-virtualized domains), you will need to use the same type of setup that you''d do if you have a "real" machine - this depends on which OS you''re using, but just follow the normal setup for IP-addresses on the OS itself. [e.g. use Windows Control panel, or SuSE "Yast2" to set the network up within the guest itself]. -- Mats> > Thanks, Dror >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Question, If you have a 64-Bit host running Xen will the guest''s be 64-bit as well? ______________________________________________________________________ Lewis Donofrio@umich.edu Cell: (734) 323-8776 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Donofrio, Lewis > Sent: 15 May 2007 13:33 > To: xen-users@lists.xensource.com > Subject: [Xen-users] 64-Bit Xen? > > Question, > > If you have a 64-Bit host running Xen will the guest''s be 64-bit as > well?Depends on several things. But first, lets just quickly recap the modes that exist biggest to smallest: 64-bit - supports HUGE memory addresses (physical memory up to 40 bits (1024 GB = 1TB), virtual memory to 48 bits (256 TB), with future extension up to, I think, 53 bits if necessary). 32-bit PAE - supports 32-bit (4GB) virtual address, but up to 36 bits (64GB) of physical memory [although Xen limits this to 34 bits/16GB]. 32-bit non-PAE - 32-bit virtual, 32-bit physical address. So now to what''s supported: HVM (Fully virtualized guest) can be anything up to the same as the hypervisor, so a 64-bit hypervisor supports all of the above modes, whilst a 32-bit PAE can''t use 64-bit, and a 32-bit non-PAE can''t do anything but 32-bit non-PAE guests. Para-virtual guest have traditionally had the requitement of being identical to the hypervisor. With the upcomming release of 3.1.0 of Xen, this will be reduced somewhat by allowing 32-bit PAE guests on top of 64-bit hypervisor. With this version, it''s still not possible to run 32-bit non-PAE on a 64-bit hypervisor. -- Mats> ______________________________________________________________________ > Lewis Donofrio@umich.edu > Cell: (734) 323-8776 > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 15 May 2007, Petersson, Mats wrote:> > If you have a 64-Bit host running Xen will the guest''s be 64-bit as > > well? > > Depends on several things. But first, lets just quickly recap the modes > that exist biggest to smallest:i''d summarise as follows (Dom0 / DomU): HVM: 64bit / 64bit : ok 64bit / PAE : ok 64bit / 32bit : ok PAE / 64bit : can''t PAE / PAE : ok PAE / 32bit : ok 32bit / 64bit : can''t 32bit / PAE : can''t 32bit / 32bit : ok PV: 64bit / 64bit : ok 64bit / PAE : ok with Xen 3.1 64bit / 32bit : can''t PAE / 64bit : can''t PAE / PAE : ok PAE / 32bit : can''t 32bit / 64bit : can''t 32bit / PAE : can''t 32bit / 32bit : ok or, even shorter: "in HVM, DomU <= Dom0; in PV, DomU == Dom0" (except for 64bit/PAE in 3.1) (i''m not so sure about PAE/32bit on PV, doesn''t sound soo hard.. but what do i know?) -- Javier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> (i''m not so sure about PAE/32bit on PV, doesn''t sound soo > hard.. but what do i know?)It''s not hard as a concept, the only major problem is that the page-tables in PAE is completely different from non-PAE page-tables. This means that the hypervisor would have to use shadow-paging, which isn''t something that is available at the moment. It may be a possibility for the future tho''. -- Mats> > -- > Javier >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- bridge vs macvlan performance (was: some veth related issues)
- bridge vs macvlan performance (was: some veth related issues)
- VM boots BUT keep throwing: "INIT: Id "X" respawning too fast: disabled for 5 minutes"
- problem for add second bridge xenbr1
- Gutsy Xen 3.1 2.6.22-9-xen network-bridge problem