Andy
2011-Jun-14 15:38 UTC
[Xen-users] Device 0 (vif) could not be connected. Hotplug scripts not working
Hi I have upgraded my Dom0 from lenny to sqeeze and xen to 4.0 after that there were some errors when i tried to reboot, but i could fix most of them my dom0 is running fine now, but when i try to start a guest, i get an error: darwin:/# xm create infopool.cfg Using config file "/etc/xen/infopool.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. i tried many things to get around this, but none did work. can anybody help me? *infopool.cfg:* kernel = ''/boot/vmlinuz-2.6.32-5-xen-686'' ramdisk = ''/boot/initrd.img-2.6.32-5-xen-686'' memory = ''256'' extra = ''console=hvc0 xencons=tty independent_wallclock=1'' root = ''/dev/sda1 ro'' disk = [ ''file:/var/xen/domains/infopool/disk.img,sda1,w'', ''file:/var/xen/domains/infopool/swap.img,sda2,w'' ] name = ''infopool'' vif = [''bridge=eth2,mac=00:16:3e:00:00:01''] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' *xend-config.sxp* (network-script ''multi-network-bridge'') (vif-script vif-bridge) (dom0-min-mem 196) (dom0-cpus 0) *xm info:* host : darwin release : 2.6.32-5-xen-686 version : #1 SMP Wed May 18 09:43:15 UTC 2011 machine : i686 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100000:00000000:00000180:0000641d:00000000:00000000:00000000 virt_caps : total_memory : 4030 free_memory : 2965 node_to_cpu : node0:0-1 node_to_memory : node0:2965 node_to_dma32_mem : node0:2913 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=1024M cc_compiler : gcc version 4.4.5 (Debian 4.4.5-10) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Wed Jan 12 15:04:50 UTC 2011 xend_config_format : 4 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jun-18 05:47 UTC
Re: [Xen-users] Device 0 (vif) could not be connected. Hotplug scripts not working
On Tue, Jun 14, 2011 at 11:38 AM, Andy <xen@unkreativ.at> wrote:> Hi > > I have upgraded my Dom0 from lenny to sqeeze and xen to 4.0 > after that there were some errors when i tried to reboot, but i could fix > most of them > > my dom0 is running fine now, but when i try to start a guest, i get an > error: > > darwin:/# xm create infopool.cfg > Using config file "/etc/xen/infopool.cfg". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >http://wiki.xensource.com/xenwiki/XenCommonProblems#head-f75dde47e11dbf9bfd8fca200917316babb654eb> i tried many things to get around this, but none did work. > can anybody help me? > > infopool.cfg: > kernel = ''/boot/vmlinuz-2.6.32-5-xen-686'' > ramdisk = ''/boot/initrd.img-2.6.32-5-xen-686'' > memory = ''256'' > extra = ''console=hvc0 xencons=tty independent_wallclock=1'' > root = ''/dev/sda1 ro'' > disk = [ ''file:/var/xen/domains/infopool/disk.img,sda1,w'', > ''file:/var/xen/domains/infopool/swap.img,sda2,w'' ] > name = ''infopool'' > vif = [''bridge=eth2,mac=00:16:3e:00:00:01''] > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > xend-config.sxp > (network-script ''multi-network-bridge'') > (vif-script vif-bridge) > (dom0-min-mem 196) > (dom0-cpus 0) > > xm info: > host : darwin > release : 2.6.32-5-xen-686 > version : #1 SMP Wed May 18 09:43:15 UTC 2011 > machine : i686 > nr_cpus : 2 > nr_nodes : 1 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 2992 > hw_caps : > bfebfbff:20100000:00000000:00000180:0000641d:00000000:00000000:00000000 > virt_caps : > total_memory : 4030 > free_memory : 2965 > node_to_cpu : node0:0-1 > node_to_memory : node0:2965 > node_to_dma32_mem : node0:2913 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .1 > xen_caps : xen-3.0-x86_32p > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xf5800000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=1024M > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-10) > cc_compile_by : waldi > cc_compile_domain : debian.org > cc_compile_date : Wed Jan 12 15:04:50 UTC 2011 > xend_config_format : 4 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- Opensolaris domU - install ok, pygrub boot not ok.
- Xen 4.0.0 pvops 2.6.31version 64 bit cannot install gplpv on a win2k3 server 32 bit
- Poor performance on bandwidth, Xen 4.0.1 kernel pvops 2.6.32.24
- broken network-support for netBSD-domUs?
- Debian/squeeze: domU live migraton hangs