Hi all, Ive been successful in getting the 3.4.0 bits installed on my OpenSolaris 2009.06 box. I''ve also managed to bfu a newly created BE to the corresponding snv115. Ive verified this setup works with a Windows 2003 hvm-based domu, but I am unable to install Windows 2008. The domu boots up from cd, but I get a bluescreen soon after with a 7E stop code. Has anyone been successful in installing Windows 2008? I will be able to provide the log files only later on in the day once I get back home. Thanks. -Siddharth
Siddharth Karnik wrote:> Hi all, > > Ive been successful in getting the 3.4.0 bits installed on my > OpenSolaris 2009.06 box. I''ve also managed to bfu a newly created BE > to the corresponding snv115. > > Ive verified this setup works with a Windows 2003 hvm-based domu, but > I am unable to install Windows 2008. > > The domu boots up from cd, but I get a bluescreen soon after with a 7E > stop code. > > Has anyone been successful in installing Windows 2008? > > I will be able to provide the log files only later on in the day once > I get back home.you need to enable viridian in the guest config.. e.g. viridian=1 MRJ
On Thu, Jun 25, 2009 at 7:26 PM, Mark Johnson<Mark.Johnson@sun.com> wrote:> > > Siddharth Karnik wrote: >> >> Hi all, >> >> Ive been successful in getting the 3.4.0 bits installed on my >> OpenSolaris 2009.06 box. I''ve also managed to bfu a newly created BE >> to the corresponding snv115. >> >> Ive verified this setup works with a Windows 2003 hvm-based domu, but >> I am unable to install Windows 2008. >> >> The domu boots up from cd, but I get a bluescreen soon after with a 7E >> stop code. >> >> Has anyone been successful in installing Windows 2008? >> >> I will be able to provide the log files only later on in the day once >> I get back home. > > > you need to enable viridian in the guest config.. e.g. > viridian=1 >Nope. This still doesn''t work for me. Here is my config file for the Win2k8 domain. Maybe there''s something else in here that I need to do.... Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get the same result for 32-bit as well. x-x-x-x-x-x-x- disk = [ ''file:/export/home/sid/Xen-configs/Windows2008/win2k8-disk.raw,hda,w'', ''file:/Seagate/Downloads/ISOs/windows.iso,hdc:cdrom,r'' ] memory = 1024 name = "Windows2008" kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' vif = [ ''type=ioemu'' ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''preserve'' boot = ''d'' acpi=1 apic=1 vnc=1 vnclisten = "0.0.0.0" vncpasswd='''' viridian=1 usb=1 usbdevice="tablet" device_model = ''/usr/lib/xen/bin/qemu-dm'' -x-x-x-x-x- Thanks. -Siddharth> > MRJ > >
Hi Siddharth,> > Nope. This still doesn''t work for me. > > Here is my config file for the Win2k8 domain. Maybe there''s something > else in here that I need to do.... > > Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get > the same result for 32-bit as well. > > x-x-x-x-x-x-x-I''ve lost track of this thread.. Did you get win2k8 to work for you? MRJ> disk = [ ''file:/export/home/sid/Xen-configs/Windows2008/win2k8-disk.raw,hda,w'', > ''file:/Seagate/Downloads/ISOs/windows.iso,hdc:cdrom,r'' > ] > > memory = 1024 > name = "Windows2008" > kernel = "/usr/lib/xen/boot/hvmloader" > builder = ''hvm'' > vif = [ ''type=ioemu'' ] > > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''preserve'' > > boot = ''d'' > acpi=1 > apic=1 > vnc=1 > vnclisten = "0.0.0.0" > vncpasswd='''' > viridian=1 > usb=1 > usbdevice="tablet" > > device_model = ''/usr/lib/xen/bin/qemu-dm'' > > -x-x-x-x-x- > > Thanks. > > -Siddharth >> MRJ >> >> > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> wrote:> > Hi Siddharth, > >> >> Nope. This still doesn''t work for me. >> >> Here is my config file for the Win2k8 domain. Maybe there''s something >> else in here that I need to do.... >> >> Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get >> the same result for 32-bit as well. >> >> x-x-x-x-x-x-x- > > I''ve lost track of this thread.. Did you get win2k8 to work for > you?I actually got this working on another machine. This is an updated 2009.06 laptop - using xen 3.1.4 I''m trying to redo the setup on my original machine to ensure that I haven''t missed anything - just gotten onnv3.4 BE up and running. Will let you know how it goes. Thanks. PS. My laptop actually hit a panic while booting the xvm bits. I had to disable the IEEE1394 devices in the BIOS before I was able to boot. This is a Dell Latitude D630. Anyone know anything more about this?> > > > MRJ > > > >> disk = [ >> ''file:/export/home/sid/Xen-configs/Windows2008/win2k8-disk.raw,hda,w'', >> ''file:/Seagate/Downloads/ISOs/windows.iso,hdc:cdrom,r'' >> ] >> >> memory = 1024 >> name = "Windows2008" >> kernel = "/usr/lib/xen/boot/hvmloader" >> builder = ''hvm'' >> vif = [ ''type=ioemu'' ] >> >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''preserve'' >> >> boot = ''d'' >> acpi=1 >> apic=1 >> vnc=1 >> vnclisten = "0.0.0.0" >> vncpasswd='''' >> viridian=1 >> usb=1 >> usbdevice="tablet" >> >> device_model = ''/usr/lib/xen/bin/qemu-dm'' >> >> -x-x-x-x-x- >> >> Thanks. >> >> -Siddharth >>> >>> MRJ >>> >>> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >
On Tue, Jun 30, 2009 at 9:19 AM, Siddharth Karnik<sidkarnik@gmail.com> wrote:> On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> wrote: >> >> Hi Siddharth, >> >>> >>> Nope. This still doesn''t work for me. >>> >>> Here is my config file for the Win2k8 domain. Maybe there''s something >>> else in here that I need to do.... >>> >>> Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get >>> the same result for 32-bit as well. >>> >>> x-x-x-x-x-x-x- >> >> I''ve lost track of this thread.. Did you get win2k8 to work for >> you? > > I actually got this working on another machine. This is an updated > 2009.06 laptop - using xen 3.1.4 > > I''m trying to redo the setup on my original machine to ensure that I > haven''t missed anything - just gotten onnv3.4 BE up and running. Will > let you know how it goes. > > Thanks. > > PS. My laptop actually hit a panic while booting the xvm bits. I had > to disable the IEEE1394 devices in the BIOS before I was able to boot. > This is a Dell Latitude D630. Anyone know anything more about this? > >Mark, I re-did the setup - but no cigar :-( Curiously, this didn''t work for the xvm 3.1.4 bits either. Here''s the setup: AMD 5000+ Dual core processor 4GB RAM 1TB Seagate SATA Once again, neither xvm 3.1.4 nor the updated 3.4.0 bits are able to setup Windows 2008 for me (Win2k3 works though). I have another 40 GB HDD with OpenSuse 11.1 - and the xen bits there seem to work OK - so I''m guessing its not a hardware issue. Also, I have a Dell Latitide D630 with a T7300 Dual core Intel processor, and at least the 3.1.4 bits here work - I am able to load Windows 2008 in an HVM domU. This looks like an AMD specific issue. Any idea how I might go about debugging this issue? Thanks. -Siddharth>> >> >> >> MRJ >> >> >> >>> disk = [ >>> ''file:/export/home/sid/Xen-configs/Windows2008/win2k8-disk.raw,hda,w'', >>> ''file:/Seagate/Downloads/ISOs/windows.iso,hdc:cdrom,r'' >>> ] >>> >>> memory = 1024 >>> name = "Windows2008" >>> kernel = "/usr/lib/xen/boot/hvmloader" >>> builder = ''hvm'' >>> vif = [ ''type=ioemu'' ] >>> >>> on_poweroff = ''destroy'' >>> on_reboot = ''restart'' >>> on_crash = ''preserve'' >>> >>> boot = ''d'' >>> acpi=1 >>> apic=1 >>> vnc=1 >>> vnclisten = "0.0.0.0" >>> vncpasswd='''' >>> viridian=1 >>> usb=1 >>> usbdevice="tablet" >>> >>> device_model = ''/usr/lib/xen/bin/qemu-dm'' >>> >>> -x-x-x-x-x- >>> >>> Thanks. >>> >>> -Siddharth >>>> >>>> MRJ >>>> >>>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >> >
Siddharth Karnik wrote:> On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> wrote: >> Hi Siddharth, > > PS. My laptop actually hit a panic while booting the xvm bits. I had > to disable the IEEE1394 devices in the BIOS before I was able to boot. > This is a Dell Latitude D630. Anyone know anything more about this?Did you get a stack trace for this? Thanks, MRJ
Siddharth Karnik wrote:> On Tue, Jun 30, 2009 at 9:19 AM, Siddharth Karnik<sidkarnik@gmail.com> wrote: >> On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> wrote: >>> Hi Siddharth, > > Mark, > > I re-did the setup - but no cigar :-( > > Curiously, this didn''t work for the xvm 3.1.4 bits either. Here''s the setup: > > AMD 5000+ Dual core processor > 4GB RAM > 1TB Seagate SATA > > Once again, neither xvm 3.1.4 nor the updated 3.4.0 bits are able to > setup Windows 2008 for me (Win2k3 works though). I have another 40 GB > HDD with OpenSuse 11.1 - and the xen bits there seem to work OK - so > I''m guessing its not a hardware issue. > > Also, I have a Dell Latitide D630 with a T7300 Dual core Intel > processor, and at least the 3.1.4 bits here work - I am able to load > Windows 2008 in an HVM domU. > > This looks like an AMD specific issue. Any idea how I might go about > debugging this issue?Hmmm, I''ll see if I can reproduce it. I''ve sent an e-mail to AMD to see if they have any ideas too.. MRJ
Siddharth Karnik wrote:> Once again, neither xvm 3.1.4 nor the updated 3.4.0 bits are able to > setup Windows 2008 for me (Win2k3 works though). I have another 40 GB > HDD with OpenSuse 11.1 - and the xen bits there seem to work OK - so > I''m guessing its not a hardware issue.Just to clarify, you are able to install 64-bit win2008 on a OpenSuse 11.1 dom0? Thanks, MRJ
Siddharth Karnik wrote:> On Tue, Jun 30, 2009 at 9:19 AM, Siddharth Karnik<sidkarnik@gmail.com> wrote: >> On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> wrote: >>> Hi Siddharth, >>> >>>> Nope. This still doesn''t work for me. >>>> >>>> Here is my config file for the Win2k8 domain. Maybe there''s something >>>> else in here that I need to do.... >>>> >>>> Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get >>>> the same result for 32-bit as well. >>>> >>>> x-x-x-x-x-x-x- >>> I''ve lost track of this thread.. Did you get win2k8 to work for >>> you? >> I actually got this working on another machine. This is an updated >> 2009.06 laptop - using xen 3.1.4 >> >> I''m trying to redo the setup on my original machine to ensure that I >> haven''t missed anything - just gotten onnv3.4 BE up and running. Will >> let you know how it goes. >> >> Thanks. >> >> PS. My laptop actually hit a panic while booting the xvm bits. I had >> to disable the IEEE1394 devices in the BIOS before I was able to boot. >> This is a Dell Latitude D630. Anyone know anything more about this? >> >> > > Mark, > > I re-did the setup - but no cigar :-( > > Curiously, this didn''t work for the xvm 3.1.4 bits either. Here''s the setup: > > AMD 5000+ Dual core processor > 4GB RAM > 1TB Seagate SATA > > Once again, neither xvm 3.1.4 nor the updated 3.4.0 bits are able to > setup Windows 2008 for me (Win2k3 works though). I have another 40 GB > HDD with OpenSuse 11.1 - and the xen bits there seem to work OK - so > I''m guessing its not a hardware issue. > > Also, I have a Dell Latitide D630 with a T7300 Dual core Intel > processor, and at least the 3.1.4 bits here work - I am able to load > Windows 2008 in an HVM domU. > > This looks like an AMD specific issue. Any idea how I might go about > debugging this issue?I''ve just installed 64-bit win2k8 on two different AMD machines (rev F machine; and 4 socket, 16-way Barcelona machine). one on 3.1.4 bits, and one with 3.3.2 bits. I tried with 1 vcpu and with 2 vcpus. Both worked fine? Not sure how I can help you unless you can come up with a case where it doesn''t fail or a config that we can reproduce the problem. MRJ Here''s one of my configs.. (domain (domid 8) (on_crash destroy) (uuid 9e5ef01b-489a-4422-4cdd-7dd3089652ec) (bootloader_args ) (vcpus 2) (name win2k8) (on_poweroff destroy) (on_reboot destroy) (bootloader ) (maxmem 2048) (memory 2048) (shadow_memory 18) (features ) (on_xend_start ignore) (on_xend_stop shutdown) (start_time 1246469662.76) (cpu_time 137.723414682) (online_vcpus 2) (distro_type windows) (distro_variant win2k8) (image (hvm (kernel ) (hpet 0) (loader /usr/lib/xen/boot/hvmloader) (serial pty) (boot d) (rtc_timeoffset 0) (pae 1) (viridian 1) (acpi 1) (localtime 1) (timer_mode 1) (apic 1) (usbdevice tablet) (device_model /usr/lib/xen/bin/qemu-dm) (keymap en-us) (usb 1) (notes (SUSPEND_CANCEL 1)) ) ) (status 2) (state r-----) (store_mfn 524285) (device (vif (bridge e1000g0) (mac 00:16:36:3f:c6:a3) (script /usr/lib/xen/scripts/vif-vnic) (uuid abc1ff55-b363-6800-5e98-f07379d12d30) (backend 0) ) ) (device (vbd (uname file:/net/heaped/export/isos/win2k8-64.iso) (uuid f88e96f3-7961-f08b-26ae-7b954b2f5b38) (mode r) (dev hdc:cdrom) (backend 0) (bootable 0) (VDI ) ) ) (device (vkbd (backend 0))) (device (vfb (vncunused 1) (keymap en-us) (type vnc) (uuid c472d73c-4d5f-4a8b-f6fd-381581867df3) (location localhost:5900) ) ) (device (console (protocol vt100) (location 4) (uuid a6ec8973-6fbe-191a-b515-0c5376b7a6b2) ) ) (device (tap (uname tap:vdisk:/net/heaped/export/dom/mrj/vdisks/win2k8/disk0) (uuid 15d38ecf-04db-085c-8cba-76e70cdf4bcc) (mode w) (dev hda:disk) (backend 0) (bootable 1) (VDI ) ) ) )
On Thu, Jul 2, 2009 at 2:19 AM, Mark Johnson<Mark.Johnson@sun.com> wrote:> > > Siddharth Karnik wrote: >> >> On Tue, Jun 30, 2009 at 9:19 AM, Siddharth Karnik<sidkarnik@gmail.com> >> wrote: >>> >>> On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> >>> wrote: >>>> >>>> Hi Siddharth, >>>> >>>>> Nope. This still doesn''t work for me. >>>>> >>>>> Here is my config file for the Win2k8 domain. Maybe there''s something >>>>> else in here that I need to do.... >>>>> >>>>> Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get >>>>> the same result for 32-bit as well. >>>>> >>>>> x-x-x-x-x-x-x- >>>> >>>> I''ve lost track of this thread.. Did you get win2k8 to work for >>>> you? >>> >>> I actually got this working on another machine. This is an updated >>> 2009.06 laptop - using xen 3.1.4 >>> >>> I''m trying to redo the setup on my original machine to ensure that I >>> haven''t missed anything - just gotten onnv3.4 BE up and running. Will >>> let you know how it goes. >>> >>> Thanks. >>> >>> PS. My laptop actually hit a panic while booting the xvm bits. I had >>> to disable the IEEE1394 devices in the BIOS before I was able to boot. >>> This is a Dell Latitude D630. Anyone know anything more about this? >>> >>> >> >> Mark, >> >> I re-did the setup - but no cigar :-( >> >> Curiously, this didn''t work for the xvm 3.1.4 bits either. Here''s the >> setup: >> >> AMD 5000+ Dual core processor >> 4GB RAM >> 1TB Seagate SATA >> >> Once again, neither xvm 3.1.4 nor the updated 3.4.0 bits are able to >> setup Windows 2008 for me (Win2k3 works though). I have another 40 GB >> HDD with OpenSuse 11.1 - and the xen bits there seem to work OK - so >> I''m guessing its not a hardware issue. >> >> Also, I have a Dell Latitide D630 with a T7300 Dual core Intel >> processor, and at least the 3.1.4 bits here work - I am able to load >> Windows 2008 in an HVM domU. >> >> This looks like an AMD specific issue. Any idea how I might go about >> debugging this issue? > > I''ve just installed 64-bit win2k8 on two different > AMD machines (rev F machine; and 4 socket, 16-way > Barcelona machine). one on 3.1.4 bits, and one with > 3.3.2 bits. I tried with 1 vcpu and with 2 vcpus. > > Both worked fine? Not sure how I can help you unless you > can come up with a case where it doesn''t fail or a config > that we can reproduce the problem. > >Mark, I re-built all - this time I installed the debug packages that resulted from a clean build of the source. I''ve attached the output of ''xm dmesg'' immediately after I see the blue screen. Maybe there''s something in there thats wrong. One thing I did notice was the "traps.c:2801: GPF (0000): ffff828c801a4bd3 -> ffff828c801f3353" message right at the bottom of the dmesg output. Maybe the two are realted? Thanks. -Siddharth> > > MRJ > > > > > > Here''s one of my configs.. > > > (domain > (domid 8) > (on_crash destroy) > (uuid 9e5ef01b-489a-4422-4cdd-7dd3089652ec) > (bootloader_args ) > (vcpus 2) > (name win2k8) > (on_poweroff destroy) > (on_reboot destroy) > (bootloader ) > (maxmem 2048) > (memory 2048) > (shadow_memory 18) > (features ) > (on_xend_start ignore) > (on_xend_stop shutdown) > (start_time 1246469662.76) > (cpu_time 137.723414682) > (online_vcpus 2) > (distro_type windows) > (distro_variant win2k8) > (image > (hvm > (kernel ) > (hpet 0) > (loader /usr/lib/xen/boot/hvmloader) > (serial pty) > (boot d) > (rtc_timeoffset 0) > (pae 1) > (viridian 1) > (acpi 1) > (localtime 1) > (timer_mode 1) > (apic 1) > (usbdevice tablet) > (device_model /usr/lib/xen/bin/qemu-dm) > (keymap en-us) > (usb 1) > (notes (SUSPEND_CANCEL 1)) > ) > ) > (status 2) > (state r-----) > (store_mfn 524285) > (device > (vif > (bridge e1000g0) > (mac 00:16:36:3f:c6:a3) > (script /usr/lib/xen/scripts/vif-vnic) > (uuid abc1ff55-b363-6800-5e98-f07379d12d30) > (backend 0) > ) > ) > (device > (vbd > (uname file:/net/heaped/export/isos/win2k8-64.iso) > (uuid f88e96f3-7961-f08b-26ae-7b954b2f5b38) > (mode r) > (dev hdc:cdrom) > (backend 0) > (bootable 0) > (VDI ) > ) > ) > (device (vkbd (backend 0))) > (device > (vfb > (vncunused 1) > (keymap en-us) > (type vnc) > (uuid c472d73c-4d5f-4a8b-f6fd-381581867df3) > (location localhost:5900) > ) > ) > (device > (console > (protocol vt100) > (location 4) > (uuid a6ec8973-6fbe-191a-b515-0c5376b7a6b2) > ) > ) > (device > (tap > (uname tap:vdisk:/net/heaped/export/dom/mrj/vdisks/win2k8/disk0) > (uuid 15d38ecf-04db-085c-8cba-76e70cdf4bcc) > (mode w) > (dev hda:disk) > (backend 0) > (bootable 1) > (VDI ) > ) > ) > ) >
On Mon, Jul 13, 2009 at 8:05 PM, Mark Johnson<Mark.Johnson@sun.com> wrote:> > Can you get a screenshot of the bluescreen and send it to me? > > > > Thanks, > > MRJ > >Attached.... Given that this happens just as the Windows 2k8 installer tries to switch to graphics mode, I''m guessing this has something to do with the VGA stuff. Is there any way I can help debug this? Unfortunately, I''m running on a machine that doesn''t have COM1 enabled (I don''t have the COM port connector hooked up to my motherboard) but I do have a "Prolific Technology Inc. USB-Serial Controller" Thanks. -Siddharth> > Siddharth Karnik wrote: >> >> On Thu, Jul 2, 2009 at 2:19 AM, Mark Johnson<Mark.Johnson@sun.com> wrote: >>> >>> Siddharth Karnik wrote: >>>> >>>> On Tue, Jun 30, 2009 at 9:19 AM, Siddharth Karnik<sidkarnik@gmail.com> >>>> wrote: >>>>> >>>>> On Tue, Jun 30, 2009 at 12:55 AM, Mark Johnson<Mark.Johnson@sun.com> >>>>> wrote: >>>>>> >>>>>> Hi Siddharth, >>>>>> >>>>>>> Nope. This still doesn''t work for me. >>>>>>> >>>>>>> Here is my config file for the Win2k8 domain. Maybe there''s something >>>>>>> else in here that I need to do.... >>>>>>> >>>>>>> Oh, I forgot to mention.... this is Win2k8 64-bit - although, I get >>>>>>> the same result for 32-bit as well. >>>>>>> >>>>>>> x-x-x-x-x-x-x- >>>>>> >>>>>> I''ve lost track of this thread.. Did you get win2k8 to work for >>>>>> you? >>>>> >>>>> I actually got this working on another machine. This is an updated >>>>> 2009.06 laptop - using xen 3.1.4 >>>>> >>>>> I''m trying to redo the setup on my original machine to ensure that I >>>>> haven''t missed anything - just gotten onnv3.4 BE up and running. Will >>>>> let you know how it goes. >>>>> >>>>> Thanks. >>>>> >>>>> PS. My laptop actually hit a panic while booting the xvm bits. I had >>>>> to disable the IEEE1394 devices in the BIOS before I was able to boot. >>>>> This is a Dell Latitude D630. Anyone know anything more about this? >>>>> >>>>> >>>> Mark, >>>> >>>> I re-did the setup - but no cigar :-( >>>> >>>> Curiously, this didn''t work for the xvm 3.1.4 bits either. Here''s the >>>> setup: >>>> >>>> AMD 5000+ Dual core processor >>>> 4GB RAM >>>> 1TB Seagate SATA >>>> >>>> Once again, neither xvm 3.1.4 nor the updated 3.4.0 bits are able to >>>> setup Windows 2008 for me (Win2k3 works though). I have another 40 GB >>>> HDD with OpenSuse 11.1 - and the xen bits there seem to work OK - so >>>> I''m guessing its not a hardware issue. >>>> >>>> Also, I have a Dell Latitide D630 with a T7300 Dual core Intel >>>> processor, and at least the 3.1.4 bits here work - I am able to load >>>> Windows 2008 in an HVM domU. >>>> >>>> This looks like an AMD specific issue. Any idea how I might go about >>>> debugging this issue? >>> >>> I''ve just installed 64-bit win2k8 on two different >>> AMD machines (rev F machine; and 4 socket, 16-way >>> Barcelona machine). one on 3.1.4 bits, and one with >>> 3.3.2 bits. I tried with 1 vcpu and with 2 vcpus. >>> >>> Both worked fine? Not sure how I can help you unless you >>> can come up with a case where it doesn''t fail or a config >>> that we can reproduce the problem. >>> >>> >> >> Mark, >> >> I re-built all - this time I installed the debug packages that >> resulted from a clean build of the source. >> >> I''ve attached the output of ''xm dmesg'' immediately after I see the blue >> screen. >> >> Maybe there''s something in there thats wrong. One thing I did notice >> was the "traps.c:2801: GPF (0000): ffff828c801a4bd3 -> >> ffff828c801f3353" message right at the bottom of the dmesg output. >> Maybe the two are realted? >> >> Thanks. >> >> -Siddharth >> >> >> >>> >>> MRJ >>> >>> >>> >>> >>> >>> Here''s one of my configs.. >>> >>> >>> (domain >>> (domid 8) >>> (on_crash destroy) >>> (uuid 9e5ef01b-489a-4422-4cdd-7dd3089652ec) >>> (bootloader_args ) >>> (vcpus 2) >>> (name win2k8) >>> (on_poweroff destroy) >>> (on_reboot destroy) >>> (bootloader ) >>> (maxmem 2048) >>> (memory 2048) >>> (shadow_memory 18) >>> (features ) >>> (on_xend_start ignore) >>> (on_xend_stop shutdown) >>> (start_time 1246469662.76) >>> (cpu_time 137.723414682) >>> (online_vcpus 2) >>> (distro_type windows) >>> (distro_variant win2k8) >>> (image >>> (hvm >>> (kernel ) >>> (hpet 0) >>> (loader /usr/lib/xen/boot/hvmloader) >>> (serial pty) >>> (boot d) >>> (rtc_timeoffset 0) >>> (pae 1) >>> (viridian 1) >>> (acpi 1) >>> (localtime 1) >>> (timer_mode 1) >>> (apic 1) >>> (usbdevice tablet) >>> (device_model /usr/lib/xen/bin/qemu-dm) >>> (keymap en-us) >>> (usb 1) >>> (notes (SUSPEND_CANCEL 1)) >>> ) >>> ) >>> (status 2) >>> (state r-----) >>> (store_mfn 524285) >>> (device >>> (vif >>> (bridge e1000g0) >>> (mac 00:16:36:3f:c6:a3) >>> (script /usr/lib/xen/scripts/vif-vnic) >>> (uuid abc1ff55-b363-6800-5e98-f07379d12d30) >>> (backend 0) >>> ) >>> ) >>> (device >>> (vbd >>> (uname file:/net/heaped/export/isos/win2k8-64.iso) >>> (uuid f88e96f3-7961-f08b-26ae-7b954b2f5b38) >>> (mode r) >>> (dev hdc:cdrom) >>> (backend 0) >>> (bootable 0) >>> (VDI ) >>> ) >>> ) >>> (device (vkbd (backend 0))) >>> (device >>> (vfb >>> (vncunused 1) >>> (keymap en-us) >>> (type vnc) >>> (uuid c472d73c-4d5f-4a8b-f6fd-381581867df3) >>> (location localhost:5900) >>> ) >>> ) >>> (device >>> (console >>> (protocol vt100) >>> (location 4) >>> (uuid a6ec8973-6fbe-191a-b515-0c5376b7a6b2) >>> ) >>> ) >>> (device >>> (tap >>> (uname >>> tap:vdisk:/net/heaped/export/dom/mrj/vdisks/win2k8/disk0) >>> (uuid 15d38ecf-04db-085c-8cba-76e70cdf4bcc) >>> (mode w) >>> (dev hda:disk) >>> (backend 0) >>> (bootable 1) >>> (VDI ) >>> ) >>> ) >>> ) >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >