Hello. First of all I ''m pretty new to Linux and this is my first install of Xen. So don''t mind me wrong if sometimes I don''t know which command is appropriate to fetch results. I''m running a new Debian Squeeze release 2.6.32-5-xen-amd64 with minimal components. I''ve been going through install of Xen as per the documentation for the 4.2.1 release and did so by source. However I installed (make install & make world) from within /user/Download/xen4.2.1, I don''t know if that is a good/bad idea? All dependancies were installed and the install showed no error upon a few tries. First weird behaviour, I ended up in/at grub with several Xen extensions.gz (xen 4.2.1, xen 4.2, xen 4.0, xen: no one of them able ton boot) so I had a Xen 4 with AMD64, which boots And I can see the DomU booted: root@debian:/home/dorian# uname -a Linux debian 2.6.32-5-xen-amd64 #1 SMP Mon Feb 25 02:51:39 UTC 2013 x86_64 GNU/Linux root@debian:/home/dorian# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2830 2 r----- 30.5 I make LVM partitions on which to install the guests. I have following logical volume created: root@debian:/dev# lvdisplay --- Logical volume --- LV Name /dev/Esp-Virt/Vol1 VG Name Esp-Virt LV UUID 4l5BVd-7vSV-W3vZ-or5i-KLjX-6MjC-JYGyEJ LV Write Access read/write LV Status available # open 0 LV Size 24,00 GiB Current LE 6144 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:0 --- Logical volume --- LV Name /dev/Esp-Virt/Marie-DHCP-swap VG Name Esp-Virt LV UUID oJhOii-Ji2Z-ZwWe-YQ37-6MRd-kA1u-cCND34 LV Write Access read/write LV Status available # open 0 LV Size 256,00 MiB Current LE 64 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:1 --- Logical volume --- LV Name /dev/Esp-Virt/Marie-DHCP-disk VG Name Esp-Virt LV UUID dGA6fg-Py5q-QHZM-0CTL-N03s-v4KV-DrQ3f7 LV Write Access read/write LV Status available # open 0 LV Size 4,00 GiB Current LE 1024 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:2 Then I edited /etc/xen-tools/xen-tools.conf to suit my wishes: root@debian:/dev# grep -E -v ''^(#|$)'' /etc/xen-tools/xen-tools.conf lvm = Esp-Virt install-method = debootstrap size = 4Gb # Disk image size. memory = 256Mb # Memory size swap = 256Mb # Swap size fs = ext3 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default distribution to install. image = sparse # Specify sparse vs. full disk images. gateway = 192.168.1.1 netmask = 255.255.255.0 broadcast = 192.168.1.255 passwd = 1 accounts = 1 kernel = /boot/vmlinuz-`uname -r` initrd = /boot/initrd.img-`uname -r` mirror = `xt-guess-suite-and-mirror --mirror` ext3_options = noatime,nodiratime,errors=remount-ro ext2_options = noatime,nodiratime,errors=remount-ro xfs_options = defaults reiserfs_options = defaults btrfs_options = defaults serial_device = hvc0 #default disk_device = xvda #default I ''ve created my virtual machines : root@debian:/home/dorian# xen-create-image --hostname=Marie-DHCP --ip=192.168.1.3 --passwd --force General Information -------------------- Hostname : Marie-DHCP Distribution : squeeze Mirror : ftp://ftp.fr.debian.org/debian/ Partitions : swap 256Mb (swap) / 4Gb (ext3) Image type : full Memory size : 256Mb Kernel path : /boot/vmlinuz-2.6.32-5-xen-amd64 Initrd path : /boot/initrd.img-2.6.32-5-xen-amd64 Networking Information ---------------------- IP Address 1 : 192.168.1.3 [MAC: 00:16:3E:BF:18:50] Netmask : 255.255.255.0 Broadcast : 192.168.1.255 Gateway : 192.168.1.1 Removing /dev/Esp-Virt/Marie-DHCP-swap - since we''re forcing the install Removing /dev/Esp-Virt/Marie-DHCP-disk - since we''re forcing the install Creating swap on /dev/Esp-Virt/Marie-DHCP-swap Done Creating ext3 filesystem on /dev/Esp-Virt/Marie-DHCP-disk Done Installation method: debootstrap Done Running hooks Done No role scripts were specified. Skipping Creating Xen configuration file Done Setting up root password Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully All done Logfile produced at: /var/log/xen-tools/Marie-DHCP.log Installation Summary --------------------- Hostname : Marie-DHCP Distribution : squeeze IP-Address(es) : 192.168.1.3 RSA Fingerprint : 25:46:6c:76:3a:39:fc:7a:bb:7b:31:33:9c:7f:30:09 Root Password : N/A A # locate Marie shows: root@debian:/home/dorian/Téléchargements/xen-4.2.1# locate Marie /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-disk /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-swap /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--disk /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--swap /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--disk /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--swap /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-disk/b254:2 /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-swap/b254:1 /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--disk/b254:2 /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--swap/b254:1 /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--disk/b254:2 /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--swap/b254:1 /dev/Esp-Virt/Marie-DHCP-disk /dev/Esp-Virt/Marie-DHCP-swap /dev/disk/by-id/dm-name-Esp--Virt-Marie--DHCP--disk /dev/disk/by-id/dm-name-Esp--Virt-Marie--DHCP--swap /dev/mapper/Esp--Virt-Marie--DHCP--disk /dev/mapper/Esp--Virt-Marie--DHCP--swap /etc/xen/Marie-DHCP.cfg /etc/xen/Marie-DHCP.cfg.ancien /usr/share/zoneinfo/Europe/Mariehamn /usr/share/zoneinfo/posix/Europe/Mariehamn /usr/share/zoneinfo/right/Europe/Mariehamn /var/log/xen-tools/Marie-DHCP.0.log /var/log/xen-tools/Marie-DHCP.1.log /var/log/xen-tools/Marie-DHCP.2.log /var/log/xen-tools/Marie-DHCP.log root@debian:/home/dorian/Téléchargements/xen-4.2.1# ls /dev/Esp-Virt/ Marie-DHCP-disk Marie-DHCP-swap Vol1 I did configure the /etc/network/interfaces file like this (conversaly xen-create image... indicated ip=192.168.1.3 # The loopback network interface auto lo iface lo inet loopback auto xenbr0 iface xenbr0 inet dhcp bridge_ports eth0 #bridge_stp on #bridge_maxwait 0 #bridge_fd 0 whereas /// root@debian:/dev# grep -E -v ''^(#|$)'' /etc/xen/xend-config.sxp // NOT CONFIGURED AS PER THE DEBIAN SQUEEZE ADVICE (vif-script vif-bridge) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '''') So, I ''ve got this interfaces showing up. Vif x.x should appear after xm create Virtual-guest.cfg, I guess (which in my case is MArie-DHCP) root@debian:/home/dorian# brctl show bridge name bridge id STP enabled interfaces pan0 8000.000000000000 no xenbr0 8000.002655c46159 no eth0 Now, when I try to boot my DomU guest here is the error, which many research on the web didn''t show up thje solution. however: Step 1: root@debian:/dev# xm create Marie-DHCP.cfg Using config file "/etc/xen/Marie-DHCP.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working.>>>> I watched in the hotplug.logroot@debian:/dev# more /var/log/xen/xen-hotplug.log xenstore-read: couldn''t read path backend/vbd/2/51714/params xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-read: couldn''t read path backend/vbd/2/51713/params xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-write: could not write path backend/vbd/2/51713/hotplug-error xenstore-write: could not write path backend/vif/2/0/hotplug-error In the meantime of weeks in searching how to get around. I found the following usefull information:http://wiki.xen.org/wiki/XenCommonProblems#Xen_complains_about_.22hotplug_scripts_not_working.22 "This problem is often related to udev. Do you have udev installed? Is your udev the correct/supported version? "This error usually has more information in the end revealing the real reason.. for example: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. "This problem is often caused by not having "xen-netback" driver loaded in dom0 kernel. "The hotplug scripts are located in /etc/xen/scripts by default, and are labeled with the prefix vif-*. Those "scripts log to /var/log/xen/xen-hotplug.log, and more detailed information can be found there.">>>>>>>>>I know I installed udev, prior to install xen from source since hotplug plugin doesn''t exists/shows up.I''ve been trying to locate xen-netback driver. root@debian:/dev# cat /proc/modules | grep xen xen_evtchn 4355 1 - Live 0xffffffffa04d7000 xenfs 9616 1 - Live 0xffffffffa04ce000>>>>>>These modules seem .okBut since this call : http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Update_modules The following modules may be required:STep 2 xen-evtchn xen-gntdev >>> missing >>>> I think the error comes from xen-netback >>>missing this missing drivers xen-blkback >>>missing xenfs blktap >>> missing |Are they missing from Xen 4.2.1 from source Or did they don''t install properly (something like exit with errors? I''m willing to re install with detailed info if needed...). On the same wiki-page are numerous important advices , but often I don''t know where to look for the files (which directory + name)and/or the commands to use to edit except using nano.. e.g. Git (what''is it , how use it?? but''i''ll google through) I don''t know from which directory input I ''ve to make the substantial intalls provided by the last mentionned adress above. What am i missing for going through Step 2, I mean be able to launch my virtual machine where find it? Which command help out? I hope I''v"e been clear. since too many research pull me with confused through all the topic/issue links. So I summarize: Will I be able to resolve the xm create vm.cfg which I encounter as an issue. How do I get the xen- modules installed and running? I appreciate your help in solving this issue. Also please provide me with the commands since from th elinks I cannot solve it and take a risk to break the system. Sorry for the long thread!! Many thanks in advance Dorian Carpentier de Changy dechangydorian@yahoo.fr 0497/623 249 -------------------------- Rue Camille Lemonnier 22 1050 Bruxelles _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I''ve added Bold entry for easier reading since this post is quite long. thx Hello. First of all I ''m pretty new to Linux and this is my first install of Xen. So don''t mind me wrong if sometimes I don''t know which command is appropriate to fetch results. I''m running a new Debian Squeeze release 2.6.32-5-xen-amd64 with minimal components. I''ve been going through install of Xen as per the documentation for the 4.2.1 release and did so by source. However I installed (make install & make world) from within /user/Download/xen4.2.1, I don''t know if that is a good/bad idea? All dependancies were installed and the install showed no error upon a few tries. First weird behaviour, I ended up in/at grub with several Xen extensions.gz (xen 4.2.1, xen 4.2, xen 4.0, xen: no one of them able ton boot) so I had a Xen 4 with AMD64, which boots And I can see the DomU booted: root@debian:/home/dorian# uname -a Linux debian 2.6.32-5-xen-amd64 #1 SMP Mon Feb 25 02:51:39 UTC 2013 x86_64 GNU/Linux root@debian:/home/dorian# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2830 2 r----- 30.5 I make LVM partitions on which to install the guests. I have following logical volume created: root@debian:/dev# lvdisplay --- Logical volume --- LV Name /dev/Esp-Virt/Vol1 VG Name Esp-Virt LV UUID 4l5BVd-7vSV-W3vZ-or5i-KLjX-6MjC-JYGyEJ LV Write Access read/write LV Status available # open 0 LV Size 24,00 GiB Current LE 6144 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:0 --- Logical volume --- LV Name /dev/Esp-Virt/Marie-DHCP-swap VG Name Esp-Virt LV UUID oJhOii-Ji2Z-ZwWe-YQ37-6MRd-kA1u-cCND34 LV Write Access read/write LV Status available # open 0 LV Size 256,00 MiB Current LE 64 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:1 --- Logical volume --- LV Name /dev/Esp-Virt/Marie-DHCP-disk VG Name Esp-Virt LV UUID dGA6fg-Py5q-QHZM-0CTL-N03s-v4KV-DrQ3f7 LV Write Access read/write LV Status available # open 0 LV Size 4,00 GiB Current LE 1024 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:2 Then I edited /etc/xen-tools/xen-tools.conf to suit my wishes: root@debian:/dev# grep -E -v ''^(#|$)'' /etc/xen-tools/xen-tools.conf lvm = Esp-Virt install-method = debootstrap size = 4Gb # Disk image size. memory = 256Mb # Memory size swap = 256Mb # Swap size fs = ext3 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default distribution to install. image = sparse # Specify sparse vs. full disk images. gateway = 192.168.1.1 netmask = 255.255.255.0 broadcast = 192.168.1.255 passwd = 1 accounts = 1 kernel = /boot/vmlinuz-`uname -r` initrd = /boot/initrd.img-`uname -r` mirror = `xt-guess-suite-and-mirror --mirror` ext3_options = noatime,nodiratime,errors=remount-ro ext2_options = noatime,nodiratime,errors=remount-ro xfs_options = defaults reiserfs_options = defaults btrfs_options = defaults serial_device = hvc0 #default disk_device = xvda #default I ''ve created my virtual machines : root@debian:/home/dorian# xen-create-image --hostname=Marie-DHCP --ip=192.168.1.3 --passwd --force General Information -------------------- Hostname : Marie-DHCP Distribution : squeeze Mirror : ftp://ftp.fr.debian.org/debian/ Partitions : swap 256Mb (swap) / 4Gb (ext3) Image type : full Memory size : 256Mb Kernel path : /boot/vmlinuz-2.6.32-5-xen-amd64 Initrd path : /boot/initrd.img-2.6.32-5-xen-amd64 Networking Information ---------------------- IP Address 1 : 192.168.1.3 [MAC: 00:16:3E:BF:18:50] Netmask : 255.255.255.0 Broadcast : 192.168.1.255 Gateway : 192.168.1.1 Removing /dev/Esp-Virt/Marie-DHCP-swap - since we''re forcing the install Removing /dev/Esp-Virt/Marie-DHCP-disk - since we''re forcing the install Creating swap on /dev/Esp-Virt/Marie-DHCP-swap Done Creating ext3 filesystem on /dev/Esp-Virt/Marie-DHCP-disk Done Installation method: debootstrap Done Running hooks Done No role scripts were specified. Skipping Creating Xen configuration file Done Setting up root password Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully All done Logfile produced at: /var/log/xen-tools/Marie-DHCP.log Installation Summary --------------------- Hostname : Marie-DHCP Distribution : squeeze IP-Address(es) : 192.168.1.3 RSA Fingerprint : 25:46:6c:76:3a:39:fc:7a:bb:7b:31:33:9c:7f:30:09 Root Password : N/A A # locate Marie shows: root@debian:/home/dorian/Téléchargements/xen-4.2.1# locate Marie /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-disk /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-swap /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--disk /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--swap /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--disk /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--swap /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-disk/b254:2 /dev/.udev/links/Esp-Virt\x2fMarie-DHCP-swap/b254:1 /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--disk/b254:2 /dev/.udev/links/disk\x2fby-id\x2fdm-name-Esp--Virt-Marie--DHCP--swap/b254:1 /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--disk/b254:2 /dev/.udev/links/mapper\x2fEsp--Virt-Marie--DHCP--swap/b254:1 /dev/Esp-Virt/Marie-DHCP-disk /dev/Esp-Virt/Marie-DHCP-swap /dev/disk/by-id/dm-name-Esp--Virt-Marie--DHCP--disk /dev/disk/by-id/dm-name-Esp--Virt-Marie--DHCP--swap /dev/mapper/Esp--Virt-M arie--DHCP--disk /dev/mapper/Esp--Virt-Marie--DHCP--swap /etc/xen/Marie-DHCP.cfg /etc/xen/Marie-DHCP.cfg.ancien /usr/share/zoneinfo/Europe/Mariehamn /usr/share/zoneinfo/posix/Europe/Mariehamn /usr/share/zoneinfo/right/Europe/Mariehamn /var/log/xen-tools/Marie-DHCP.0.log /var/log/xen-tools/Marie-DHCP.1.log /var/log/xen-tools/Marie-DHCP.2.log /var/log/xen-tools/Marie-DHCP.log root@debian:/home/dorian/Téléchargements/xen-4.2.1# ls /dev/Esp-Virt/ Marie-DHCP-disk Marie-DHCP-swap Vol1 I did configure the /etc/network/interfaces file like this (conversaly xen-create image... indicated ip=192.168.1.3 # The loopback network interface auto lo iface lo inet loopback auto xenbr0 iface xenbr0 inet dhcp bridge_ports eth0 #bridge_stp on #bridge_maxwait 0 #bridge_fd 0 whereas /// root@debian:/dev# grep -E -v ''^(#|$)'' /etc/xen/xend-config.sxp // NOT CONFIGURED AS PER THE DEBIAN SQUEEZE ADVICE (vif-script vif-bridge) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '''') So, I ''ve got this interfaces showing up. Vif x.x should appear after xm create Virtual-guest.cfg, I guess (which in my case is MArie-DHCP) root@debian:/home/dorian# brctl show bridge name bridge id STP enabled interfaces pan0 8000.000000000000 no xenbr0 8000.002655c46159 no eth0 Now, when I try to boot my DomU guest here is the error, which many research on the web didn''t show up thje solution. however: Step 1: root@debian:/dev# xm create Marie-DHCP.cfg Using config file "/etc/xen/Marie-DHCP.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working.>>>> I watched in the hotplug.logroot@debian:/dev# more /var/log/xen/xen-hotplug.log xenstore-read: couldn''t read path backend/vbd/2/51714/params xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-read: couldn''t read path backend/vbd/2/51713/params xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-write: could not write path backend/vbd/2/51713/hotplug-error xenstore-write: could not write path backend/vif/2/0/hotplug-error In the meantime of weeks in searching how to get around. I found the following usefull information:http://wiki.xen.org/wiki/XenCommonProblems#Xen_complains_about_.22hotplug_scripts_not_working.22 "This problem is often related to udev. Do you have udev installed? Is your udev the correct/supported version? "This error usually has more information in the end revealing the real reason.. for example: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. "This problem is often caused by not having "xen-netback" driver loaded in dom0 kernel. "The hotplug scripts are located in /etc/xen/scripts by default, and are labeled with the prefix vif-*. Those "scripts log to /var/log/xen/xen-hotplug.log, and more detailed information can be found there.">>I know I installed udev, prior to install xen from source since hotplug plugin doesn''t exists/shows up.I''ve been trying to locate xen-netback driver. root@debian:/dev# cat /proc/modules | grep xen xen_evtchn 4355 1 - Live 0xffffffffa04d7000 xenfs 9616 1 - Live 0xffffffffa04ce000>>These modules seem .ok but following are missing. Probably the source of the issueBut since this call : http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Update_modules The following modules may be required:STep 2 xen-evtchn xen-gntdev >>> missing >>>> I think the error comes from xen-netback >>>missing this missing drivers xen-blkback >>>missing xenfs blktap >>> missing |Are they missing from Xen 4.2.1 from source Or did they don''t install properly (something like exit with errors? I''m willing to re install with detailed info if needed...). On the same wiki-page are numerous important advices , but often I don''t know where to look for the files (which directory + name)and/or the commands to use to edit except using nano.. e.g. Git (what''is it , how use it?? but''i''ll google through) I don''t know from which directory input I ''ve to make the substantial intalls provided by the last mentionned adress above. What am i missing for going through Step 2, I mean be able to launch my virtual machine where find it? Which command help out? I hope I''v"e been clear. since too many research pull me with confused through all the topic/issue links. So I summarize: Will I be able to resolve the xm create vm.cfg which I encounter as an issue. How do I get the xen- modules installed and running? I appreciate your help in solving this issue. Also please provide me with the commands since from th elinks I cannot solve it and take a risk to break the system. Sorry for the long thread!! Many thanks in advance Dorian Carpentier de Changy dechangydorian@yahoo.fr 0497/623 249 -------------------------- Rue Camille Lemonnier 22 1050 Bruxelles _______________________________________________ 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
On Tue, 2013-04-30 at 13:58 +0100, Dorian wrote:> Hello. > > > First of all I ''m pretty new to Linux and this is my first install of > Xen. So don''t mind me wrong if sometimes I don''t know which command is > appropriate to fetch results. > > > I''m running a new Debian Squeeze release 2.6.32-5-xen-amd64 with > minimal components. I''ve been going through install of Xen as per the > documentation for the 4.2.1 release and did so by source. However I > installed (make install & make world) from > within /user/Download/xen4.2.1, I don''t know if that is a good/bad > idea?If you are new to this then I would strongly recommend you use the version of Xen which is packaged in Debian. Likewise for the kernel. [...]> Vif x.x should appear after xm create Virtual-guest.cfg, I guess > (which in my case is MArie-DHCP) > > root@debian:/home/dorian# brctl show > bridge name bridge id STP enabled interfaces > pan0 8000.000000000000 no > xenbr0 8000.002655c46159 no eth0Does vifx.y exist in the "ifconfig -a" output?> "This problem is often related to udev. Do you have udev installed? Is > your udev the correct/supported version? "This error usually has more > information in the end revealing the real reason.. for example: > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.> "This problem is often caused by not having "xen-netback" driver > loaded in dom0 kernel. > "The hotplug scripts are located in /etc/xen/scripts by default, and > are labeled with the prefix vif-*. Those "scripts log > to /var/log/xen/xen-hotplug.log, and more detailed information can be > found there." > >>>>>>>>>I know I installed udev, prior to install xen from source > since hotplug plugin doesn''t exists/shows up.Do you have Xen rules file in /et/udev/rules.d/foo? e.g. # head -n2 /etc/udev/rules.d/xen-backend.rules SUBSYSTEM=="xen-backend", KERNEL=="tap*", ENV{UDEV_CALL}="1", RUN +="/etc/xen/scripts/blktap $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="v... ...> I''ve been trying to locate xen-netback driver. > root@debian:/dev# cat /proc/modules | grep xen > xen_evtchn 4355 1 - Live 0xffffffffa04d7000 > xenfs 9616 1 - Live 0xffffffffa04ce000Did you try "modprobe xen-netback" ? Or "find /lib/modules -name \*netback\*" in case it was called something else in Squeeze?> >>>>>>These modules seem .ok > But since this call : > http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Update_modules > The following modules may be required:STep 2 > > xen-evtchn > xen-gntdev >>> missing >>>> I think the error comes from > xen-netback >>>missing this missing drivers > xen-blkback >>>missing > xenfs > blktap >>> missing |Are they missing from Xen 4.2.1 from source Or > did they don''t install properly (something like exit with errors? I''m willing to re install > with detailed info if needed...).These modules come from your kernel, not from Xen itself. The -xen flavours of the Debian kernel should have them already (either modular or static). If you built your own kernel then you will need to ensure you enable the relevant option. Ian.
Each reply in bold Char. Thx De : Ian Campbell <Ian.Campbell@citrix.com> À : Dorian <dechangydorian@yahoo.fr> Cc : "xen-users@lists.xen.org" <xen-users@lists.xen.org> Envoyé le : Mardi 30 avril 2013 16h07 Objet : Re: [Xen-users] Unaible to create DomU Guest On Tue, 2013-04-30 at 13:58 +0100, Dorian wrote:> Hello. > > > First of all I ''m pretty new to Linux and this is my first install of > Xen. So don''t mind me wrong if sometimes I don''t know which command is > appropriate to fetch results. > > > I''m running a new Debian Squeeze release 2.6.32-5-xen-amd64 with > minimal components. I''ve been going through install of Xen as per the > documentation for the 4.2.1 release and did so by source. However I > installed (make install & make world) from > within /user/Download/xen4.2.1, I don''t know if that is a good/bad > idea?If you are new to this then I would strongly recommend you use the version of Xen which is packaged in Debian. Likewise for the kernel. [...] I''m not sure what you mean with "version of Xen which is packaged in Debian" when I tried to install with aptitude, I got uncomplete install. From source it looks like correct. On top... of this I can''t google a distro of Debian with Xen included (pre-packaged), if that is what you meant. If so please resume with this practice.... :> Vif x.x should appear after xm create Virtual-guest.cfg, I guess > (which in my case is MArie-DHCP) > > root@debian:/home/dorian# brctl show > bridge name bridge id STP enabled interfaces > pan0 8000.000000000000 no > xenbr0 8000.002655c46159 no eth0Does vifx.y exist in the "ifconfig -a" output? This is the second issue I aim to view in sight. I don''t see it. I have : eth0 lo pan0 wlan0 xenbr0 xenbr0:avahi I can tell that when I launch the guest ( #xm create ), the network "icon" shows an vifx.y device when I slide my mouse over it. Unfortunately , as the guest doesn''t perform the read/write execution and returns recursive error in hotplug.log, it crashes and alert me with "Error: Device 0 (vif) could not be connected. Hotplug scripts not working." This bug is reported in the page > wiki.xen.org/wiki/xenCommonProblems# Problems are quoted below (I put them in bold char)> "This problem is often related to udev. Do you have udev installed? Is > your udev the correct/supported version? "This error usually has more > information in the end revealing the real reason.. for example: > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.> "This problem is often caused by not having "xen-netback" driver > loaded in dom0 kernel. > "The hotplug scripts are located in /etc/xen/scripts by default, and > are labeled with the prefix vif-*. Those "scripts log > to /var/log/xen/xen-hotplug.log, and more detailed information can be > found there." >I know I installed udev, prior to install xen from source > since hotplug plugin doesn''t exists/shows up.Do you have Xen rules file in /et/udev/rules.d/foo? e.g.No file ./foo doesn''t exist. Whereas I have xen-backend.rules xend.rules + 3 other beginin 70-... & z60.. 85-pcm.. # head -n2 /etc/udev/rules.d/xen-backend.rules SUBSYSTEM=="xen-backend", KERNEL=="tap*", ENV{UDEV_CALL}="1", RUN +="/etc/xen/scripts/blktap $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="v... ...> I''ve been trying to locate xen-netback driver. > root@debian:/dev# cat /proc/modules | grep xen > xen_evtchn 4355 1 - Live 0xffffffffa04d7000 > xenfs 9616 1 - Live 0xffffffffa04ce000>>Did you try "modprobe xen-netback" ? Or "find /lib/modules -name >>\*netback\*" in case it was called something else in Squeeze?A locate xen-netback returns NOthing Prompted modprobe xen-netback >> answer: FATAL: Module xen-netback not found. ''(I remind of the former and latter also missing - see below ) How do I get around!? Maybe I''ll never fix it on my own :5 But once @ A TIME> >>>>>>These modules seem .ok > But since this call : > http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs#Update_modules > The following modules may be required:STep 2 > > xen-evtchn > xen-gntdev >>> missing >>>> I think the error comes from > xen-netback >>>missing this missing drivers > xen-blkback >>>missing > xenfs > blktap >>> missing |Are they missing from Xen 4.2.1 from source Or > did they don''t install properly (something like exit with errors? I''m willing to re install > with detailed info if needed...).These modules come from your kernel, not from Xen itself. The -xen flavours of the Debian kernel should have them already (either modular or static). If you built your own kernel then you will need to ensure you enable the relevant option. Is it this you mean that installing xen from source DID NOT install these modules. They are present in the Debian kernel? How come I get a FATAL answer! Again you point out the xen flavour of Debian kernel... Hm kernel 2.6.32-5 is one ? Can you answer this basic and maybe idiot Q by Yes or No? Thx! Hm, sezcondly I''m afraid I won''t build my own kernel - I''ve never read an article on this topic. Looks like too much developer side on either sides. My respect. Final: if these modules should have been packed with the Debian kernel, how will I install them. This is a basic question but for instance an aptitude search xen-netback returns 0. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, 2013-04-30 at 17:15 +0100, Dorian wrote:> > Each reply in bold Char.I don''t see any bold in your reply, because I do not read HTML mail (. Please stick to the customary ">" style of quoting and post only plain text mails. I have gone through and tried to pick out your reply this time.> > I''m running a new Debian Squeeze release 2.6.32-5-xen-amd64 with > > minimal components. I''ve been going through install of Xen as per > the > > documentation for the 4.2.1 release and did so by source. However I > > installed (make install & make world) from > > within /user/Download/xen4.2.1, I don''t know if that is a good/bad > > idea? > > If you are new to this then I would strongly recommend you use the > version of Xen which is packaged in Debian. Likewise for the kernel. > [...] > > > I''m not sure what you mean with "version of Xen which is packaged in > Debian"Debian contains binary packages of Xen: http://packages.debian.org/search?keywords=xen http://wiki.debian.org/Xen http://wiki.xen.org/wiki/Category:Debian> when I tried to install with aptitude, I got uncomplete install. From > source it looks like correct. > On top... of this I can''t google a distro of Debian with Xen included > (pre-packaged), if that is what you meant. If so please resume with > this practice.... :I''m afraid I cannot parse the above. If you are saying that the Debian packages did not work for you then perhaps this is something to investigate further. The links I gave above contains various tutorials regarding installing Xen on Debian. I really think you would be better off using the binary packages supplied by Debian.> > > > > Vif x.x should appear after xm create Virtual-guest.cfg, I guess > > (which in my case is MArie-DHCP) > > > > root@debian:/home/dorian# brctl show > > bridge name bridge id STP enabled interfaces > > pan0 8000.000000000000 no > > xenbr0 8000.002655c46159 no eth0 > > Does vifx.y exist in the "ifconfig -a" output? > > > This is the second issue I aim to view in sight. I don''t see it. I > have :On second thoughts this could be because the toolstack cleaned up after the failure, so we can''t really tell anything here.> > "This problem is often related to udev. Do you have udev installed? > Is > > your udev the correct/supported version? "This error usually has > more > > information in the end revealing the real reason.. for example: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working. > > > > "This problem is often caused by not having "xen-netback" driver > > loaded in dom0 kernel. > > "The hotplug scripts are located in /etc/xen/scripts by default, and > > are labeled with the prefix vif-*. Those "scripts log > > to /var/log/xen/xen-hotplug.log, and more detailed information can > be > > found there." > >I know I installed udev, prior to install xen from source > > since hotplug plugin doesn''t exists/shows up. > > > Do you have Xen rules file in /et/udev/rules.d/foo? > > e.g. No file ./foo doesn''t exist.Sorry, foo is usually used as a placeholder for "something".> Whereas I have > xen-backend.rules > xend.rules + 3 other beginin 70-... & z60.. 85-pcm.. > > # head -n2 /etc/udev/rules.d/xen-backend.rules > SUBSYSTEM=="xen-backend", KERNEL=="tap*", ENV{UDEV_CALL}="1", RUN > +="/etc/xen/scripts/blktap $env{ACTION}" > SUBSYSTEM=="xen-backend", KERNEL=="v... > ... > > > I''ve been trying to locate xen-netback driver. > > root@debian:/dev# cat /proc/modules | grep xen > > xen_evtchn 4355 1 - Live 0xffffffffa04d7000 > > xenfs 9616 1 - Live 0xffffffffa04ce000 > > >>Did you try "modprobe xen-netback" ? Or "find /lib/modules -name > >>\*netback\*" in case it was called something else in Squeeze? > > A locate xen-netback returns NOthingThe reason I suggested *netback* and not *xen-netback* is the in some kernels the module is just called "netback" and not "xen-netback", I don''t recall if this is the case for Debian Squeeze or not. If you use the Debian packages then you won''t have this sort of problem I think.> These modules come from your kernel, not from Xen itself. The -xen > flavours of the Debian kernel should have them already (either modular > or static). If you built your own kernel then you will need to ensure > you enable the relevant option. > > Is it this you mean that installing xen from source DID NOT install > these modules. They are present in the Debian kernel?That is correct. The backend drivers are part of the kernel and not part of the hypervisor.> How come I get a FATAL answer! Again you point out the xen flavour of > Debian kernel... Hm kernel 2.6.32-5 is one ?No, you need the flavour with -xen in its name. -xen-686-bigmem or -xen-amd64 IIRC. However if you are already running under Xen and you don''t build your own kernel then you have surely found the correct kernel. Ian.
Sorry I forgot to add the mailing list. So from the output is there something may be pointing to something could go broken during an install? befor e make world and make install... root@debian:/home/dorian/Downloads/xen-4.2.1# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking for bison... /usr/bin/bison checking for flex... /usr/bin/flex checking for perl... /usr/bin/perl checking for ocamlc... ocamlc OCaml version is 3.11.2 OCaml library path is /usr/lib/ocaml checking for ocamlopt... ocamlopt checking for ocamlc.opt... no checking for ocamlopt.opt... no checking for ocaml... ocaml checking for ocamldep... ocamldep checking for ocamlmktop... ocamlmktop checking for ocamlmklib... ocamlmklib checking for ocamldoc... ocamldoc checking for ocamlbuild... ocamlbuild checking for bash... /bin/bash checking for python... /usr/bin/python checking for python version >= 2.3 ... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for python-config... /usr/bin/python-config checking Python.h usability... yes checking Python.h presence... yes checking for Python.h... yes checking for PyArg_ParseTuple in -lpython2.6... yes checking for xgettext... /usr/bin/xgettext checking for as86... /usr/bin/as86 checking for ld86... /usr/bin/ld86 checking for bcc... /usr/bin/bcc checking for iasl... /usr/bin/iasl checking uuid/uuid.h usability... yes checking uuid/uuid.h presence... yes checking for uuid/uuid.h... yes checking for uuid_clear in -luuid... yes checking uuid.h usability... no checking uuid.h presence... no checking for uuid.h... no checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for clear in -lcurses... yes checking ncurses.h usability... yes checking ncurses.h presence... yes checking for ncurses.h... yes checking for clear in -lncurses... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for glib... yes checking bzlib.h usability... no checking bzlib.h presence... no checking for bzlib.h... no checking lzma.h usability... no checking lzma.h presence... no checking for lzma.h... no checking lzo/lzo1x.h usability... no checking lzo/lzo1x.h presence... no checking for lzo/lzo1x.h... no checking for io_setup in -laio... yes checking for MD5 in -lcrypto... yes checking ext2fs/ext2fs.h usability... no checking ext2fs/ext2fs.h presence... no checking for ext2fs/ext2fs.h... no checking ext4fs/ext2fs.h usability... no checking ext4fs/ext2fs.h presence... no checking for ext4fs/ext2fs.h... no checking for gcry_md_hash_buffer in -lgcrypt... no checking for pthread flag... -pthread checking libutil.h usability... yes checking libutil.h presence... yes checking for libutil.h... yes checking for openpty et al... -lutil checking for yajl_alloc in -lyajl... yes checking for deflateCopy in -lz... yes checking for libiconv_open in -liconv... no checking yajl/yajl_version.h usability... no checking yajl/yajl_version.h presence... no checking for yajl/yajl_version.h... no configure: creating ./config.status config.status: creating ../config/Tools.mk config.status: creating config.h config.status: config.h is unchanged Thx De : Ian Campbell <Ian.Campbell@citrix.com> À : Dorian <dechangydorian@yahoo.fr> Envoyé le : Mercredi 1 mai 2013 11h03 Objet : Re: [Xen-users] Unaible to run DomU Guest Gah, please keep the conversation on the list, I failed to notice that your other reply was private too. On Wed, 2013-05-01 at 10:01 +0100, Dorian wrote:> > Hello > > > Do you see something broken, here? >... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users