Hi, all: I am using Ubuntu 12.04, 64bit. compiled Linux kernel from source, kernel is 3.3.6. Compiled Xen from source, version is 4.1.2. so far so good. Dom0 can boot without problem. Dom0 has network. However, when I downloaded the vmlinuz and initrd.img for centos 6.2 and try to install it, I first picked network install, then it asked me to pick network, I choose DHCP for both iipv4 and ipv6. After that, it stops at "Waiting for NetworkManager to configure eth0." "Retry". From the notification area, I can see that a vif2.0 has been created. I disabled the firewall, and ubuntu seems don''t have selinux problem. could someone help me with this? Thanks in advance. "xl info" gives: host : xisisu-desktop release : 3.3.6 version : #1 SMP Sun May 13 18:24:00 CDT 2012 machine : x86_64 nr_cpus : 12 nr_nodes : 1 cores_per_socket : 6 threads_per_core : 2 cpu_mhz : 3378 hw_caps : bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 12277 free_memory : 1094 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) cc_compile_by : xisisu cc_compile_domain : cc_compile_date : Sun May 13 17:46:53 CDT 2012 xend_config_format : 4 Here is the install configure file: "name="centosinstall" vcpus=2 memory=2048 disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] vif=[''bridge=eth0''] kernel="/home/xisisu/Desktop/vmlinuz" ramdisk="/home/xisisu/Desktop/initrd.img" on_reboot=''restart'' on_crash=''restart'' _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Casey DeLorme
2012-May-14 05:36 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
Hello, Guessing eth0 isn''t a bridge, have you tried creating a bridge and using that instead? bridge-utils package installed and add to /etc/networking/interfaces: auto xenbr0 iface xenbr0 inet manual bridge_ports eth0 Then replace eth0 in the centos HVM configuration? On Mon, May 14, 2012 at 1:25 AM, Sisu Xi <xisisu@gmail.com> wrote:> Hi, all: > > I am using Ubuntu 12.04, 64bit. compiled Linux kernel from source, kernel > is 3.3.6. Compiled Xen from source, version is 4.1.2. > > so far so good. > Dom0 can boot without problem. Dom0 has network. > > However, when I downloaded the vmlinuz and initrd.img for centos 6.2 and > try to install it, > I first picked network install, then it asked me to pick network, I choose > DHCP for both iipv4 and ipv6. > After that, it stops at > "Waiting for NetworkManager to configure eth0." > "Retry". > > From the notification area, I can see that a vif2.0 has been created. > > I disabled the firewall, and ubuntu seems don''t have selinux problem. > could someone help me with this? > > Thanks in advance. > > "xl info" gives: > host : xisisu-desktop > release : 3.3.6 > version : #1 SMP Sun May 13 18:24:00 CDT 2012 > machine : x86_64 > nr_cpus : 12 > nr_nodes : 1 > cores_per_socket : 6 > threads_per_core : 2 > cpu_mhz : 3378 > hw_caps : > bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 12277 > free_memory : 1094 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : > cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) > cc_compile_by : xisisu > cc_compile_domain : > cc_compile_date : Sun May 13 17:46:53 CDT 2012 > xend_config_format : 4 > > > Here is the install configure file: > > "name="centosinstall" > vcpus=2 > memory=2048 > disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] > vif=[''bridge=eth0''] > kernel="/home/xisisu/Desktop/vmlinuz" > ramdisk="/home/xisisu/Desktop/initrd.img" > on_reboot=''restart'' > on_crash=''restart'' > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Sisu Xi
2012-May-14 05:53 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
Hi, Casey: Thanks for your reply. Could you be a little more specific? I checked my /etc/networking/interfaces, it is: auto lo iface lo inet loopback. I changed it to what you suggested: auto xenbr0 iface xenbr0 inet manual bridge_ports eth0 This time Dom0 has no network. I also tried: auto xenbr0 iface xenbr0 inet dhcp bridge_ports eth0 Dom0 also has no network. Thanks! On Mon, May 14, 2012 at 12:36 AM, Casey DeLorme <cdelorme@gmail.com> wrote:> Hello, > > Guessing eth0 isn''t a bridge, have you tried creating a bridge and using > that instead? > > bridge-utils package installed and add to /etc/networking/interfaces: > > auto xenbr0 > iface xenbr0 inet manual > bridge_ports eth0 > > Then replace eth0 in the centos HVM configuration? > > > On Mon, May 14, 2012 at 1:25 AM, Sisu Xi <xisisu@gmail.com> wrote: > >> Hi, all: >> >> I am using Ubuntu 12.04, 64bit. compiled Linux kernel from source, kernel >> is 3.3.6. Compiled Xen from source, version is 4.1.2. >> >> so far so good. >> Dom0 can boot without problem. Dom0 has network. >> >> However, when I downloaded the vmlinuz and initrd.img for centos 6.2 and >> try to install it, >> I first picked network install, then it asked me to pick network, I >> choose DHCP for both iipv4 and ipv6. >> After that, it stops at >> "Waiting for NetworkManager to configure eth0." >> "Retry". >> >> From the notification area, I can see that a vif2.0 has been created. >> >> I disabled the firewall, and ubuntu seems don''t have selinux problem. >> could someone help me with this? >> >> Thanks in advance. >> >> "xl info" gives: >> host : xisisu-desktop >> release : 3.3.6 >> version : #1 SMP Sun May 13 18:24:00 CDT 2012 >> machine : x86_64 >> nr_cpus : 12 >> nr_nodes : 1 >> cores_per_socket : 6 >> threads_per_core : 2 >> cpu_mhz : 3378 >> hw_caps : >> bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 >> virt_caps : hvm hvm_directio >> total_memory : 12277 >> free_memory : 1094 >> free_cpus : 0 >> xen_major : 4 >> xen_minor : 1 >> xen_extra : .2 >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> xen_scheduler : credit >> xen_pagesize : 4096 >> platform_params : virt_start=0xffff800000000000 >> xen_changeset : unavailable >> xen_commandline : >> cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) >> cc_compile_by : xisisu >> cc_compile_domain : >> cc_compile_date : Sun May 13 17:46:53 CDT 2012 >> xend_config_format : 4 >> >> >> Here is the install configure file: >> >> "name="centosinstall" >> vcpus=2 >> memory=2048 >> disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] >> vif=[''bridge=eth0''] >> kernel="/home/xisisu/Desktop/vmlinuz" >> ramdisk="/home/xisisu/Desktop/initrd.img" >> on_reboot=''restart'' >> on_crash=''restart'' >> >> >> >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Casey DeLorme
2012-May-14 06:04 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
First, just in case, make sure you have the bridge-utils package installed (apt-get install bridge-utils). As for the interfaces, when you bridge a network to a Xen virtual machine, you use a bridge (from bridge-utils). Your interfaces file should have eth0 configuration inside of it. Based on the fact that your interfaces file did not have a record for eth0, I am going to assume that you are using the Ubuntu GUI utility "Network Manager". Interfaces will override the Network Manager, just be forewarned that the Ubuntu GUI may tell you that you have no iInternet connection when in fact you do. If you are using DHCP on Ubuntu, your interfaces file can work as follows: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet manual auto xenbr0 iface xenbr0 inet dhcp bridge_ports eth0 When you add "auto xenbr0" you are effectively "creating" a new virtual network bridge called "xenbr0". So xenbr0 is a virtual bridge, eth0 is a physical device. You can flip-flop which is dhcp and which is manual, it only determines which device gives Ubuntu an IP address. I believe the lack of connection with the previous configurations is because no physical device (eth0) was established in the interfaces file. Give it a try and let me know. ~Casey On Mon, May 14, 2012 at 1:53 AM, Sisu Xi <xisisu@gmail.com> wrote:> Hi, Casey: > > Thanks for your reply. Could you be a little more specific? > > I checked my /etc/networking/interfaces, it is: > auto lo > iface lo inet loopback. > > I changed it to what you suggested: > auto xenbr0 > iface xenbr0 inet manual > bridge_ports eth0 > This time Dom0 has no network. > > I also tried: > auto xenbr0 > iface xenbr0 inet dhcp > bridge_ports eth0 > Dom0 also has no network. > > Thanks! > > On Mon, May 14, 2012 at 12:36 AM, Casey DeLorme <cdelorme@gmail.com>wrote: > >> Hello, >> >> Guessing eth0 isn''t a bridge, have you tried creating a bridge and using >> that instead? >> >> bridge-utils package installed and add to /etc/networking/interfaces: >> >> auto xenbr0 >> iface xenbr0 inet manual >> bridge_ports eth0 >> >> Then replace eth0 in the centos HVM configuration? >> >> >> On Mon, May 14, 2012 at 1:25 AM, Sisu Xi <xisisu@gmail.com> wrote: >> >>> Hi, all: >>> >>> I am using Ubuntu 12.04, 64bit. compiled Linux kernel from source, >>> kernel is 3.3.6. Compiled Xen from source, version is 4.1.2. >>> >>> so far so good. >>> Dom0 can boot without problem. Dom0 has network. >>> >>> However, when I downloaded the vmlinuz and initrd.img for centos 6.2 and >>> try to install it, >>> I first picked network install, then it asked me to pick network, I >>> choose DHCP for both iipv4 and ipv6. >>> After that, it stops at >>> "Waiting for NetworkManager to configure eth0." >>> "Retry". >>> >>> From the notification area, I can see that a vif2.0 has been created. >>> >>> I disabled the firewall, and ubuntu seems don''t have selinux problem. >>> could someone help me with this? >>> >>> Thanks in advance. >>> >>> "xl info" gives: >>> host : xisisu-desktop >>> release : 3.3.6 >>> version : #1 SMP Sun May 13 18:24:00 CDT 2012 >>> machine : x86_64 >>> nr_cpus : 12 >>> nr_nodes : 1 >>> cores_per_socket : 6 >>> threads_per_core : 2 >>> cpu_mhz : 3378 >>> hw_caps : >>> bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 >>> virt_caps : hvm hvm_directio >>> total_memory : 12277 >>> free_memory : 1094 >>> free_cpus : 0 >>> xen_major : 4 >>> xen_minor : 1 >>> xen_extra : .2 >>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>> hvm-3.0-x86_32p hvm-3.0-x86_64 >>> xen_scheduler : credit >>> xen_pagesize : 4096 >>> platform_params : virt_start=0xffff800000000000 >>> xen_changeset : unavailable >>> xen_commandline : >>> cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro >>> 4.6.3-1ubuntu5) >>> cc_compile_by : xisisu >>> cc_compile_domain : >>> cc_compile_date : Sun May 13 17:46:53 CDT 2012 >>> xend_config_format : 4 >>> >>> >>> Here is the install configure file: >>> >>> "name="centosinstall" >>> vcpus=2 >>> memory=2048 >>> disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] >>> vif=[''bridge=eth0''] >>> kernel="/home/xisisu/Desktop/vmlinuz" >>> ramdisk="/home/xisisu/Desktop/initrd.img" >>> on_reboot=''restart'' >>> on_crash=''restart'' >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Sisu Xi
2012-May-14 06:14 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
Hi,Casey: Thanks for your reply. I do have bridge-utils installed. I am using the suggested configuration, and still, Dom0 has network, while i stuck in the waiting screen for DomU. Here is a screenshot showing network manager, domu screen, and the interface file. thanks! Sisu On Mon, May 14, 2012 at 1:04 AM, Casey DeLorme <cdelorme@gmail.com> wrote:> First, just in case, make sure you have the bridge-utils package installed > (apt-get install bridge-utils). > > As for the interfaces, when you bridge a network to a Xen virtual machine, > you use a bridge (from bridge-utils). Your interfaces file should have > eth0 configuration inside of it. > > Based on the fact that your interfaces file did not have a record for > eth0, I am going to assume that you are using the Ubuntu GUI utility > "Network Manager". Interfaces will override the Network Manager, just be > forewarned that the Ubuntu GUI may tell you that you have no iInternet > connection when in fact you do. > > > If you are using DHCP on Ubuntu, your interfaces file can work as follows: > > > auto lo > iface lo inet loopback > > allow-hotplug eth0 > iface eth0 inet manual > > auto xenbr0 > iface xenbr0 inet dhcp > bridge_ports eth0 > > > When you add "auto xenbr0" you are effectively "creating" a new virtual > network bridge called "xenbr0". So xenbr0 is a virtual bridge, eth0 is a > physical device. > > You can flip-flop which is dhcp and which is manual, it only determines > which device gives Ubuntu an IP address. > > > I believe the lack of connection with the previous configurations is > because no physical device (eth0) was established in the interfaces file. > > Give it a try and let me know. > > ~Casey > > > On Mon, May 14, 2012 at 1:53 AM, Sisu Xi <xisisu@gmail.com> wrote: > >> Hi, Casey: >> >> Thanks for your reply. Could you be a little more specific? >> >> I checked my /etc/networking/interfaces, it is: >> auto lo >> iface lo inet loopback. >> >> I changed it to what you suggested: >> auto xenbr0 >> iface xenbr0 inet manual >> bridge_ports eth0 >> This time Dom0 has no network. >> >> I also tried: >> auto xenbr0 >> iface xenbr0 inet dhcp >> bridge_ports eth0 >> Dom0 also has no network. >> >> Thanks! >> >> On Mon, May 14, 2012 at 12:36 AM, Casey DeLorme <cdelorme@gmail.com>wrote: >> >>> Hello, >>> >>> Guessing eth0 isn''t a bridge, have you tried creating a bridge and using >>> that instead? >>> >>> bridge-utils package installed and add to /etc/networking/interfaces: >>> >>> auto xenbr0 >>> iface xenbr0 inet manual >>> bridge_ports eth0 >>> >>> Then replace eth0 in the centos HVM configuration? >>> >>> >>> On Mon, May 14, 2012 at 1:25 AM, Sisu Xi <xisisu@gmail.com> wrote: >>> >>>> Hi, all: >>>> >>>> I am using Ubuntu 12.04, 64bit. compiled Linux kernel from source, >>>> kernel is 3.3.6. Compiled Xen from source, version is 4.1.2. >>>> >>>> so far so good. >>>> Dom0 can boot without problem. Dom0 has network. >>>> >>>> However, when I downloaded the vmlinuz and initrd.img for centos 6.2 >>>> and try to install it, >>>> I first picked network install, then it asked me to pick network, I >>>> choose DHCP for both iipv4 and ipv6. >>>> After that, it stops at >>>> "Waiting for NetworkManager to configure eth0." >>>> "Retry". >>>> >>>> From the notification area, I can see that a vif2.0 has been created. >>>> >>>> I disabled the firewall, and ubuntu seems don''t have selinux problem. >>>> could someone help me with this? >>>> >>>> Thanks in advance. >>>> >>>> "xl info" gives: >>>> host : xisisu-desktop >>>> release : 3.3.6 >>>> version : #1 SMP Sun May 13 18:24:00 CDT 2012 >>>> machine : x86_64 >>>> nr_cpus : 12 >>>> nr_nodes : 1 >>>> cores_per_socket : 6 >>>> threads_per_core : 2 >>>> cpu_mhz : 3378 >>>> hw_caps : >>>> bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 >>>> virt_caps : hvm hvm_directio >>>> total_memory : 12277 >>>> free_memory : 1094 >>>> free_cpus : 0 >>>> xen_major : 4 >>>> xen_minor : 1 >>>> xen_extra : .2 >>>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>> hvm-3.0-x86_32p hvm-3.0-x86_64 >>>> xen_scheduler : credit >>>> xen_pagesize : 4096 >>>> platform_params : virt_start=0xffff800000000000 >>>> xen_changeset : unavailable >>>> xen_commandline : >>>> cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro >>>> 4.6.3-1ubuntu5) >>>> cc_compile_by : xisisu >>>> cc_compile_domain : >>>> cc_compile_date : Sun May 13 17:46:53 CDT 2012 >>>> xend_config_format : 4 >>>> >>>> >>>> Here is the install configure file: >>>> >>>> "name="centosinstall" >>>> vcpus=2 >>>> memory=2048 >>>> disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] >>>> vif=[''bridge=eth0''] >>>> kernel="/home/xisisu/Desktop/vmlinuz" >>>> ramdisk="/home/xisisu/Desktop/initrd.img" >>>> on_reboot=''restart'' >>>> on_crash=''restart'' >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >> >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Sisu Xi
2012-May-14 06:22 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
Hi, Casey: after fixing the typo (hotplut -> hotplug), it works now! Thanks very much! Yours, Sisu On Mon, May 14, 2012 at 1:04 AM, Casey DeLorme <cdelorme@gmail.com> wrote:> First, just in case, make sure you have the bridge-utils package installed > (apt-get install bridge-utils). > > As for the interfaces, when you bridge a network to a Xen virtual machine, > you use a bridge (from bridge-utils). Your interfaces file should have > eth0 configuration inside of it. > > Based on the fact that your interfaces file did not have a record for > eth0, I am going to assume that you are using the Ubuntu GUI utility > "Network Manager". Interfaces will override the Network Manager, just be > forewarned that the Ubuntu GUI may tell you that you have no iInternet > connection when in fact you do. > > > If you are using DHCP on Ubuntu, your interfaces file can work as follows: > > > auto lo > iface lo inet loopback > > allow-hotplug eth0 > iface eth0 inet manual > > auto xenbr0 > iface xenbr0 inet dhcp > bridge_ports eth0 > > > When you add "auto xenbr0" you are effectively "creating" a new virtual > network bridge called "xenbr0". So xenbr0 is a virtual bridge, eth0 is a > physical device. > > You can flip-flop which is dhcp and which is manual, it only determines > which device gives Ubuntu an IP address. > > > I believe the lack of connection with the previous configurations is > because no physical device (eth0) was established in the interfaces file. > > Give it a try and let me know. > > ~Casey > > > On Mon, May 14, 2012 at 1:53 AM, Sisu Xi <xisisu@gmail.com> wrote: > >> Hi, Casey: >> >> Thanks for your reply. Could you be a little more specific? >> >> I checked my /etc/networking/interfaces, it is: >> auto lo >> iface lo inet loopback. >> >> I changed it to what you suggested: >> auto xenbr0 >> iface xenbr0 inet manual >> bridge_ports eth0 >> This time Dom0 has no network. >> >> I also tried: >> auto xenbr0 >> iface xenbr0 inet dhcp >> bridge_ports eth0 >> Dom0 also has no network. >> >> Thanks! >> >> On Mon, May 14, 2012 at 12:36 AM, Casey DeLorme <cdelorme@gmail.com>wrote: >> >>> Hello, >>> >>> Guessing eth0 isn''t a bridge, have you tried creating a bridge and using >>> that instead? >>> >>> bridge-utils package installed and add to /etc/networking/interfaces: >>> >>> auto xenbr0 >>> iface xenbr0 inet manual >>> bridge_ports eth0 >>> >>> Then replace eth0 in the centos HVM configuration? >>> >>> >>> On Mon, May 14, 2012 at 1:25 AM, Sisu Xi <xisisu@gmail.com> wrote: >>> >>>> Hi, all: >>>> >>>> I am using Ubuntu 12.04, 64bit. compiled Linux kernel from source, >>>> kernel is 3.3.6. Compiled Xen from source, version is 4.1.2. >>>> >>>> so far so good. >>>> Dom0 can boot without problem. Dom0 has network. >>>> >>>> However, when I downloaded the vmlinuz and initrd.img for centos 6.2 >>>> and try to install it, >>>> I first picked network install, then it asked me to pick network, I >>>> choose DHCP for both iipv4 and ipv6. >>>> After that, it stops at >>>> "Waiting for NetworkManager to configure eth0." >>>> "Retry". >>>> >>>> From the notification area, I can see that a vif2.0 has been created. >>>> >>>> I disabled the firewall, and ubuntu seems don''t have selinux problem. >>>> could someone help me with this? >>>> >>>> Thanks in advance. >>>> >>>> "xl info" gives: >>>> host : xisisu-desktop >>>> release : 3.3.6 >>>> version : #1 SMP Sun May 13 18:24:00 CDT 2012 >>>> machine : x86_64 >>>> nr_cpus : 12 >>>> nr_nodes : 1 >>>> cores_per_socket : 6 >>>> threads_per_core : 2 >>>> cpu_mhz : 3378 >>>> hw_caps : >>>> bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 >>>> virt_caps : hvm hvm_directio >>>> total_memory : 12277 >>>> free_memory : 1094 >>>> free_cpus : 0 >>>> xen_major : 4 >>>> xen_minor : 1 >>>> xen_extra : .2 >>>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >>>> hvm-3.0-x86_32p hvm-3.0-x86_64 >>>> xen_scheduler : credit >>>> xen_pagesize : 4096 >>>> platform_params : virt_start=0xffff800000000000 >>>> xen_changeset : unavailable >>>> xen_commandline : >>>> cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro >>>> 4.6.3-1ubuntu5) >>>> cc_compile_by : xisisu >>>> cc_compile_domain : >>>> cc_compile_date : Sun May 13 17:46:53 CDT 2012 >>>> xend_config_format : 4 >>>> >>>> >>>> Here is the install configure file: >>>> >>>> "name="centosinstall" >>>> vcpus=2 >>>> memory=2048 >>>> disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] >>>> vif=[''bridge=eth0''] >>>> kernel="/home/xisisu/Desktop/vmlinuz" >>>> ramdisk="/home/xisisu/Desktop/initrd.img" >>>> on_reboot=''restart'' >>>> on_crash=''restart'' >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >> >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Niels Dettenbach (Syndicat IT&Internet)
2012-May-14 06:28 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Sisu Xi <xisisu@gmail.com> schrieb:>> You can flip-flop which is dhcp and which is manual, it only >determines >> which device gives Ubuntu an IP address.This is afair not correct at all as the *correct* point to assign is the bridge device. This *do* work usually even if you use a bridge port device on a connectitvity level - but afair bridge port devices should be not configured for IP byself as this might breaks other functionality. hth best regards, N.iels. - -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iIEEAREIAEEFAk+wpfY6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDS/4AJ4hkeiyqGbg fWaJCevOfSvv+MuX6gCfeCpGDK4juMkEslMOfyjtwjawdRo=ZwTy -----END PGP SIGNATURE-----
Sisu Xi
2012-May-14 22:58 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
Hi, Casey and Niels: Thanks for your reply. I am trying it on another machine with centos 6.2, 64bit installed. Compiled kernel 3.3.6 from source, compiled xen 4.1.2 from source. I am having exactly the same problem as before, where when installing domU, the screen stops at waiting for networkmanager, and then "retry". I have network in dom0. I do have "bridge-utils" installed. This time in centos, there is no /etc/networks/interfaces file, could you kindly tell me how to solve this problem in CentOS? Thanks in advance! Sisu [root@null-001cc0b1994f VM]# cat /etc/networks default 0.0.0.0 loopback 127.0.0.0 link-local 169.254.0.0 [root@null-001cc0b1994f VM]# ip route show default via 172.16.21.254 dev eth0 proto static 172.16.20.0/23 dev eth0 proto kernel scope link src 172.16.21.167 metric 1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 [root@null-001cc0b1994f VM]# xl info host : null-001cc0b1994f.seas.wustl.edu release : 3.3.6 version : #1 SMP Mon May 14 17:29:53 CDT 2012 machine : x86_64 nr_cpus : 12 nr_nodes : 1 cores_per_socket : 6 threads_per_core : 2 cpu_mhz : 3378 hw_caps : bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 12277 free_memory : 10062 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_mem=2048M dom0_max_vcpus=1 dom0_vcpus_pin sched=credit cc_compiler : gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) cc_compile_by : xisisu cc_compile_domain : seas.wustl.edu cc_compile_date : Mon May 14 17:06:47 CDT 2012 xend_config_format : 4 [root@null-001cc0b1994f VM]# cat vm1.run name="centos" vcpus=2 memory=2048 disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] vif=[''bridge=eth0''] kernel="/home/xisisu/Desktop/vmlinuz" ramdisk="/home/xisisu/Desktop/initrd.img" on_reboot=''restart'' on_crash=''restart'' [root@null-001cc0b1994f VM]# chkconfig --list NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off autofs 0:off 1:off 2:off 3:on 4:on 5:on 6:off avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off cgconfig 0:off 1:off 2:on 3:on 4:on 5:on 6:off cgred 0:off 1:off 2:off 3:off 4:off 5:off 6:off cpuspeed 0:off 1:on 2:off 3:off 4:off 5:off 6:off crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off dnsmasq 0:off 1:off 2:off 3:off 4:off 5:off 6:off ebtables 0:off 1:off 2:off 3:off 4:off 5:off 6:off fcoe 0:off 1:off 2:on 3:on 4:on 5:on 6:off firstboot 0:off 1:off 2:off 3:off 4:off 5:off 6:off haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ip6tables 0:off 1:off 2:off 3:off 4:off 5:off 6:off iptables 0:off 1:off 2:off 3:off 4:off 5:off 6:off irqbalance 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off kdump 0:off 1:off 2:off 3:on 4:on 5:on 6:off ksm 0:off 1:off 2:off 3:on 4:on 5:on 6:off ksmtuned 0:off 1:off 2:off 3:on 4:on 5:on 6:off libvirt-guests 0:off 1:off 2:on 3:on 4:on 5:on 6:off libvirtd 0:off 1:off 2:off 3:on 4:on 5:on 6:off livesys 0:off 1:off 2:off 3:on 4:on 5:on 6:off livesys-late 0:off 1:off 2:off 3:on 4:on 5:on 6:off lldpad 0:off 1:off 2:on 3:on 4:on 5:on 6:off lvm2-monitor 0:off 1:on 2:on 3:on 4:on 5:on 6:off mdmonitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off multipathd 0:off 1:off 2:off 3:off 4:off 5:off 6:off netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off network 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ntpdate 0:off 1:off 2:off 3:off 4:off 5:off 6:off openct 0:off 1:off 2:on 3:on 4:on 5:on 6:off pcscd 0:off 1:off 2:on 3:on 4:on 5:on 6:off portreserve 0:off 1:off 2:on 3:on 4:on 5:on 6:off postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off psacct 0:off 1:off 2:off 3:off 4:off 5:off 6:off quota_nld 0:off 1:off 2:off 3:off 4:off 5:off 6:off radvd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off restorecond 0:off 1:off 2:off 3:off 4:off 5:off 6:off rngd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcbind 0:off 1:off 2:on 3:on 4:on 5:on 6:off rpcgssd 0:off 1:off 2:off 3:on 4:on 5:on 6:off rpcidmapd 0:off 1:off 2:off 3:on 4:on 5:on 6:off rpcsvcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off saslauthd 0:off 1:off 2:off 3:off 4:off 5:off 6:off smartd 0:off 1:off 2:off 3:off 4:off 5:off 6:off spice-vdagentd 0:off 1:off 2:off 3:off 4:off 5:on 6:off sshd 0:off 1:off 2:off 3:off 4:off 5:off 6:off sysstat 0:off 1:on 2:on 3:on 4:on 5:on 6:off udev-post 0:off 1:on 2:on 3:on 4:on 5:on 6:off vncserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off wdaemon 0:off 1:off 2:off 3:off 4:off 5:off 6:off wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off xen-watchdog 0:off 1:off 2:on 3:on 4:on 5:on 6:off xencommons 0:off 1:off 2:on 3:on 4:on 5:on 6:off xend 0:off 1:off 2:on 3:on 4:on 5:on 6:off xendomains 0:off 1:off 2:on 3:on 4:on 5:on 6:off On Mon, May 14, 2012 at 1:28 AM, Niels Dettenbach (Syndicat IT&Internet) < nd@syndicat.com> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > > Sisu Xi <xisisu@gmail.com> schrieb: > > >> You can flip-flop which is dhcp and which is manual, it only > >determines > >> which device gives Ubuntu an IP address. > > This is afair not correct at all as the *correct* point to assign is the > bridge device. > > This *do* work usually even if you use a bridge port device on a > connectitvity level - but afair bridge port devices should be not > configured for IP byself as this might breaks other functionality. > > > hth > best regards, > > > N.iels. > > > - -- > Niels Dettenbach > Syndicat IT&Internet > http://www.syndicat.com > -----BEGIN PGP SIGNATURE----- > Version: APG v1.0.8 > > iIEEAREIAEEFAk+wpfY6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu > dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDS/4AJ4hkeiyqGbg > fWaJCevOfSvv+MuX6gCfeCpGDK4juMkEslMOfyjtwjawdRo> =ZwTy > -----END PGP SIGNATURE----- > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Sisu Xi
2012-May-14 23:14 UTC
Re: domu has no network when installing (but Dom0 has) -- sisu
Hi, all: after removing all the *virt* and *qemu* packages, it works now. I don''t know why. Thanks all the same. Sisu On Mon, May 14, 2012 at 5:58 PM, Sisu Xi <xisisu@gmail.com> wrote:> Hi, Casey and Niels: > > Thanks for your reply. > > I am trying it on another machine with centos 6.2, 64bit installed. > Compiled kernel 3.3.6 from source, compiled xen 4.1.2 from source. > > I am having exactly the same problem as before, where when installing > domU, the screen stops at waiting for networkmanager, and then "retry". > > I have network in dom0. > > > I do have "bridge-utils" installed. > > This time in centos, there is no /etc/networks/interfaces file, could you > kindly tell me how to solve this problem in CentOS? > > Thanks in advance! > > Sisu > > [root@null-001cc0b1994f VM]# cat /etc/networks > default 0.0.0.0 > loopback 127.0.0.0 > link-local 169.254.0.0 > > [root@null-001cc0b1994f VM]# ip route show > default via 172.16.21.254 dev eth0 proto static > 172.16.20.0/23 dev eth0 proto kernel scope link src 172.16.21.167 > metric 1 > 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > > [root@null-001cc0b1994f VM]# xl info > host : null-001cc0b1994f.seas.wustl.edu > release : 3.3.6 > version : #1 SMP Mon May 14 17:29:53 CDT 2012 > > machine : x86_64 > nr_cpus : 12 > nr_nodes : 1 > cores_per_socket : 6 > threads_per_core : 2 > cpu_mhz : 3378 > hw_caps : > bfebfbff:2c000800:00000000:00003f40:029ae3bf:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 12277 > free_memory : 10062 > > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : dom0_mem=2048M dom0_max_vcpus=1 dom0_vcpus_pin > sched=credit > cc_compiler : gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) > (GCC) > cc_compile_by : xisisu > cc_compile_domain : seas.wustl.edu > cc_compile_date : Mon May 14 17:06:47 CDT 2012 > xend_config_format : 4 > > > [root@null-001cc0b1994f VM]# cat vm1.run > name="centos" > > vcpus=2 > memory=2048 > disk=[''file:/home/xisisu/Desktop/VM/vm1.img,xvda,w''] > vif=[''bridge=eth0''] > kernel="/home/xisisu/Desktop/vmlinuz" > ramdisk="/home/xisisu/Desktop/initrd.img" > on_reboot=''restart'' > on_crash=''restart'' > > [root@null-001cc0b1994f VM]# chkconfig --list > NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off > acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off > atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > autofs 0:off 1:off 2:off 3:on 4:on 5:on 6:off > avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off > cgconfig 0:off 1:off 2:on 3:on 4:on 5:on 6:off > cgred 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > cpuspeed 0:off 1:on 2:off 3:off 4:off 5:off > 6:off > crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off > cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off > dnsmasq 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > ebtables 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > fcoe 0:off 1:off 2:on 3:on 4:on 5:on 6:off > firstboot 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off > httpd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > ip6tables 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > iptables 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > irqbalance 0:off 1:off 2:off 3:on 4:on 5:on 6:off > iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off > iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off > kdump 0:off 1:off 2:off 3:on 4:on 5:on 6:off > ksm 0:off 1:off 2:off 3:on 4:on 5:on 6:off > ksmtuned 0:off 1:off 2:off 3:on 4:on 5:on 6:off > libvirt-guests 0:off 1:off 2:on 3:on 4:on 5:on 6:off > libvirtd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > livesys 0:off 1:off 2:off 3:on 4:on 5:on 6:off > livesys-late 0:off 1:off 2:off 3:on 4:on 5:on 6:off > lldpad 0:off 1:off 2:on 3:on 4:on 5:on 6:off > lvm2-monitor 0:off 1:on 2:on 3:on 4:on 5:on 6:off > mdmonitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off > messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off > multipathd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > netconsole 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off > network 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > nfs 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off > ntpd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > ntpdate 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > openct 0:off 1:off 2:on 3:on 4:on 5:on 6:off > pcscd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > portreserve 0:off 1:off 2:on 3:on 4:on 5:on 6:off > postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off > psacct 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > quota_nld 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > radvd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > rdisc 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > restorecond 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > rngd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > rpcbind 0:off 1:off 2:on 3:on 4:on 5:on 6:off > rpcgssd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > rpcidmapd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > rpcsvcgssd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off > saslauthd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > smartd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > spice-vdagentd 0:off 1:off 2:off 3:off 4:off 5:on > 6:off > sshd 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > sysstat 0:off 1:on 2:on 3:on 4:on 5:on 6:off > udev-post 0:off 1:on 2:on 3:on 4:on 5:on 6:off > vncserver 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > wdaemon 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > xen-watchdog 0:off 1:off 2:on 3:on 4:on 5:on 6:off > xencommons 0:off 1:off 2:on 3:on 4:on 5:on 6:off > xend 0:off 1:off 2:on 3:on 4:on 5:on 6:off > xendomains 0:off 1:off 2:on 3:on 4:on 5:on 6:off > > > > > > > > > > On Mon, May 14, 2012 at 1:28 AM, Niels Dettenbach (Syndicat IT&Internet) < > nd@syndicat.com> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> >> >> Sisu Xi <xisisu@gmail.com> schrieb: >> >> >> You can flip-flop which is dhcp and which is manual, it only >> >determines >> >> which device gives Ubuntu an IP address. >> >> This is afair not correct at all as the *correct* point to assign is the >> bridge device. >> >> This *do* work usually even if you use a bridge port device on a >> connectitvity level - but afair bridge port devices should be not >> configured for IP byself as this might breaks other functionality. >> >> >> hth >> best regards, >> >> >> N.iels. >> >> >> - -- >> Niels Dettenbach >> Syndicat IT&Internet >> http://www.syndicat.com >> -----BEGIN PGP SIGNATURE----- >> Version: APG v1.0.8 >> >> iIEEAREIAEEFAk+wpfY6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu >> dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDS/4AJ4hkeiyqGbg >> fWaJCevOfSvv+MuX6gCfeCpGDK4juMkEslMOfyjtwjawdRo>> =ZwTy >> -----END PGP SIGNATURE----- >> >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users