Valtteri Kiviniemi
2012-Oct-03 13:05 UTC
Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
Hi, I am trying to get Windows Server 2008 R2 HVM domU working in Xen 4.2.0. The domU will start and I can see the boot output to the point when the .iso-image starts loading and I get the "Windows is loading files" loading bar in VNC. After the Windows installer has finished loading the necessary files and starts the installer the resolution will change on the VNC screen and it goes black. However despite that, I think that the Windows installer is still starting fine and it probably is responding to keyboard input, I just cant see anything but black. Qemu-dm log file does not contain any error messages. I''m using the same config file on different server and it is working there, and when comparing the qemu-dm log files on this server and the other server where the windows is working they are pretty much consistent. I have tried playing with different settings on domU config, but nothing makes any difference, the outcome is always the same. Installer starts, resolution changes and then only black. I''am using rather new hardware, CPU is the new Intel Ivy-Bridge Core i7-3770 with integrated GPU and motherboard is Intel DQ77MK with latest bios installed. dom0 kernel is 3.6.0 64bit, hypervisor is 64bit and Windows is 64bit. The same kernel config and domU config is working on my older server which is running mid 2008 CPU Intel Q9950 and motherboard Intel DQ45CB, so I would suspect that this might be some kind of hardware incompatibility problem? Any ideas of how to debug this problem? I have enabled all the debuggint options for Xen and dom0 kernel but I''m not getting any error messages. It seems that the domU is working as intented but only graphics are missing. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 13:22 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
Hi, Tested with realvnc and tightvnc. Realvnc just closes itself when the resolution changes and tightvnc just stays open with the black screen. - Valtteri 2012/10/3 chris <tknchris@gmail.com>> What vnc client I''ve seen this on os x > On Oct 3, 2012 9:08 AM, "Valtteri Kiviniemi" <kiviniemi.valtteri@gmail.com> > wrote: > >> Hi, >> >> I am trying to get Windows Server 2008 R2 HVM domU working in Xen 4.2.0. >> The domU will start and I can see the boot output to the point when the >> .iso-image starts loading and I get the "Windows is loading files" loading >> bar in VNC. After the Windows installer has finished loading the necessary >> files and starts the installer the resolution will change on the VNC screen >> and it goes black. However despite that, I think that the Windows installer >> is still starting fine and it probably is responding to keyboard input, I >> just cant see anything but black. Qemu-dm log file does not contain any >> error messages. I''m using the same config file on different server and it >> is working there, and when comparing the qemu-dm log files on this server >> and the other server where the windows is working they are pretty much >> consistent. >> >> I have tried playing with different settings on domU config, but nothing >> makes any difference, the outcome is always the same. Installer starts, >> resolution changes and then only black. I''am using rather new hardware, CPU >> is the new Intel Ivy-Bridge Core i7-3770 with integrated GPU and >> motherboard is Intel DQ77MK with latest bios installed. dom0 kernel is >> 3.6.0 64bit, hypervisor is 64bit and Windows is 64bit. The same kernel >> config and domU config is working on my older server which is running mid >> 2008 CPU Intel Q9950 and motherboard Intel DQ45CB, so I would suspect that >> this might be some kind of hardware incompatibility problem? >> >> Any ideas of how to debug this problem? I have enabled all the debuggint >> options for Xen and dom0 kernel but I''m not getting any error messages. It >> seems that the domU is working as intented but only graphics are missing. >> >> - Valtteri >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >> >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Konrad Rzeszutek Wilk
2012-Oct-03 13:33 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> wrote:> Hi, > > Tested with realvnc and tightvnc. Realvnc just closes itself when the > resolution changes and tightvnc just stays open with the black screen. >Lets first see if this is a problem with Windows 2008 expecting certain registers in the VGA emulation and falling flat on its face. If you launch (with the same guest config - but obviously replace the ISO), with an Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC screen changing resolution and all that?> - Valtteri > > 2012/10/3 chris <tknchris@gmail.com> >> >> What vnc client I''ve seen this on os x >> >> On Oct 3, 2012 9:08 AM, "Valtteri Kiviniemi" >> <kiviniemi.valtteri@gmail.com> wrote: >>> >>> Hi, >>> >>> I am trying to get Windows Server 2008 R2 HVM domU working in Xen 4.2.0. >>> The domU will start and I can see the boot output to the point when the >>> .iso-image starts loading and I get the "Windows is loading files" loading >>> bar in VNC. After the Windows installer has finished loading the necessary >>> files and starts the installer the resolution will change on the VNC screen >>> and it goes black. However despite that, I think that the Windows installer >>> is still starting fine and it probably is responding to keyboard input, I >>> just cant see anything but black. Qemu-dm log file does not contain any >>> error messages. I''m using the same config file on different server and it is >>> working there, and when comparing the qemu-dm log files on this server and >>> the other server where the windows is working they are pretty much >>> consistent. >>> >>> I have tried playing with different settings on domU config, but nothing >>> makes any difference, the outcome is always the same. Installer starts, >>> resolution changes and then only black. I''am using rather new hardware, CPU >>> is the new Intel Ivy-Bridge Core i7-3770 with integrated GPU and motherboard >>> is Intel DQ77MK with latest bios installed. dom0 kernel is 3.6.0 64bit, >>> hypervisor is 64bit and Windows is 64bit. The same kernel config and domU >>> config is working on my older server which is running mid 2008 CPU Intel >>> Q9950 and motherboard Intel DQ45CB, so I would suspect that this might be >>> some kind of hardware incompatibility problem? >>> >>> Any ideas of how to debug this problem? I have enabled all the debuggint >>> options for Xen and dom0 kernel but I''m not getting any error messages. It >>> seems that the domU is working as intented but only graphics are missing. >>> >>> - Valtteri >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xen.org >>> http://lists.xen.org/xen-devel >>> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >
Valtteri Kiviniemi
2012-Oct-03 13:48 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
2012/10/3 Konrad Rzeszutek Wilk <konrad@kernel.org>> On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi > <kiviniemi.valtteri@gmail.com> wrote: > > Hi, > > > > Tested with realvnc and tightvnc. Realvnc just closes itself when the > > resolution changes and tightvnc just stays open with the black screen. > > > > Lets first see if this is a problem with Windows 2008 expecting > certain registers in the VGA > emulation and falling flat on its face. > > If you launch (with the same guest config - but obviously replace the > ISO), with an > Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC screen > changing resolution > and all that? > >Hi, Same problem with Fedora-17-x86_64-Live-Desktop.iso. I after the resolution changed the screen goes black. If I change stdvga to 1 I will see a bit further but then the VNC client crashes and says something about unsupported features (dont know even if it should work). - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-03 13:57 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
On Wed, Oct 03, 2012 at 04:48:33PM +0300, Valtteri Kiviniemi wrote:> 2012/10/3 Konrad Rzeszutek Wilk <[1]konrad@kernel.org> > > On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi > <[2]kiviniemi.valtteri@gmail.com> wrote: > > Hi, > > > > Tested with realvnc and tightvnc. Realvnc just closes itself when the > > resolution changes and tightvnc just stays open with the black screen. > > > > Lets first see if this is a problem with Windows 2008 expecting > certain registers in the VGA > emulation and falling flat on its face. > > If you launch (with the same guest config - but obviously replace the > ISO), with an > Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC screen > changing resolution > and all that? > > Hi, > > Same problem with Fedora-17-x86_64-Live-Desktop.iso. I after the > resolution changed the screen goes black. If I change stdvga to 1 I will > see a bit further but then the VNC client crashes and says something about > unsupported features (dont know even if it should work). >Did you try xvnc4viewer? or normal vncviewer? or virt-viewer? I usually use virt-viewer without problems.. -- Pasi
Valtteri Kiviniemi
2012-Oct-03 14:11 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
2012/10/3 Pasi Kärkkäinen <pasik@iki.fi>> On Wed, Oct 03, 2012 at 04:48:33PM +0300, Valtteri Kiviniemi wrote: > > 2012/10/3 Konrad Rzeszutek Wilk <[1]konrad@kernel.org> > > > > On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi > > <[2]kiviniemi.valtteri@gmail.com> wrote: > > > Hi, > > > > > > Tested with realvnc and tightvnc. Realvnc just closes itself when > the > > > resolution changes and tightvnc just stays open with the black > screen. > > > > > > > Lets first see if this is a problem with Windows 2008 expecting > > certain registers in the VGA > > emulation and falling flat on its face. > > > > If you launch (with the same guest config - but obviously replace > the > > ISO), with an > > Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC screen > > changing resolution > > and all that? > > > > Hi, > > > > Same problem with Fedora-17-x86_64-Live-Desktop.iso. I after the > > resolution changed the screen goes black. If I change stdvga to 1 I > will > > see a bit further but then the VNC client crashes and says something > about > > unsupported features (dont know even if it should work). > > > > Did you try xvnc4viewer? or normal vncviewer? or virt-viewer? > I usually use virt-viewer without problems.. > > -- Pasi > >Hi, I''m using Windows 7 in my desktop-computer, so I have not tested any other vnc clients than ultravnc or tightvnc. I can of course test others too if there is windows binary available. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 14:19 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> > > 2012/10/3 Pasi Kärkkäinen <pasik@iki.fi> > >> On Wed, Oct 03, 2012 at 04:48:33PM +0300, Valtteri Kiviniemi wrote: >> > 2012/10/3 Konrad Rzeszutek Wilk <[1]konrad@kernel.org> >> > >> > On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi >> > <[2]kiviniemi.valtteri@gmail.com> wrote: >> > > Hi, >> > > >> > > Tested with realvnc and tightvnc. Realvnc just closes itself >> when the >> > > resolution changes and tightvnc just stays open with the black >> screen. >> > > >> > >> > Lets first see if this is a problem with Windows 2008 expecting >> > certain registers in the VGA >> > emulation and falling flat on its face. >> > >> > If you launch (with the same guest config - but obviously replace >> the >> > ISO), with an >> > Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC screen >> > changing resolution >> > and all that? >> > >> > Hi, >> > >> > Same problem with Fedora-17-x86_64-Live-Desktop.iso. I after the >> > resolution changed the screen goes black. If I change stdvga to 1 I >> will >> > see a bit further but then the VNC client crashes and says something >> about >> > unsupported features (dont know even if it should work). >> > >> >> Did you try xvnc4viewer? or normal vncviewer? or virt-viewer? >> I usually use virt-viewer without problems.. >> >> -- Pasi >> >> > Hi, > > I''m using Windows 7 in my desktop-computer, so I have not tested any other > vnc clients than ultravnc or tightvnc. I can of course test others too if > there is windows binary available. > > - Valtteri >Hi, Good news, I got it working. It seems that for some reason the encoding has to be RAW and stdvga has to be enabled. This is strange since this same config and setup is working on different hardware. But now I''m able to see the VNC output. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-03 14:21 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
On Wed, Oct 03, 2012 at 05:11:25PM +0300, Valtteri Kiviniemi wrote:> 2012/10/3 Pasi Kärkkäinen <[1]pasik@iki.fi> > > On Wed, Oct 03, 2012 at 04:48:33PM +0300, Valtteri Kiviniemi wrote: > > 2012/10/3 Konrad Rzeszutek Wilk <[1][2]konrad@kernel.org> > > > > On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi > > <[2][3]kiviniemi.valtteri@gmail.com> wrote: > > > Hi, > > > > > > Tested with realvnc and tightvnc. Realvnc just closes itself > when the > > > resolution changes and tightvnc just stays open with the black > screen. > > > > > > > Lets first see if this is a problem with Windows 2008 expecting > > certain registers in the VGA > > emulation and falling flat on its face. > > > > If you launch (with the same guest config - but obviously replace > the > > ISO), with an > > Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC screen > > changing resolution > > and all that? > > > > Hi, > > > > Same problem with Fedora-17-x86_64-Live-Desktop.iso. I after the > > resolution changed the screen goes black. If I change stdvga to 1 I > will > > see a bit further but then the VNC client crashes and says > something about > > unsupported features (dont know even if it should work). > > > > Did you try xvnc4viewer? or normal vncviewer? or virt-viewer? > I usually use virt-viewer without problems.. > -- Pasi > > Hi, > > I''m using Windows 7 in my desktop-computer, so I have not tested any other > vnc clients than ultravnc or tightvnc. I can of course test others too if > there is windows binary available. >I don''t think I''ve ever tried using from Windows :) How about installing Xming to your Windows box, and then use putty ssh X11 forwarding to dom0, and execute vncviewer/virt-viewer in dom0? You''ll get the vnc GUI displayed on your Windows. -- Pasi
Valtteri Kiviniemi
2012-Oct-03 14:29 UTC
Re: Xen 4.2.0, VNC connection to Windows domU causes black screen on VNC
2012/10/3 Pasi Kärkkäinen <pasik@iki.fi>> On Wed, Oct 03, 2012 at 05:11:25PM +0300, Valtteri Kiviniemi wrote: > > 2012/10/3 Pasi Kärkkäinen <[1]pasik@iki.fi> > > > > On Wed, Oct 03, 2012 at 04:48:33PM +0300, Valtteri Kiviniemi wrote: > > > 2012/10/3 Konrad Rzeszutek Wilk <[1][2]konrad@kernel.org> > > > > > > On Wed, Oct 3, 2012 at 9:22 AM, Valtteri Kiviniemi > > > <[2][3]kiviniemi.valtteri@gmail.com> wrote: > > > > Hi, > > > > > > > > Tested with realvnc and tightvnc. Realvnc just closes > itself > > when the > > > > resolution changes and tightvnc just stays open with the > black > > screen. > > > > > > > > > > Lets first see if this is a problem with Windows 2008 > expecting > > > certain registers in the VGA > > > emulation and falling flat on its face. > > > > > > If you launch (with the same guest config - but obviously > replace > > the > > > ISO), with an > > > Fedora or Ubuntu LiveCD - does it boot? Do you see the VNC > screen > > > changing resolution > > > and all that? > > > > > > Hi, > > > > > > Same problem with Fedora-17-x86_64-Live-Desktop.iso. I after > the > > > resolution changed the screen goes black. If I change stdvga > to 1 I > > will > > > see a bit further but then the VNC client crashes and says > > something about > > > unsupported features (dont know even if it should work). > > > > > > > Did you try xvnc4viewer? or normal vncviewer? or virt-viewer? > > I usually use virt-viewer without problems.. > > -- Pasi > > > > Hi, > > > > I''m using Windows 7 in my desktop-computer, so I have not tested any > other > > vnc clients than ultravnc or tightvnc. I can of course test others > too if > > there is windows binary available. > > > > I don''t think I''ve ever tried using from Windows :) > > How about installing Xming to your Windows box, and then use putty ssh X11 > forwarding to dom0, > and execute vncviewer/virt-viewer in dom0? You''ll get the vnc GUI > displayed on your Windows. > > -- Pasi > >Hi, No need anymore, since I got it working (see my earlier post). Somone should add this to the xen wiki/common problems. In my case stdvga needs to be enabled and then VNC connection type must be RAW. So in case someone has these kind of problems in the future, it would be good to mention this in wiki :) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel