Dorian
2013-Sep-12 11:24 UTC
Get Network on DomU + Parsing multiple Guest Domains with lvm usage
Hi there I''m in the process of testing Xen 4.0 on §Debian Squeeze install. I''ve a working Xen Hypervisor on Debian Squeeze 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 I set up a lvm partition. root@debian:/home/dorian# vgdisplay --- Volume group --- VG Name Esp-Virt System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 25 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 29,29 GiB PE Size 4,00 MiB Total PE 7499 Alloc PE / Size 1152 / 4,50 GiB Free PE / Size 6347 / 24,79 GiB VG UUID emvcGa-xLrC-mLeN-UfGp-3Lzd-eIiq-7wM02w I installed 2 Debian squeeze volumes with debootstrap and xm created them. Log in is succesfull. I installed 1 Ubuntu Lucid volume, but creating fails using root@debian:/home/dorian# xm create Machin-bizarre-ubu.net.cfg (same command as for the Debian images) Error: Unable to open config file: Machin-bizarre-ubu.net.cfg Usage: xm create <ConfigFile> [options] [vars] However my lv looks like --- Logical volume --- LV Name /dev/Esp-Virt/Machin-bizarre.ubu.net-swap VG Name Esp-Virt LV UUID UL0AMi-IMCt-qzz8-REUd-emse-J2NR-8RiKb6 LV Write Access read/write LV Status available # open 0 LV Size 512,00 MiB Current LE 128 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:2 --- Logical volume --- LV Name /dev/Esp-Virt/Machin-bizarre.ubu.net-disk VG Name Esp-Virt LV UUID QbOA2D-NeRp-jeGl-5OA3-GBd8-FScw-F32slF 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:5 Is there anything special regarding creating Ubuntu image? Cc the llogical volumes, following the beginners tutorial, one tell to create pv then vg and, might I be misleaded, lv. I made at first thought multiple lv io to use seperate lv per DomU created but the command to create DomU doesn''t take argument to bind the DomU to the lv (I had 3 lv like /dev/Esp-Virt/Vol1 - Vol2 & Vol3) Using all the extent of the vg, When I went to install with debootstrap I had no space as a consequence. So I deleted the Vol1,2 &3. Recalling what lvcreate stands for, I remain dubious (what stands it for if Icannot bind to it? I only suppose lvremove stands for destroying the DomU - Machin-bizarre.ubu.net-disk and swap for instance)? CC debootstrap, does it physically install a cd image on a sub-directory? How can I find it out (install dir)? ''cause for each newly created DomU I ''ve to take usage of the internet and/or exploit my / ( maybe the lvm volmuewhere I created a vg, to get it simple) partition, increasing the occupied storage capcity. Can I use a previous debootstrap image and install the extra guests from there? Maybe other caveats , but I assume you know better how I summarise it. Now about my network: My hypervisor is configured with a working bridge > oot@debian:/home/dorian# ifconfig eth0 Link encap:Ethernet HWaddr 00:26:55:c4:61:59 adr inet6: fe80::226:55ff:fec4:6159/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:527 errors:0 dropped:0 overruns:0 frame:0 TX packets:71 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:158499 (154.7 KiB) TX bytes:10997 (10.7 KiB) Interruption:17 lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B) vif1.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:21 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:2 overruns:0 carrier:0 collisions:0 lg file transmission:32 RX bytes:6888 (6.7 KiB) TX bytes:4411 (4.3 KiB) vif2.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:21 errors:0 dropped:2 overruns:0 carrier:0 collisions:0 lg file transmission:32 RX bytes:2952 (2.8 KiB) TX bytes:4753 (4.6 KiB) xenbr0 Link encap:Ethernet HWaddr 00:26:55:c4:61:59 inet adr:192.168.1.3 Bcast:192.168.1.255 Masque:255.255.255.0 adr inet6: fe80::226:55ff:fec4:6159/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:522 errors:0 dropped:0 overruns:0 frame:0 TX packets:54 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:150151 (146.6 KiB) TX bytes:7962 (7.7 KiB)>> brctl showbridge name bridge id STP enabled interfaces pan0 8000.feffffffffff no vif1.0 vif2.0 xenbr0 8000.002655c46159 no eth0 From the DomU guest I got the following and no internet: xm console Machin-chose-cpt.net [ 1737.324143] Setting capacity to 8388608 [ 1737.326271] Setting capacity to 1048576 [ 1737.327052] Setting capacity to 8388608 [ 1737.373784] Setting capacity to 1048576 root@Machin-chose-cpt:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3e:5f:81:78 inet6 addr: fe80::216:3eff:fe5f:8178/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8262 (8.0 KiB) TX bytes:17568 (17.1 KiB) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) # grep -E -v ''^(#)'' /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp I''ve to inform that upon creation of this DomU, the system advices about Networking will not work since there is a missing network-script or vif-script. Here is what I have in root@debian:/home/dorian# grep -E -v ^# /etc/xen/xend-config.sxp (vif-script vif-bridge) I''m not sure whether I must add (network-script network-bridge) and what I have to configure against these stanzas. Adding and/or removing any of these stanzas lead to the same berhaviour-warning. I don''t find any clue on this with googling around. I know for sure that this xend-config.sxp must be configured, isn''t it? I remind that upon creating the debootstrap I image I passed --dhcp as a network cfg. So for so far how will I be able to network my Dom guest? * Thanks you for enlightning my horizon. 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
Alexandre Kouznetsov
2013-Sep-12 19:15 UTC
Re: Get Network on DomU + Parsing multiple Guest Domains with lvm usage
Hello. El 12/09/13 06:24, Dorian escribió:> I''m in the process of testing Xen 4.0 on §Debian Squeeze install. > I''ve a working Xen Hypervisor on Debian Squeeze > [...] > > I installed 2 Debian squeeze volumes with debootstrap and xm created > them. Log in is succesfull. > I installed 1 Ubuntu Lucid volume, but creating fails using > root@debian:/home/dorian# xm create Machin-bizarre-ubu.net.cfg (same > command as for the Debian images) > Error: Unable to open config file: Machin-bizarre-ubu.net.cfg > Usage: xm create <ConfigFile> [options] [vars]xm complains that it can not read the config file. This means, between other things, that it did not parsed it yet, so whatever happens with the storage is irrelevant on this stage. Make sure Machin-bizarre-ubu.net.cfg is the correct config file name. Remember that the file names in Linux are case-sensitive.> Is there anything special regarding creating Ubuntu image?No, except that usually you use pygrub as the boot loader with Ubuntu, while in case of Debian DomU sometines it''s easer to specify the kernel and initrd directly, it will load them from Dom0 filesystem.> Cc the llogical volumes, following the beginners tutorial, one tell to > create pv then vg and, might I be misleaded, lv. I made at first thought > multiple lv io to use seperate lv per DomU created but the command to > create DomU doesn''t take argument to bind the DomU to the lv (I had 3 > lv like /dev/Esp-Virt/Vol1 - Vol2 & Vol3) Using all the extent of the > vg, When I went to install with debootstrap I had no space as a > consequence. So I deleted the Vol1,2 &3. Recalling what lvcreate stands > for, I remain dubious (what stands it for if Icannot bind to it? I only > suppose lvremove stands for destroying the DomU - > Machin-bizarre.ubu.net-disk and swap for instance)?Sorry, your explanation is little bit confusing, but I still hope I can answer this. While using LVM as storage for DomUs, as initial setup you usually define some block device(s) as one (or several) Physical Volume, then create a Volume Group and you are done. After that you create/remove/resize Logical Volumes as need them. In case of Xen over Debian, I would recommend to use xen-tools instead of debootstrap directly. I can also create the necessary Logical volumes an generate a nice config file.> CC debootstrap, does it physically install a cd image on a > sub-directory? How can I find it out (install dir)? ''cause for each > newly created DomU I ''ve to take usage of the internet and/or exploit my > / ( maybe the lvm volmuewhere I created a vg, to get it simple) > partition, increasing the occupied storage capcity. Can I use a previous > debootstrap image and install the extra guests from there? Maybe other > caveats , but I assume you know better how I summarise it.debootstrap does not need to use a CD image (unless it''s specified as Debian Repository), the most common way is to make it pull packages from network. It does store a copy of the downloaded packages within the target directory tree. https://wiki.debian.org/Debootstrap You can deploy Debian DomU from a master image instead of debootstrapping each of them. Personally, I tried that but then found that xen-tools if the easiest and most flexible way to deploy machines. The master image became outdated soon enough to justify a new deploy each time. Please consider to board different questions in different threads. Greetings. -- Alexandre Kouznetsov
Hello again. El 12/09/13 06:24, Dorian escribió:> Now about my network: > My hypervisor is configured with a working bridge > [...] > >> brctl show > bridge name bridge id STP enabled interfaces > pan0 8000.feffffffffff no vif1.0 > vif2.0 > xenbr0 8000.002655c46159 no eth0You VM''s network seems to be attached to a pan0, and there is no physical interface to the outside world in that bridge. If you mean your VM''s to have a network interface within the same network as your Dom0''s eth0, change their''s config files. Make them to be attached to xenbr0.> From the DomU guest I got the following and no internet: > xm console Machin-chose-cpt.net > [ 1737.324143] Setting capacity to 8388608 > [ 1737.326271] Setting capacity to 1048576 > [ 1737.327052] Setting capacity to 8388608 > [ 1737.373784] Setting capacity to 1048576 > > root@Machin-chose-cpt:~# ifconfig > eth0 Link encap:Ethernet HWaddr 00:16:3e:5f:81:78 > inet6 addr: fe80::216:3eff:fe5f:8178/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:40 errors:0 dropped:0 overruns:0 frame:0 > TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:8262 (8.0 KiB) TX bytes:17568 (17.1 KiB) > Interrupt:19 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > # grep -E -v ''^(#)'' /etc/network/interfaces > auto lo > iface lo inet loopback > auto eth0 > iface eth0 inet dhcpUnless one your VM''s have a DHCP server, this won''t work aether. If you attach you VM to xenbr0 AND there is a working DHCP server on your network, nothing need to be changed here, your VM will get a address form you regular DHCP server.> I''ve to inform that upon creation of this DomU, the system advices about > Networking will not work since there is a missing network-script or > vif-script. > Here is what I have in root@debian:/home/dorian# > grep -E -v ^# /etc/xen/xend-config.sxp > > (vif-script vif-bridge)A common approach, at least on Debian, is to drop Xen''s stock network scripts and create the necessary bridges by OS''s means, from /etc/network/interfaces. This would give you more solid and predictible setup. There are plenty of examples in this list''s archive. Greetings. -- Alexandre Kouznetsov