Hi, I installed Xen-3.2 last night and setup the grub.conf and kernel as usual. However, when I rebooted I did not get an console input when booting the dom0. I tried adding the console=vga to my grub.conf as shown below: title xen-3.2 root (hd0,0) kernel /boot/xen-3.2.gz console=vga module /boot/vmlinuz-2.6.18.8 root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 module /boot/xen-2.6.18 quiet I am not sure where to go from here. Thanks chuck _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Do you mean you cannot type input at the vga console, or do you mean there is no output at all? Does output from Xen appear, but not from dom0? -- Keir On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote:> Hi, > > I installed Xen-3.2 last night and setup the grub.conf and kernel as > usual. However, when I rebooted I did not get an console input when > booting the dom0. I tried adding the console=vga to my grub.conf as > shown below: > > title xen-3.2 > root (hd0,0) > kernel /boot/xen-3.2.gz console=vga > module /boot/vmlinuz-2.6.18.8 > root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 > module /boot/xen-2.6.18 > quiet > > I am not sure where to go from here. > > Thanks > chuck > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
No output at all. On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:> Do you mean you cannot type input at the vga console, or do you mean there > is no output at all? Does output from Xen appear, but not from dom0? > > -- Keir > > > On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: > > > Hi, > > > > I installed Xen-3.2 last night and setup the grub.conf and kernel as > > usual. However, when I rebooted I did not get an console input when > > booting the dom0. I tried adding the console=vga to my grub.conf as > > shown below: > > > > title xen-3.2 > > root (hd0,0) > > kernel /boot/xen-3.2.gz console=vga > > module /boot/vmlinuz-2.6.18.8 > > root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 > > module /boot/xen-2.6.18 > > quiet > > > > I am not sure where to go from here. > > > > Thanks > > chuck > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Did the system actually boot, just with no console output, or might the system simply have been toast? Also, from where did you get Xen 3.2? Since it doesn''t exist yet, did you pull and build the xen-unstable repo? -- Keir On 13/11/07 15:18, "Chuck Short" <zulcss@gmail.com> wrote:> No output at all. > > On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: >> Do you mean you cannot type input at the vga console, or do you mean there >> is no output at all? Does output from Xen appear, but not from dom0? >> >> -- Keir >> >> >> On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: >> >>> Hi, >>> >>> I installed Xen-3.2 last night and setup the grub.conf and kernel as >>> usual. However, when I rebooted I did not get an console input when >>> booting the dom0. I tried adding the console=vga to my grub.conf as >>> shown below: >>> >>> title xen-3.2 >>> root (hd0,0) >>> kernel /boot/xen-3.2.gz console=vga >>> module /boot/vmlinuz-2.6.18.8 >>> root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 >>> module /boot/xen-2.6.18 >>> quiet >>> >>> I am not sure where to go from here. >>> >>> Thanks >>> chuck >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yes it did acutally boot but there was no console output. I meant to say from the xen-unstable repo. On Nov 13, 2007 10:35 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:> Did the system actually boot, just with no console output, or might the > system simply have been toast? > > Also, from where did you get Xen 3.2? Since it doesn''t exist yet, did you > pull and build the xen-unstable repo? > > -- Keir > > > On 13/11/07 15:18, "Chuck Short" <zulcss@gmail.com> wrote: > > > No output at all. > > > > On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: > >> Do you mean you cannot type input at the vga console, or do you mean there > >> is no output at all? Does output from Xen appear, but not from dom0? > >> > >> -- Keir > >> > >> > >> On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: > >> > >>> Hi, > >>> > >>> I installed Xen-3.2 last night and setup the grub.conf and kernel as > >>> usual. However, when I rebooted I did not get an console input when > >>> booting the dom0. I tried adding the console=vga to my grub.conf as > >>> shown below: > >>> > >>> title xen-3.2 > >>> root (hd0,0) > >>> kernel /boot/xen-3.2.gz console=vga > >>> module /boot/vmlinuz-2.6.18.8 > >>> root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 > >>> module /boot/xen-2.6.18 > >>> quiet > >>> > >>> I am not sure where to go from here. > >>> > >>> Thanks > >>> chuck > >>> > >>> _______________________________________________ > >>> Xen-devel mailing list > >>> Xen-devel@lists.xensource.com > >>> http://lists.xensource.com/xen-devel > >> > >> > >> > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Are you using the tip of the tree? Could it be a crash? I see it crashing (tip) and only the cursor blinking in the upper left corner. Stefan xen-devel-bounces@lists.xensource.com wrote on 11/13/2007 10:18:53 AM:> No output at all. > > On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: > > Do you mean you cannot type input at the vga console, or do you meanthere> > is no output at all? Does output from Xen appear, but not from dom0? > > > > -- Keir > > > > > > On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: > > > > > Hi, > > > > > > I installed Xen-3.2 last night and setup the grub.conf and kernel as > > > usual. However, when I rebooted I did not get an console input when > > > booting the dom0. I tried adding the console=vga to my grub.conf as > > > shown below: > > > > > > title xen-3.2 > > > root (hd0,0) > > > kernel /boot/xen-3.2.gz console=vga > > > module /boot/vmlinuz-2.6.18.8 > > > root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 > > > module /boot/xen-2.6.18 > > > quiet > > > > > > I am not sure where to go from here. > > > > > > Thanks > > > chuck > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
correct On Nov 13, 2007 10:54 AM, Stefan Berger <stefanb@us.ibm.com> wrote:> > Are you using the tip of the tree? Could it be a crash? I see it crashing > (tip) and only the cursor blinking in the upper left corner. > > Stefan > > xen-devel-bounces@lists.xensource.com wrote on 11/13/2007 10:18:53 AM: > > > > > No output at all. > > > > On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: > > > Do you mean you cannot type input at the vga console, or do you mean > there > > > is no output at all? Does output from Xen appear, but not from dom0? > > > > > > -- Keir > > > > > > > > > On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: > > > > > > > Hi, > > > > > > > > I installed Xen-3.2 last night and setup the grub.conf and kernel as > > > > usual. However, when I rebooted I did not get an console input when > > > > booting the dom0. I tried adding the console=vga to my grub.conf as > > > > shown below: > > > > > > > > title xen-3.2 > > > > root (hd0,0) > > > > kernel /boot/xen-3.2.gz console=vga > > > > module /boot/vmlinuz-2.6.18.8 > > > > root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 > > > > module /boot/xen-2.6.18 > > > > quiet > > > > > > > > I am not sure where to go from here. > > > > > > > > Thanks > > > > chuck > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xensource.com > > > > http://lists.xensource.com/xen-devel > > > > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> Stefan Berger <stefanb@us.ibm.com> 13.11.07 16:54 >>> >Are you using the tip of the tree? Could it be a crash? I see it crashing >(tip) and only the cursor blinking in the upper left corner.Same to me on one 32-bit system. Two other 32-bit systems and all my 64-bit ones work fine. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Perhaps try no-real-mode on Xen''s command line? I would definitely expect you should get output on the vga display with your current setup. -- Keir On 13/11/07 15:40, "Chuck Short" <zulcss@gmail.com> wrote:> Yes it did acutally boot but there was no console output. I meant to > say from the xen-unstable repo. > > On Nov 13, 2007 10:35 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: >> Did the system actually boot, just with no console output, or might the >> system simply have been toast? >> >> Also, from where did you get Xen 3.2? Since it doesn''t exist yet, did you >> pull and build the xen-unstable repo? >> >> -- Keir >> >> >> On 13/11/07 15:18, "Chuck Short" <zulcss@gmail.com> wrote: >> >>> No output at all. >>> >>> On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: >>>> Do you mean you cannot type input at the vga console, or do you mean there >>>> is no output at all? Does output from Xen appear, but not from dom0? >>>> >>>> -- Keir >>>> >>>> >>>> On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I installed Xen-3.2 last night and setup the grub.conf and kernel as >>>>> usual. However, when I rebooted I did not get an console input when >>>>> booting the dom0. I tried adding the console=vga to my grub.conf as >>>>> shown below: >>>>> >>>>> title xen-3.2 >>>>> root (hd0,0) >>>>> kernel /boot/xen-3.2.gz console=vga >>>>> module /boot/vmlinuz-2.6.18.8 >>>>> root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 >>>>> module /boot/xen-2.6.18 >>>>> quiet >>>>> >>>>> I am not sure where to go from here. >>>>> >>>>> Thanks >>>>> chuck >>>>> >>>>> _______________________________________________ >>>>> Xen-devel mailing list >>>>> Xen-devel@lists.xensource.com >>>>> http://lists.xensource.com/xen-devel >>>> >>>> >>>> >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Changesets 16215, 16156, 16147 have to be suspected. Could one of you try backing those out one by one (cumulatively, not individually) and see if Xen springs back to life? My fear is that shifting the location of the boot trampoline has screwed us on some boxes. But then again I have no reason to think that 0x8c000 isn''t a safe place to stick the trampoline... Thanks, Keir On 13/11/07 16:15, "Jan Beulich" <jbeulich@novell.com> wrote:>>>> Stefan Berger <stefanb@us.ibm.com> 13.11.07 16:54 >>> >> Are you using the tip of the tree? Could it be a crash? I see it crashing >> (tip) and only the cursor blinking in the upper left corner. > > Same to me on one 32-bit system. Two other 32-bit systems and all my > 64-bit ones work fine. > > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
No effect. On Nov 13, 2007 11:15 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:> Perhaps try no-real-mode on Xen''s command line? I would definitely expect > you should get output on the vga display with your current setup. > > -- Keir > > > > On 13/11/07 15:40, "Chuck Short" <zulcss@gmail.com> wrote: > > > Yes it did acutally boot but there was no console output. I meant to > > say from the xen-unstable repo. > > > > On Nov 13, 2007 10:35 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: > >> Did the system actually boot, just with no console output, or might the > >> system simply have been toast? > >> > >> Also, from where did you get Xen 3.2? Since it doesn''t exist yet, did you > >> pull and build the xen-unstable repo? > >> > >> -- Keir > >> > >> > >> On 13/11/07 15:18, "Chuck Short" <zulcss@gmail.com> wrote: > >> > >>> No output at all. > >>> > >>> On Nov 13, 2007 10:10 AM, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: > >>>> Do you mean you cannot type input at the vga console, or do you mean there > >>>> is no output at all? Does output from Xen appear, but not from dom0? > >>>> > >>>> -- Keir > >>>> > >>>> > >>>> On 13/11/07 13:40, "Chuck Short" <zulcss@gmail.com> wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I installed Xen-3.2 last night and setup the grub.conf and kernel as > >>>>> usual. However, when I rebooted I did not get an console input when > >>>>> booting the dom0. I tried adding the console=vga to my grub.conf as > >>>>> shown below: > >>>>> > >>>>> title xen-3.2 > >>>>> root (hd0,0) > >>>>> kernel /boot/xen-3.2.gz console=vga > >>>>> module /boot/vmlinuz-2.6.18.8 > >>>>> root=UUID=7373696f-c367-4a6a-b198-17e593508cc8 ro console=tty0 > >>>>> module /boot/xen-2.6.18 > >>>>> quiet > >>>>> > >>>>> I am not sure where to go from here. > >>>>> > >>>>> Thanks > >>>>> chuck > >>>>> > >>>>> _______________________________________________ > >>>>> Xen-devel mailing list > >>>>> Xen-devel@lists.xensource.com > >>>>> http://lists.xensource.com/xen-devel > >>>> > >>>> > >>>> > >>> > >>> _______________________________________________ > >>> Xen-devel mailing list > >>> Xen-devel@lists.xensource.com > >>> http://lists.xensource.com/xen-devel > >> > >> > >> > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 13.11.07 17:32 >>> >Changesets 16215, 16156, 16147 have to be suspected. Could one of you try >backing those out one by one (cumulatively, not individually) and see if Xen >springs back to life? My fear is that shifting the location of the boot >trampoline has screwed us on some boxes. But then again I have no reason to >think that 0x8c000 isn''t a safe place to stick the trampoline...16215 appears to be innocent - it''s sufficiently isolated for reverting alone. The others I''ll try tomorrow, unless Stefan beats me. In any case - setting a video mode works, so the problem is likely on the return path from real mode. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
xen-devel-bounces@lists.xensource.com wrote on 11/13/2007 12:17:53 PM:> >>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 13.11.07 17:32 >>> > >Changesets 16215, 16156, 16147 have to be suspected. Could one of youtry> >backing those out one by one (cumulatively, not individually) and seeif Xen> >springs back to life? My fear is that shifting the location of the boot > >trampoline has screwed us on some boxes. But then again I have noreason to> >think that 0x8c000 isn''t a safe place to stick the trampoline... > > 16215 appears to be innocent - it''s sufficiently isolated for revertingalone.> The others I''ll try tomorrow, unless Stefan beats me.So I have tried the following versions and hope I did not do anything wrong on the way: 16146 works 16147 works 16156 works 16215 works 16300 does not work So, it would take me ld(85) more tries to hopefully find the CS that caused it. Any hints, though? Stefan> > In any case - setting a video mode works, so the problem is likely onthe> return path from real mode. > > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Oh, you¹re just doing hg update <changeset>¹? You could use binary chop in the range 16215-16300. :-) I¹ll have a quick look and see if any changesets are very suspect in that range.... 16287,16266,16259,16249. I think you¹re best off doing a binary chop. It should only take you half a dozen tries. -- Keir On 13/11/07 18:14, "Stefan Berger" <stefanb@us.ibm.com> wrote:> So I have tried the following versions and hope I did not do anything wrong on > the way: > > 16146 works > 16147 works > 16156 works > 16215 works > 16300 does not work > > So, it would take me ld(85) more tries to hopefully find the CS that caused > it. Any hints, though?_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
xen-devel-bounces@lists.xensource.com wrote on 11/13/2007 01:21:12 PM:> Oh, you?re just doing ?hg update <changeset>?? You could use binary > chop in the range 16215-16300. :-) I?ll have a quick look and see if > any changesets are very suspect in that range.... 16287,16266,16259, > 16249. I think you?re best off doing a binary chop. It should only > take you half a dozen tries.On my machine 16259 causes the crash, 16258 still works. Stefan> > -- Keir > > On 13/11/07 18:14, "Stefan Berger" <stefanb@us.ibm.com> wrote:> So I have tried the following versions and hope I did not do > anything wrong on the way: > > 16146 works > 16147 works > 16156 works > 16215 works > 16300 does not work > > So, it would take me ld(85) more tries to hopefully find the CS that > caused it. Any hints, though? > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Okay, thanks. To be clear, it crashes for you with no console output at all? Is that over serial line, or on vga? If on vga, is it text mode or vesa lfb (the latter is initialised relatively late in boot)? -- Keir On 13/11/07 19:01, "Stefan Berger" <stefanb@us.ibm.com> wrote:> > xen-devel-bounces@lists.xensource.com wrote on 11/13/2007 01:21:12 PM: > >> > Oh, you¹re just doing hg update <changeset>¹? You could use binary >> > chop in the range 16215-16300. :-) I¹ll have a quick look and see if >> > any changesets are very suspect in that range.... 16287,16266,16259, >> > 16249. I think you¹re best off doing a binary chop. It should only >> > take you half a dozen tries. > > On my machine 16259 causes the crash, 16258 still works. > > Stefan > >> > >> > -- Keir >> > >> > On 13/11/07 18:14, "Stefan Berger" <stefanb@us.ibm.com> wrote: > >> > So I have tried the following versions and hope I did not do >> > anything wrong on the way: >> > >> > 16146 works >> > 16147 works >> > 16156 works >> > 16215 works >> > 16300 does not work >> > >> > So, it would take me ld(85) more tries to hopefully find the CS that >> > caused it. Any hints, though? >> > _______________________________________________ >> > Xen-devel mailing list >> > Xen-devel@lists.xensource.com >> > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote on 11/13/2007 02:14:01 PM:> Okay, thanks. To be clear, it crashes for you with no console output > at all? Is that over serial line, or on vga? If on vga, is it text > mode or vesa lfb (the latter is initialised relatively late in boot)?This is on VGA output. I haven''t checked serial line. The boot entry in grub.conf has only one parameter for xen and that''s dom0_mem=2G -- must be VGA then? Stefan> > -- Keir > > On 13/11/07 19:01, "Stefan Berger" <stefanb@us.ibm.com> wrote:> > xen-devel-bounces@lists.xensource.com wrote on 11/13/2007 01:21:12 PM: > > > Oh, you?re just doing ?hg update <changeset>?? You could use binary > > chop in the range 16215-16300. :-) I?ll have a quick look and see if > > any changesets are very suspect in that range.... 16287,16266,16259, > > 16249. I think you?re best off doing a binary chop. It should only > > take you half a dozen tries. > > On my machine 16259 causes the crash, 16258 still works. > > Stefan > > > > > -- Keir > > > > On 13/11/07 18:14, "Stefan Berger" <stefanb@us.ibm.com> wrote: > > > So I have tried the following versions and hope I did not do > > anything wrong on the way: > > > > 16146 works > > 16147 works > > 16156 works > > 16215 works > > 16300 does not work > > > > So, it would take me ld(85) more tries to hopefully find the CS that > > caused it. Any hints, though? > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 13/11/07 19:26, "Stefan Berger" <stefanb@us.ibm.com> wrote:> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote on 11/13/2007 02:14:01 PM: > >> > Okay, thanks. To be clear, it crashes for you with no console output >> > at all? Is that over serial line, or on vga? If on vga, is it text >> > mode or vesa lfb (the latter is initialised relatively late in boot)? > > This is on VGA output. I haven''t checked serial line. > The boot entry in grub.conf has only one parameter for xen and that''s > dom0_mem=2G -- must be VGA then?Yes. It should be the traditional¹ crappy lo-res text mode. That gets initialised early. Oh, I see I put in an unconditional MSR_EFER access early on. Not all systems will have that.... Ooops, will fix. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Xen-unstable staging c/s 16378. -- Keir On 13/11/07 19:33, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:> Oh, I see I put in an unconditional MSR_EFER access early on. Not all systems > will have that.... Ooops, will fix. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Xen-unstable staging c/s 16378.Thanks. Works for me now. Stefan> > -- Keir > > On 13/11/07 19:33, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:> Oh, I see I put in an unconditional MSR_EFER access early on. Not > all systems will have that.... Ooops, will fix.> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Works for me now as well. Thanks On Nov 13, 2007 3:30 PM, Stefan Berger <stefanb@us.ibm.com> wrote:> > > Xen-unstable staging c/s 16378. > > Thanks. Works for me now. > > Stefan > > > > > -- Keir > > > > On 13/11/07 19:33, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote: > > > > Oh, I see I put in an unconditional MSR_EFER access early on. Not > > all systems will have that.... Ooops, will fix. > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks, this fixes it for me, too. Jan>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 13.11.07 21:12 >>>Xen-unstable staging c/s 16378. -- Keir On 13/11/07 19:33, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:> Oh, I see I put in an unconditional MSR_EFER access early on. Not all systems > will have that.... Ooops, will fix. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel