Hi, I''m stuck in my attempts to get xen up and running. I selected Debian Lenny as base as I''m a bit more familiar with Debian/Ubuntu than with the other Linux distros. Uname -r 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows Server 2008 R2. My first problem is that /proc/cpuinfo does not show the vmx flag, although I know that the processor (Intel E5504) has VT-X support (and virtualization is enabled in BIOS). Anyway, I tried to set up a guest anyway. Running the command "xm create" seems to return successfully, but I can''t connect to the guest via VNC. No VNC-like port is opened (given "netstat -a"). No warnings (only debug/info) in xend.log while starting the guest domain, although while starting domain 0 the following warnings occur: [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VBD.set_device not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VBD.set_type not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: session.get_all_records not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: event.get_record not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: event.get_all not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VM.get_auto_power_on not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VM.set_auto_power_on not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.get_network not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_device not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_MAC not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_MTU not found [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: debug.get_all not found This one is also interesting: [2009-12-03 09:37:54 2944] INFO (XendNetwork:114) Not recreating missing unmanaged network xenbr0 ...I thought xenbr0 was no more with xen 3.2, so the question is what the cause of this message is. Thankful for help! // David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote:> Hi, > > I''m stuck in my attempts to get xen up and running. > > I selected Debian Lenny as base as I''m a bit more familiar with > Debian/Ubuntu than with the other Linux distros. Uname -r > 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows Server > 2008 R2. >First of all you might have hard time getting 2008R2 working on Xen 3.2. 2008R2 didn''t exist when 3.2 was released. Xen has has a lot of fixes and improvements after version 3.2.> My first problem is that /proc/cpuinfo does not show the vmx flag, > although I know that the processor (Intel E5504) has VT-X support (and > virtualization is enabled in BIOS). > > Anyway, I tried to set up a guest anyway. Running the command "xm create" > seems to return successfully, but I can''t connect to the guest via VNC. No > VNC-like port is opened (given "netstat -a"). No warnings (only > debug/info) in xend.log while starting the guest domain, although while > starting domain 0 the following warnings occur: > > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VBD.set_device > not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VBD.set_type > not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: > session.get_all_records not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: > event.get_record not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: event.get_all > not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: > VM.get_auto_power_on not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: > VM.set_auto_power_on not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.get_network > not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_device > not found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_MAC not > found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_MTU not > found > [2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: debug.get_all > not found > > This one is also interesting: > > [2009-12-03 09:37:54 2944] INFO (XendNetwork:114) Not recreating missing > unmanaged network xenbr0 > > ...I thought xenbr0 was no more with xen 3.2, so the question is what the > cause of this message is. > > Thankful for help! >Did qemu-dm start at all? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote: >> Hi, >> >> I''m stuck in my attempts to get xen up and running. >> >> I selected Debian Lenny as base as I''m a bit more familiar with >> Debian/Ubuntu than with the other Linux distros. Uname -r >> 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows Server >> 2008 R2. > > First of all you might have hard time getting 2008R2 working on Xen 3.2. > 2008R2 didn''t exist when 3.2 was released. > > Xen has has a lot of fixes and improvements after version 3.2.Thanks for your answer, Pasi. Meanwhile we have also discovered that if we try Ubuntu 9.10 (with kernel 2.6.31) the vmx flag is indeed present. However, Ubuntu has no xen kernel. :-( I could try to build it myself, but it seems a bit hairy according to http://old.nabble.com/2.6.30-dom0-Xen-patches-td24293721i20.html I have read http://wiki.xensource.com/xenwiki/XenDom0Kernels/ which is a good source of information but I have a hard time picking distro. To start with, what minimum versions (of Xen hypervisor, and Linux kernel) would you recommend if you want to run 2008R2? // David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 04, 2009 at 11:18:36AM +0100, David Henningsson wrote:> > On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote: > >> Hi, > >> > >> I''m stuck in my attempts to get xen up and running. > >> > >> I selected Debian Lenny as base as I''m a bit more familiar with > >> Debian/Ubuntu than with the other Linux distros. Uname -r > >> 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows Server > >> 2008 R2. > > > > First of all you might have hard time getting 2008R2 working on Xen 3.2. > > 2008R2 didn''t exist when 3.2 was released. > > > > Xen has has a lot of fixes and improvements after version 3.2. > > Thanks for your answer, Pasi. Meanwhile we have also discovered that if we > try Ubuntu 9.10 (with kernel 2.6.31) the vmx flag is indeed present. > However, Ubuntu has no xen kernel. :-( I could try to build it myself, but > it seems a bit hairy according to > http://old.nabble.com/2.6.30-dom0-Xen-patches-td24293721i20.html > > I have read http://wiki.xensource.com/xenwiki/XenDom0Kernels/ which is a > good source of information but I have a hard time picking distro. To start > with, what minimum versions (of Xen hypervisor, and Linux kernel) would > you recommend if you want to run 2008R2? >I''d recommend going with Xen 3.4.2, since that''s the latest stable release. The official dom0 kernel for Xen 3.4.2 is linux-2.6.18-xen, so that''s the safe choise aswell, assuming it has all the drivers for your hardware. http://xenbits.xen.org/linux-2.6.18-xen.hg seems to have some additional driver backports committed after 3.4.2 snapshot, so you might want to fetch the dom0 kernel directly from hg. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 04, 2009 at 11:18:36AM +0100, David Henningsson wrote:> > On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote: > >> Hi, > >> > >> I''m stuck in my attempts to get xen up and running. > >> > >> I selected Debian Lenny as base as I''m a bit more familiar with > >> Debian/Ubuntu than with the other Linux distros. Uname -r > >> 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows Server > >> 2008 R2. > > > > First of all you might have hard time getting 2008R2 working on Xen 3.2. > > 2008R2 didn''t exist when 3.2 was released. > > > > Xen has has a lot of fixes and improvements after version 3.2. > > Thanks for your answer, Pasi. Meanwhile we have also discovered that if we > try Ubuntu 9.10 (with kernel 2.6.31) the vmx flag is indeed present. > However, Ubuntu has no xen kernel. :-( I could try to build it myself, but > it seems a bit hairy according to > http://old.nabble.com/2.6.30-dom0-Xen-patches-td24293721i20.html >Also what does "xm info" say about the capabilities/caps? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 4, 2009 at 5:18 PM, David Henningsson <launchpad.web@epost.diwic.se> wrote:> To start > with, what minimum versions (of Xen hypervisor, and Linux kernel) would > you recommend if you want to run 2008R2?If you don''t want to compile from source, I highly suggest you use RHEL/Centos 5 x86_64 and use Xen 3.4.2 from Gitco. That''s what I use on my setup. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On Fri, Dec 04, 2009 at 11:18:36AM +0100, David Henningsson wrote: >> > On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote: >> >> Hi, >> >> >> >> I''m stuck in my attempts to get xen up and running. >> >> >> >> I selected Debian Lenny as base as I''m a bit more familiar with >> >> Debian/Ubuntu than with the other Linux distros. Uname -r >> >> 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows >> Server >> >> 2008 R2. >> > >> > First of all you might have hard time getting 2008R2 working on Xen >> 3.2. >> > 2008R2 didn''t exist when 3.2 was released. >> > >> > Xen has has a lot of fixes and improvements after version 3.2. > > Also what does "xm info" say about the capabilities/caps?Hi Pasi and Fajar, and thanks for trying to help out :-) Here is the requested information: # xm info | grep caps hw_caps : bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 There is no qemu-dm process after having run "xm create" (which completes successfully): # ps -ef | grep qemu root 3447 2804 0 14:52 pts/0 00:00:00 grep qemu The last thing in "xend.log" is my domU being "unpaused". And xm list shows it: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1851 4 r----- 116.6 win2008 2 4096 1 ------ 0.0 Also, I doubt 2.6.18 is an option for this hardware. // David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 04, 2009 at 03:01:49PM +0100, David Henningsson wrote:> > On Fri, Dec 04, 2009 at 11:18:36AM +0100, David Henningsson wrote: > >> > On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote: > >> >> Hi, > >> >> > >> >> I''m stuck in my attempts to get xen up and running. > >> >> > >> >> I selected Debian Lenny as base as I''m a bit more familiar with > >> >> Debian/Ubuntu than with the other Linux distros. Uname -r > >> >> 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows > >> Server > >> >> 2008 R2. > >> > > >> > First of all you might have hard time getting 2008R2 working on Xen > >> 3.2. > >> > 2008R2 didn''t exist when 3.2 was released. > >> > > >> > Xen has has a lot of fixes and improvements after version 3.2. > > > > Also what does "xm info" say about the capabilities/caps? > > Hi Pasi and Fajar, and thanks for trying to help out :-) > > Here is the requested information: > > # xm info | grep caps > hw_caps : > bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 >so the caps says you _do_ have hvm (vmx) support.> There is no qemu-dm process after having run "xm create" (which completes > successfully): >Do you even have qemu-dm binary?> # ps -ef | grep qemu > root 3447 2804 0 14:52 pts/0 00:00:00 grep qemu > > The last thing in "xend.log" is my domU being "unpaused". And xm list > shows it: >So no errors in the log? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 4, 2009 at 9:01 PM, David Henningsson <launchpad.web@epost.diwic.se> wrote:> Also, I doubt 2.6.18 is an option for this hardware.The original 2.6.18, perhaps. But Redhat and xen.org both have backported lost of drivers. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On Fri, Dec 04, 2009 at 03:01:49PM +0100, David Henningsson wrote: >> > On Fri, Dec 04, 2009 at 11:18:36AM +0100, David Henningsson wrote: >> >> > On Thu, Dec 03, 2009 at 10:25:38AM +0100, David Henningsson wrote: >> >> >> Hi, >> >> >> >> >> >> I''m stuck in my attempts to get xen up and running. >> >> >> >> >> >> I selected Debian Lenny as base as I''m a bit more familiar with >> >> >> Debian/Ubuntu than with the other Linux distros. Uname -r >> >> >> 2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows >> >> Server >> >> >> 2008 R2. >> >> > >> >> > First of all you might have hard time getting 2008R2 working on Xen >> >> 3.2. >> >> > 2008R2 didn''t exist when 3.2 was released. >> >> > >> >> > Xen has has a lot of fixes and improvements after version 3.2. >> > >> > Also what does "xm info" say about the capabilities/caps? >> >> Hi Pasi and Fajar, and thanks for trying to help out :-) >> >> Here is the requested information: >> >> # xm info | grep caps >> hw_caps : >> bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001 >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> > so the caps says you _do_ have hvm (vmx) support.I assume that''s a good thing :-)>> There is no qemu-dm process after having run "xm create" (which >> completes >> successfully): >> > > Do you even have qemu-dm binary?# find . -iname "qemu-dm" ./usr/lib/xen-3.2-1/bin/qemu-dm>> # ps -ef | grep qemu >> root 3447 2804 0 14:52 pts/0 00:00:00 grep qemu >> >> The last thing in "xend.log" is my domU being "unpaused". And xm list >> shows it: > > So no errors in the log?Not except the Xendapi warnings I get when restarting xend (see earlier posted message). // David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>> On Fri, Dec 04, 2009 at 03:01:49PM +0100, David Henningsson wrote: >>> There is no qemu-dm process after having run "xm create" (which >>> completes >>> successfully): >> >> Do you even have qemu-dm binary? > > # find . -iname "qemu-dm" > ./usr/lib/xen-3.2-1/bin/qemu-dmActually, this was most helpful. I managed to come a little bit further by cd /usr/lib64 ln -s xen-3.2-1 xen ...and now the machine starts! If I attach to it with VNC, I see a screen saying "Starting Windows (C) Microsoft Corporation" (forever), and the following is the last things seen in qemu-dm-4.log: Register xen platform. Done register platform. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Do you think this is solvable, or should I try another distro with a later xen version? // David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users