Hello! I''m sort of new to Xen but took some time to read around forums, wikis and official documentation. I''m experiencing some problems with the latest Xen version 3.1. The whole thing I''m currently working is supposed to support some old OS-es on newer hardware, ofc by using virtualization. * first ( i think it''s related with the bootloader ) - dom0 is 64bit / k 2.6 - domU is 32bit/ k 2.4 I''m creating the image using: #xen-create-image --hostname=vm2.bla.com --size=2G --swap=256 --ide --ip=10.1.27.202 --netmask=255.255.224.0 --gateway=10.1.0.254--dir=/dat a/xen-vms --memory=256Mb --arch=i386 --kernel=/boot/xen-guests-kernels/vmlinuz-2 .4.26-1-686-smp --initrd=/boot/xen-guests-kernels/initrd.img- 2.4.26-1-686-smp -- copy=/data/tmp/somesytemimage/ --passwd # xm create /etc/xen/vm2.bla.com.cfg Using config file "/etc/xen/vm2.bla.cfg". Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') In xend.log I get: [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.constructDomain [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Balloon: 557796 KiB free; need 2048; done. [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Adding Domain: 18 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.initDomain: 18 256 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) _initDomain:shadow_memory=0x0, memory_static_max=0x10000000, memory_static_min=0x0. [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Balloon: 557788 KiB free; need 262144; done. [2007-07-25 13:13:42 3152] INFO (__init__:1072) buildDomain os=linux dom=18 vcpus=1 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) domid = 18 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) memsize = 256 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) image = /boot/vmlinuz- 2.4.26-1-686-smp [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) store_evtchn = 1 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) console_evtchn = 2 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) cmdline = root=/dev/hda1 ro [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) ramdisk = /boot/initrd.img- 2.4.26-1-686-smp [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) vcpus = 1 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) features [2007-07-25 13:13:42 3152] ERROR (__init__:1072) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1517, in _initDomain channel_details = self.image.createImage() File "/usr/lib64/python/xen/xend/image.py", line 112, in createImage return self.createDomain() File "/usr/lib64/python/xen/xend/image.py", line 131, in createDomain result = self.buildDomain() File "/usr/lib64/python/xen/xend/image.py", line 517, in buildDomain return LinuxImageHandler.buildDomain(self) File "/usr/lib64/python/xen/xend/image.py", line 215, in buildDomain features = self.vm.getFeatures()) Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') [2007-07-25 13:13:42 3152] ERROR (__init__:1072) VM start failed Traceback (most recent call last): File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 396, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1543, in _initDomain raise VmError(str(exn)) VmError: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=18 [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(18) [2007-07-25 13:13:42 3152] ERROR (__init__:1072) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 81, in create vm.start() File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 396, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1543, in _initDomain raise VmError(str(exn)) VmError: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=None [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(None) vm2.bla.com cfg is: kernel = ''/boot/vmlinuz-2.4.26-1-686-smp'' ramdisk = ''/boot/initrd.img-2.4.26-1-686-smp'' memory = ''256'' root = ''/dev/hda1 ro'' disk = [ ''file:/data/xen-vms/domains/cagemove1- vm2.auctionwatch.com/disk.img,hda1,w'', ''file:/data/xen-vms/domains/cagemove1-vm2.auctionwatch.com/swap.img,hda2,w'' ] name = ''vm2.bla.com'' vif = [ ''ip=10.1.27.202'' ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' * second problem is related to networking - each time i start network-bridge dom0 losses all it''s networking. As far as I''ve managed to track so far the peth0 doesn''t get setup-ed correctly. I need to dig deeper on this one but wondering if someone having a similar setup managed to find out a solution. I''m using Debian Etch 64bit running on a IBM x3550 machine ( quad xeon,4G RAM, VT support ) and the binary 3.1 package from xensource Thanks! -- + Lorin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Lorin pravi:> * second problem is related to networking - each time i start > network-bridge dom0 losses all it''s networking. As far as I''ve managed > to track so far > the peth0 doesn''t get setup-ed correctly. I need to dig deeper on this > one but wondering if someone > having a similar setup managed to find out a solution. > > I''m using Debian Etch 64bit running on a IBM x3550 machine ( quad > xeon,4G RAM, VT support ) and the binary 3.1 package from xensourceI had a similar problem and it turned out to be a bug in the bnx2 network driver used in Dom0. IIRC I got the new driver on Broadcomm website. D. --------------------------------------------------------------------- Danilo Godec danilo.godec@agenda.si --------------------------------------------------------------------- --------------------------------------------------------------------- Agenda Open Systems Slovenija, Europe Cesta Pohorskega bataljona 49, SI 2000 Maribor tel# +386 2 421 61 31 http://www.agenda.si/ fax# +386 2 421 61 41 --------------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Goldstone
2007-Jul-26 08:05 UTC
Re: [Xen-users] xen 3.1 and 32bit guests in 64bit dom0
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1st question: Is the domU kernel actually a Xen kernel? By the look of that error, I''d guess that it isn''t, especially as normally Xen kernels have -xen in them somewhere, and yours ends in -smp. You need to have a Xen kernel to do PV, or you have to use HVM. 2nd question: If it is a Xen kernel, what version of Xen was that 2.4 kernel compiled for? In my experience, both dom0 and domU have to be for Xen 3.1 in order to mix 32 bit with 64. 3rd question: If Danilo Godec''s suggestion about the NIC driver doesn''t work, could you give us some more details about your networking setup (ie NIC make/model, Bonding, VLANs etc)? Hope this helps. Martin Lorin wrote:> Hello! > > I''m sort of new to Xen but took some time to read around forums, wikis and > official documentation. I''m experiencing > some problems with the latest Xen version 3.1. The whole thing I''m > currently > working is supposed to support some old OS-es on newer > hardware, ofc by using virtualization. > > > * first ( i think it''s related with the bootloader ) > - dom0 is 64bit / k 2.6 > - domU is 32bit/ k 2.4 > > I''m creating the image using: > #xen-create-image --hostname=vm2.bla.com --size=2G --swap=256 > --ide --ip=10.1.27.202 --netmask=255.255.224.0 > --gateway=10.1.0.254--dir=/dat > a/xen-vms --memory=256Mb --arch=i386 > --kernel=/boot/xen-guests-kernels/vmlinuz-2 > .4.26-1-686-smp --initrd=/boot/xen-guests-kernels/initrd.img- > 2.4.26-1-686-smp -- > copy=/data/tmp/somesytemimage/ --passwd > > > # xm create /etc/xen/vm2.bla.com.cfg > Using config file "/etc/xen/vm2.bla.cfg". > Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') > > In xend.log I get: > > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) > XendDomainInfo.constructDomain > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Balloon: 557796 KiB free; > need 2048; done. > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Adding Domain: 18 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.initDomain: > 18 256 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) > _initDomain:shadow_memory=0x0, memory_static_max=0x10000000, > memory_static_min=0x0. > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Balloon: 557788 KiB free; > need 262144; done. > [2007-07-25 13:13:42 3152] INFO (__init__:1072) buildDomain os=linux dom=18 > vcpus=1 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) domid = 18 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) memsize = 256 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) image = /boot/vmlinuz- > 2.4.26-1-686-smp > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) store_evtchn = 1 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) console_evtchn = 2 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) cmdline > root=/dev/hda1 ro > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) ramdisk > /boot/initrd.img- > 2.4.26-1-686-smp > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) vcpus = 1 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) features > [2007-07-25 13:13:42 3152] ERROR (__init__:1072) XendDomainInfo.initDomain: > exception occurred > Traceback (most recent call last): > File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1517, in > _initDomain channel_details = self.image.createImage() > File "/usr/lib64/python/xen/xend/image.py", line 112, in createImage return > self.createDomain() > File "/usr/lib64/python/xen/xend/image.py", line 131, in createDomain > result > = self.buildDomain() > File "/usr/lib64/python/xen/xend/image.py", line 517, in buildDomain return > LinuxImageHandler.buildDomain(self) > File "/usr/lib64/python/xen/xend/image.py", line 215, in buildDomain > features = self.vm.getFeatures()) > Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') > [2007-07-25 13:13:42 3152] ERROR (__init__:1072) VM start failed > Traceback (most recent call last): > File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 396, in start > XendTask.log_progress(31, 60, self._initDomain) > File "/usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress > retval = func(*args, **kwds) > File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1543, in > _initDomain raise VmError(str(exn)) > VmError: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroy: > domid=18 > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) > XendDomainInfo.destroyDomain(18) > [2007-07-25 13:13:42 3152] ERROR (__init__:1072) Domain construction failed > Traceback (most recent call last): > File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 81, in create > vm.start() > File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 396, in start > XendTask.log_progress(31, 60, self._initDomain) > File "/usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress > retval = func(*args, **kwds) > File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1543, in > _initDomain raise VmError(str(exn)) > VmError: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroy: > domid=None > [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) > XendDomainInfo.destroyDomain(None) > > vm2.bla.com cfg is: > kernel = ''/boot/vmlinuz-2.4.26-1-686-smp'' > ramdisk = ''/boot/initrd.img-2.4.26-1-686-smp'' > memory = ''256'' > root = ''/dev/hda1 ro'' > disk = [ ''file:/data/xen-vms/domains/cagemove1- > vm2.auctionwatch.com/disk.img,hda1,w'', > ''file:/data/xen-vms/domains/cagemove1-vm2.auctionwatch.com/swap.img,hda2,w'' > ] > name = ''vm2.bla.com'' > > vif = [ ''ip=10.1.27.202'' ] > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > > * second problem is related to networking - each time i start > network-bridge > dom0 losses all it''s networking. As far as I''ve managed to track so far > the peth0 doesn''t get setup-ed correctly. I need to dig deeper on this > one but wondering if someone > having a similar setup managed to find out a solution. > > I''m using Debian Etch 64bit running on a IBM x3550 machine ( quad xeon,4G > RAM, VT support ) and the binary 3.1 package from xensource > > > Thanks! > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGqFXaRnwIDhcMR9MRAihqAJ0cuqFnsCGuUQvqQty6DyUQ/N7PwgCdFv6K DXdremp+wkX7EWY5PcARQMM=ktUW -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/26/07, Danilo Godec <danilo.godec@agenda.si> wrote:> Lorin pravi: > > > * second problem is related to networking - each time i start > > network-bridge dom0 losses all it''s networking. As far as I''ve managed > > to track so far > > the peth0 doesn''t get setup-ed correctly. I need to dig deeper on this > > one but wondering if someone > > having a similar setup managed to find out a solution. > > > > I''m using Debian Etch 64bit running on a IBM x3550 machine ( quad > > xeon,4G RAM, VT support ) and the binary 3.1 package from xensource > > I had a similar problem and it turned out to be a bug in the bnx2 > network driver used in Dom0. > > IIRC I got the new driver on Broadcomm website.Figured that out after browsing trough the mailling list archives. Thanks. -- + Lorin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/26/07, Martin Goldstone <m.j.goldstone@isc.keele.ac.uk> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 1st question: Is the domU kernel actually a Xen kernel? By the look of > that error, I''d guess that it isn''t, especially as normally Xen kernels > have -xen in them somewhere, and yours ends in -smp. You need to have a > Xen kernel to do PV, or you have to use HVM.It''s not a Xen kernel but a plain old stock kernel on which I''m supposed to run the VM (application requirements ). I have VT support in the cores so HVM should be enabled from what I''ve read so far . Does it require anything else ? Speaking of PV and HVM the latter is better because it makes use of hardware support right ?> 3rd question: If Danilo Godec''s suggestion about the NIC driver doesn''t > work, could you give us some more details about your networking setup > (ie NIC make/model, Bonding, VLANs etc)?Yeah, it was the bnx2 problem. Thanks a lot! -- + Lorin + Nosce te ciment. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Goldstone
2007-Jul-26 12:32 UTC
Re: [Xen-users] xen 3.1 and 32bit guests in 64bit dom0
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 PV is faster than HVM, but HVM allows unmodified guest OSs, so it''s not a clear cut case for which is better. PV has better performance, but if you have to use a non-Xenified kernel, then I guess your hands are tied (although apparently there is now some domU support in the standard kernel according to kerneltrap.org). As you''ve got hardware support, the only thing you need is to set the config file and disk image up properly. HVM domains boot just like regular systems (they have a BIOS as well), and so require a boot loader in the disk image (I use an image for the entire disk, I don''t know if you can split it up into different files for different partitions with HVM), along with the kernel etc, and in the config file for the domain you need to remove the initrd line, point the kernel line to the hvmloader, change the builder to hvm and add the device modeller etc. You can find an example in /etc/xen/xmexample.hvm in the standard Xen install, or you could use RedHat''s virt-manager/virt-install to configure and install the domain. Hope this helps, Martin Lorin wrote:> On 7/26/07, Martin Goldstone <m.j.goldstone@isc.keele.ac.uk> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> 1st question: Is the domU kernel actually a Xen kernel? By the look of >> that error, I''d guess that it isn''t, especially as normally Xen kernels >> have -xen in them somewhere, and yours ends in -smp. You need to have a >> Xen kernel to do PV, or you have to use HVM. > > It''s not a Xen kernel but a plain old stock kernel on which I''m > supposed to run the VM (application requirements ). > I have VT support in the cores so HVM should be enabled from what I''ve > read so far . Does it require anything else ? > > Speaking of PV and HVM the latter is better because it makes use of > hardware support right ? > >> 3rd question: If Danilo Godec''s suggestion about the NIC driver doesn''t >> work, could you give us some more details about your networking setup >> (ie NIC make/model, Bonding, VLANs etc)? > > Yeah, it was the bnx2 problem. > > Thanks a lot! >-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGqJRlRnwIDhcMR9MRAhezAJ4s8PQ2wyRzAv62hwdC/F4bwECHcACeKyA4 7n6emtvICycdqTRTQXTX8Jw=R+LB -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/26/07, Martin Goldstone <m.j.goldstone@isc.keele.ac.uk> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > PV is faster than HVM, but HVM allows unmodified guest OSs, so it''s not > a clear cut case for which is better. PV has better performance, but if > you have to use a non-Xenified kernel, then I guess your hands are tied > (although apparently there is now some domU support in the standard > kernel according to kerneltrap.org). > > As you''ve got hardware support, the only thing you need is to set the > config file and disk image up properly. HVM domains boot just like > regular systems (they have a BIOS as well), and so require a boot loader > in the disk image (I use an image for the entire disk, I don''t know if > you can split it up into different files for different partitions with > HVM), along with the kernel etc, and in the config file for the domain > you need to remove the initrd line, point the kernel line to the > hvmloader, change the builder to hvm and add the device modeller etc. > You can find an example in /etc/xen/xmexample.hvm in the standard Xen > install, or you could use RedHat''s virt-manager/virt-install to > configure and install the domain. >All clear! If i want to build an image out of a physical machine is there a specific tool besides dd or such ? Any docs on building a HVM image from scratch or an already existing (and running ) physical server ? Thanks!! -- + Lorin + Nosce te ciment. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Goldstone
2007-Jul-26 13:52 UTC
Re: [Xen-users] xen 3.1 and 32bit guests in 64bit dom0
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There are no specific tools I know of besides dd. Just remember to change things like fstab and your ethernet configurations accordingly, as the devices and MACs your using now may be different in a VM (the MAC address will definitely be different for example). Sadly I haven''t got any specific docs I can point you at about building a HVM domain from scratch. A quick search for p2v and xen on Google has a few guides for converting a physical machine to a PV one, but not for HVM. I''ve not attempted it myself either (I''ve been using HVM for Windows machines mainly, and I''ve been doing the install from scratch as I know how picky Windows can be about hardware), but I expect it''d be pretty straight forward. When I do finally try it myself, I''ll endeavour to document the experience if anything strange occurs. Lorin wrote:> > All clear! > If i want to build an image out of a physical machine is there a > specific tool besides dd or such ? > Any docs on building a HVM image from scratch or an already existing > (and running ) physical server ? > > Thanks!! >-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGqKc3RnwIDhcMR9MRAmS1AKCFtVQYoeczL9p2MbbQytZOtPuIIQCgogz4 7wyXPTI/jtHhBrClUwBB1eI=Z8A5 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> There are no specific tools I know of besides dd. Just remember to > change things like fstab and your ethernet configurations accordingly, > as the devices and MACs your using now may be different in a VM (the MAC > address will definitely be different for example). > > Sadly I haven''t got any specific docs I can point you at about building > a HVM domain from scratch. A quick search for p2v and xen on Google has > a few guides for converting a physical machine to a PV one, but not for > HVM. I''ve not attempted it myself either (I''ve been using HVM for > Windows machines mainly, and I''ve been doing the install from scratch as > I know how picky Windows can be about hardware), but I expect it''d be > pretty straight forward. When I do finally try it myself, I''ll > endeavour to document the experience if anything strange occurs. >Got it, thanks a lot to everybody for the excellent help. -- + Lorin + Nosce te ciment. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2007-Jul-26 17:29 UTC
Re: [Xen-users] xen 3.1 and 32bit guests in 64bit dom0
> PV is faster than HVM, but HVM allows unmodified guest OSs, so it''s not > a clear cut case for which is better.PV has good performance. Performance of 32-bit PV guests (on either a 32-bit or a 64-bit hypervisor) is probably higher than that of a 64-bit PV guest. I don''t know how well 64-bit PV guests compare to 64-bit HVM guests (which could potentially still have PV drivers installed) because implementing full PV on 64-bit was hard to do as efficiently as on 32-bit. It may be that HVM is more competitive for performance in the case of 64-bit guests.> PV has better performance, but if > you have to use a non-Xenified kernel, then I guess your hands are tied > (although apparently there is now some domU support in the standard > kernel according to kerneltrap.org).The 2.6.23 development tree (which has just passed -rc1) includes support for Xen. If you select a Xen capable host architecture (Pentium Pro and above) then there''ll be an option to support Xen under the paravirtualisation support section. The resulting kernel build will be capable of booting native or on Xen. However you''ll need to use the vmlinux / vmlinuz on Xen, whereas native booting will still need the bzImage. There''s work underway to allow Xen to boot bzImages directly, so you''ll only need to keep one image around. Cheers, Mark> As you''ve got hardware support, the only thing you need is to set the > config file and disk image up properly. HVM domains boot just like > regular systems (they have a BIOS as well), and so require a boot loader > in the disk image (I use an image for the entire disk, I don''t know if > you can split it up into different files for different partitions with > HVM), along with the kernel etc, and in the config file for the domain > you need to remove the initrd line, point the kernel line to the > hvmloader, change the builder to hvm and add the device modeller etc. > You can find an example in /etc/xen/xmexample.hvm in the standard Xen > install, or you could use RedHat''s virt-manager/virt-install to > configure and install the domain. > > Hope this helps, > > Martin > > Lorin wrote: > > On 7/26/07, Martin Goldstone <m.j.goldstone@isc.keele.ac.uk> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> 1st question: Is the domU kernel actually a Xen kernel? By the look of > >> that error, I''d guess that it isn''t, especially as normally Xen kernels > >> have -xen in them somewhere, and yours ends in -smp. You need to have a > >> Xen kernel to do PV, or you have to use HVM. > > > > It''s not a Xen kernel but a plain old stock kernel on which I''m > > supposed to run the VM (application requirements ). > > I have VT support in the cores so HVM should be enabled from what I''ve > > read so far . Does it require anything else ? > > > > Speaking of PV and HVM the latter is better because it makes use of > > hardware support right ? > > > >> 3rd question: If Danilo Godec''s suggestion about the NIC driver doesn''t > >> work, could you give us some more details about your networking setup > >> (ie NIC make/model, Bonding, VLANs etc)? > > > > Yeah, it was the bnx2 problem. > > > > Thanks a lot!-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > The 2.6.23 development tree (which has just passed -rc1) includes support for > Xen. If you select a Xen capable host architecture (Pentium Pro and above) > then there''ll be an option to support Xen under the paravirtualisation > support section. > > The resulting kernel build will be capable of booting native or on Xen. > However you''ll need to use the vmlinux / vmlinuz on Xen, whereas native > booting will still need the bzImage. There''s work underway to allow Xen to > boot bzImages directly, so you''ll only need to keep one image around. > > Cheers, > MarkCan we get more info about this? I assume this means that you can compile a stock linux kernel for use as a domU... how about a dom0? And since the kernel compile is separate from the current xen packaged compile which builds the hypervisor, I guess this will imply a fairly formal/strict API? or should I just go download it and try it out? I''ll try to find time for that. -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > The 2.6.23 development tree (which has just passed -rc1) includes support > > for Xen. If you select a Xen capable host architecture (Pentium Pro and > > above) then there''ll be an option to support Xen under the > > paravirtualisation support section. > > > > The resulting kernel build will be capable of booting native or on Xen. > > However you''ll need to use the vmlinux / vmlinuz on Xen, whereas native > > booting will still need the bzImage. There''s work underway to allow Xen > > to boot bzImages directly, so you''ll only need to keep one image around. > > > > Cheers, > > Mark > > Can we get more info about this? I assume this means that you can compile > a stock linux kernel for use as a domU...Yep. The code is different from that shipped in the sparse tree, and therefore not quite as widely used / tested, but it''s been through a fair amount of review now so hopefully it''ll work reasonably well. Suspend / resume, live migration and ballooning are not currently supported. Nor is the virtual framebuffer (and maybe some other stuff I forget).> how about a dom0?Nope. The Xen <-> dom0 interface isn''t in mainline yet. It''s not entirely clear whether it ever will be, or if it''ll be shipped as a patch against mainline. I think Jeremy is looking at something like this.> And since the > kernel compile is separate from the current xen packaged compile which > builds the hypervisor, I guess this will imply a fairly formal/strict API?The Xen <-> domU ABI has been pretty strict since the 3.0 release. Any 3.x-aware guest will run on an equally new, or newer hypervisor. You can''t in general guarantee that a newer kernel will run on an older hypervisor, unless it supports appropriate compatibility APIs. The default build for the XenLinux tree kernels (the kernel tree built by Xen, by default) also includes compatibility support so that they may run on older hypervisors as well as newer ones. The Xen <-> dom0 ABI has been fixed since uhhhh around 3.0.4 / 3.1, I can''t remember which. However, you may sacifice some functionality if you use an older kernel for dom0.> or should I just go download it and try it out? I''ll try to find time for > that.You can grab it from Linus'' git tree, or you can probably download a snapshot of that tree. Remember that you need to set your architecture to be PPro or newer, otherwise the Xen option won''t show up - that confused me for some time a couple of days ago ;-) For the moment, the XenLinux repository at XenSource contains a more full featured port of Linux to Xen than what is available in mainline. This is downloaded and built by default when you build Xen. I think you might now be able to get the Xen build system to grab mainline Linux and build it as a domU kernel automagically though... Eventually I expect that the main XenLinux repository will move to be closer to mainline Linux, as feature from the former are merged upstream, or refactored into patches against upstream. I hope this makes some sense! Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> >> Can we get more info about this? I assume this means that you can > >> compile a stock linux kernel for use as a domU... > > > > Yep. The code is different from that shipped in the sparse tree, and > > therefore not quite as widely used / tested, but it''s been through a fair > > amount of review now so hopefully it''ll work reasonably well. > > > > Suspend / resume, live migration and ballooning are not currently > > supported. Nor is the virtual framebuffer (and maybe some other stuff I > > forget). > > hmm, the migration capabilites are something that I like to have but > rarely use. Graphics, hvm, etc I can do without.I expect you know this, but just to clarify HVM is independent of the Linux domU kernel. If dom0 and Xen support it then it''ll work.> We''re "just" a linux > hosting service. Anyhow, the ability to have a CURRENT linux kernel with > up to date security patches, etc will be a plus. pity about migration > though :( I expect you folks will get to that in time :)Glad it''s a good step for you. The suspend / resume / migration needs cleaning up, plus I think it conflicts with other features (pre-emption?) at the moment.> > Eventually I expect that the main XenLinux repository will move to be > > closer to mainline Linux, as feature from the former are merged upstream, > > or refactored into patches against upstream. > > > > I hope this makes some sense! > > lots of sense and it''s a big step in a good direction.Hopefully it''ll minimise the diff between a fully featured Xenified kernel, and the mainline, even if there are still patches required for full functionality. In the long run this ought to make life easier for everyone concerned.> Thanks for the info! and thanks for your work on/with XEN!Enjoy. Would be nice to have some success reports (or bug reports if appropriate) once you''ve tried out the new kernels. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 26 Jul 2007, Mark Williamson wrote:>> or should I just go download it and try it out? I''ll try to find time for >> that. > > You can grab it from Linus'' git tree, or you can probably download a snapshot > of that tree. Remember that you need to set your architecture to be PPro or > newer, otherwise the Xen option won''t show up - that confused me for some > time a couple of days ago ;-)Finally got around to trying this... but it looks like the kernel config options for XEN (and PARAVIRT) only exist in the arch/i386 tree :( ... I''ve been trying to use x86_64 for the year or more, but it sure seems to be an uphill path :( So, I''ve found one small machine of mine that is an i386 build, but I can''t seem to get the new kernel packaged up correctly... or maybe this only works with newer hypervisors? None of the boxes I currently have access to are running anything more current than 3.0.4 ERROR: Kernel image does not have a a.out9 header. ERROR: Unrecognized image format ERROR: Error constructing guest OS and after monkeying around: ERROR: Not a Xen-ELF image: ''__xen_guest'' section not found. ERROR: Error constructing guest OS I poked around on the wiki and in google, but I can''t find anything about getting a stock linux kernel to run... It seems you want to copy the vmlinux file out of the top of the kernel source tree, strip it, and gzip it ... that APPEARS to get the right format of file that the xen tools will try to load... but at that point I''m hosed... with the xen_guest message. I''ll try upgrading to a more current version of xen, but did not like the 3.1.0 build procedures the last time I tried them ... -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > You can grab it from Linus'' git tree, or you can probably download a > > snapshot of that tree. Remember that you need to set your architecture > > to be PPro or newer, otherwise the Xen option won''t show up - that > > confused me for some time a couple of days ago ;-) > > Finally got around to trying this... but it looks like the kernel config > options for XEN (and PARAVIRT) only exist in the arch/i386 tree :( ... > I''ve been trying to use x86_64 for the year or more, but it sure seems to > be an uphill path :(Yep, the mainline support is x86_64 only for the moment (though it ought to run in 32-bit PAE compatibility mode on an x64 Xen host). The XenLinux in the XenSource repositority is currently a separate codebase from the mainline Linux Xen support (although code flows between the two) and it does have support for x86_64, which I assume you''ve tried?> So, I''ve found one small machine of mine that is an i386 build, but I > can''t seem to get the new kernel packaged up correctly... or maybe this > only works with newer hypervisors? None of the boxes I currently have > access to are running anything more current than 3.0.4 > > ERROR: Kernel image does not have a a.out9 header. > ERROR: Unrecognized image format > ERROR: Error constructing guest OS > > and after monkeying around: > > ERROR: Not a Xen-ELF image: ''__xen_guest'' section not found. > ERROR: Error constructing guest OS > > I poked around on the wiki and in google, but I can''t find > anything about getting a stock linux kernel to run... It seems > you want to copy the vmlinux file out of the top of the kernel > source tree, strip it, and gzip it ... that APPEARS to get the > right format of file that the xen tools will try to load... but > at that point I''m hosed... with the xen_guest message.Yeah. It''s not possible to boot bzImage kernels directly under Xen at all; that requires an update of the bzImage format, which has to be made without breaking buggy bootloaders - so that part of the effort is going slow. The vmlinux from the source tree should load on its own; stripping it and gzipping it to get a small vmlinuz helps keep the size down a lot though! What Xen were you running this on? I''ve had a mainline kernel boot successfully on the Xen 3.0.3 shipped with CentOS / RHEL 5. Are you sure that paravirt_ops support *and* the specific Xen support were both compiled into the kernel? Cheers, Mrak> I''ll try upgrading to a more current version of xen, but did not > like the 3.1.0 build procedures the last time I tried them ... > > > -Tom > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 19 Oct 2007, Mark Williamson wrote:> The XenLinux in the XenSource repositority is currently a separate codebase > from the mainline Linux Xen support (although code flows between the two) and > it does have support for x86_64, which I assume you''ve tried?no. I just ran into a situation where I needed a modern linux kernel so I could get a more current CIFS implimentation... moving the cifs directory between linux versions does not work :( This didn''t start as a XEN study, so I haven''t poked deeply at the XEN options... if I was that much of a keener I probably wouldn''t still be running close to a dozen 3.0.x xen hosts... :) :(>> I poked around on the wiki and in google, but I can''t find >> anything about getting a stock linux kernel to run... It seems >> you want to copy the vmlinux file out of the top of the kernel >> source tree, strip it, and gzip it ... that APPEARS to get the >> right format of file that the xen tools will try to load... but >> at that point I''m hosed... with the xen_guest message. > > Yeah. It''s not possible to boot bzImage kernels directly under Xen at all; > that requires an update of the bzImage format, which has to be made without > breaking buggy bootloaders - so that part of the effort is going slow. > > The vmlinux from the source tree should load on its own; stripping it and > gzipping it to get a small vmlinuz helps keep the size down a lot though!At this point I don''t care much, if vmlinux is good enough, that should be fine. I couldn''t find _any_ docs on this process ... I was just trying to match what the domU and dom0 kernels looked like.> What Xen were you running this on? I''ve had a mainline kernel boot > successfully on the Xen 3.0.3 shipped with CentOS / RHEL 5. Are you sure > that paravirt_ops support *and* the specific Xen support were both compiled > into the kernel?AFAIK, You can''t get xen support without the paravirt options... and I did look at the system-map for my kernel, and it was full of xen symbols, it just didn''t have __xen_guest in it ... Hhmm, a quick grep of the the linux.2.6.23.1 tree only shows xen_guest in include/xen/interface/elfnote.h ... and event that is only in the comments... from xm info... xen_major : 3 xen_minor : 0 xen_extra : .2-2 xen_caps : xen-3.0-x86_32 That''s just what''s on the i386 box... From where I sit, it looks like my issues are a consequence of not keeping up to date. can you tell me more about "32-bit PAE compatibility mode on an x64 Xen host"? I''d never heard of that. I''ve also trying to get hvm working on one of the x86_64 machines ... I had a corrupted rpm database that slowed things down a bit, and since my overall goal is win2003 <-> Linux file access I''ve spent a fair bit of the day on other topics. The 3.0.2 i386 box is at a state where I have both remote power and remote serial console control... (just tested)... it''s a drbd secondary so I don''t really want to trash it, but rebooting it isn''t a big deal as long as I''m darn sure it''s going to come back. THANKS for the info, you''ve given me more than a few things to look into. -Tom> > Cheers, > MrakGotta like it when people typo their own names :) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users