https://bugzilla.novell.com/show_bug.cgi?id=469210 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c1 --- Comment #1 from pgnet _ 2009-01-25 09:10:32 MST --- Created an attachment (id=267509) --> (https://bugzilla.novell.com/attachment.cgi?id=267509) output of 'x86info --all -v', kernel-xen case for additional reference, here's the verbose output of the 'x86info' util, for the kernel-xen case note reference to, SVM: revision 0, 0 ASIDs but 'svm' is missing from "Feature flags" & "Extended feature flags" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c3 --- Comment #3 from pgnet _ 2009-01-26 09:30:26 MST --- a question 1st ... as I understand, pae enables 4GB < X < 32GB of physical memory to be used in 32-bit systems. i'm attempting to install *64* bit guest on *64* bit host. setting pae=1 instructs the guest to use a PAE kernel, no? and that's not supported;. e.g., @ http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx. "PAE is supported only on 32-bit versions of the Windows operating system. 64-bit versions of Windows do not support PAE." correct? not? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c4 Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbeulich@novell.com, | |lbendixs@novell.com --- Comment #4 from Jason Douglas 2009-01-26 15:04:37 MST --- In this case pae=1 has nothing to do with what kernel will be used in the guest. Instead, by -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c6 --- Comment #6 from pgnet _ 2009-01-26 15:22:23 MST --- Fair enough. I'll give it a whirl with both OS11.1 & Win7 64-bit DomUs here in a bit ... TBH, this (setting pae=1 for 64-bit DomU) runs contrary to eveything I've managed to find to read, so clearly I've missed something rather important :-/ Can you, off-hand, 'point' to docs about this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c8 Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #8 from Jason Douglas 2009-02-03 11:04:40 MST --- Since pae=1 allowed the installation to start appropriately, we are going to close this issue. Please feel free to open additional bugs for any other issues you encounter. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User lbendixs@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c10 Lynn Bendixsen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #10 from Lynn Bendixsen 2009-02-03 12:45:42 MST --- (In reply to comment #9)

well, actually, i'm still flailing away at this ...

i've moved to a minimal Dom0 -- no X11 -- and am unable to get *any* sort of VNC-view of any HVM client. PV-installs work all-day-long ...

This last could be a duplicate of 468233. To work around the issue in that bug, reboot the host system and the problem will be resolved (perhaps only temporarily) If it is not a duplicate of 468233 this new issue still needs to be opened as a new bug for our tracking purposes. Sorry for the inconvenience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User lbendixs@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c12 --- Comment #12 from Lynn Bendixsen 2009-02-03 14:28:34 MST --- Ah, I apologize, that bug is a partner bug and for privacy reasons I cannot disclose the whole of it. To summarize: the partner was installing several fully virtual Code 11 VM's on a SLES11 SP2 host and was seeing an inability to access some of the consoles remotely after rebooting the VM's sometimes. The problem appeared to be at least partly in the host as the problem has not been seen since trying SLES11 RC3. SLES 11 RC3 had some dbus and some pv driver fixes in it that we think solved the problems. Have you tried rebooting the host yet? Disabling or completely enabling the pv drivers in the Domu's may also help resolve the new issues. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User lbendixs@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c14 --- Comment #14 from Lynn Bendixsen 2009-02-03 15:04:10 MST --- (In reply to comment #13)

no longer 'complaining' about the 32-bitness of the CPU, then simply stalls @ 2nd screen,

Starting WIndows

& gets no further.

We see this here for Windows 7 also. This issue will get higher priority attention as Win7 gets closer to shipping. But this:

Attempting the same with Opensuse 11.1/X86_64 as an HVM install -- either with pae=0,1 -- i've been unable to get any sort of VNC display at all in my current headless, X11-less Dom0 config. depending on the permutations of the various xm config parameters, i get connections with black screens, refused connections, "Alarm Clock" (???) messages at shell, etc etc but no installer display @ VNC -- yet.

may be something we need to look at and try to duplicate. We're still hoping that your configuration has something to do with it ;) but once we have tried it more we'll have a better idea. Have you tried using vm-install yet? It sets up a VM with parameters that are known to work,then maybe you can tweak it from there. Thanks for the report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c16 --- Comment #16 from pgnet _ 2009-02-03 16:01:11 MST --- exploring the cfg files created by, "vm-install --noinstall ..." the 'trick' seems to be, for installing OS 11.1 as HVM Domu, to change: - vif = [ 'type=ioemu,bridge=brINT' ] - stdvga = 0 + vif = [ 'mac=00:16:3E:02:01:00,bridge=brINT' ] + stdvga = 1 ( fyi, @ http://www.virtuatopia.com/index.php/Installing_and_Running_Windows_XP_or_Vi..., adivce is "stdvga = 0", & @, http://en.opensuse.org/Xen_Full_Virtualization_Example, there no mentioned of the param made, other that to start with "/etc/xen/examples/xmexample.hvm", where, grep stdvga /etc/xen/examples/xmexample.hvm # enable stdvga, default = 0 (use cirrus logic device model) stdvga=0 ) then @ xm create, installer starts & gets to: "Your computer does not fulfill all requirements for a graphical installation. There is less than 96 MB memory or the X server could not be started. As a fallback, the text from-end of YaST will guide you ..." I've allocated (above) 1024M to the DomU, and the install disk should (?) have an X server ... so unclear why the message, and why not graphical console. Nonetheless, continuing in text-mode, selecting auto config, default partitioning & full kde 4.1, the install is proceeding (sloooowly ... another ~45 mins ...). checking, xm info win7 | egrep "machine|hvm" machine : x86_64 virt_caps : hvm max_hvm_memory : 5790 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 it _looks_ like it's, in fact, a full 64-bit DomU install (will be sure when the install completes, i suppose). Question: if this is all "OK", then clearly i've the amd/svm extensions required to do the HVM install. then, why does: cat /proc/cpuinfo | grep -i svm return (empty), but, foor non-xen, kernel-default, it's "there"? also, @ attempts to listen directly to the DomU installer's VNC server, changing, - vif = [ 'mac=00:16:3E:02:01:00,bridge=brINT' ] - vnclisten = "172.30.11.2" + vif = [ 'ip=172.30.11.201,mac=00:16:3E:02:01:00,bridge=brINT' ] + vnclisten = "172.30.11.201" currently result in simply a report of, "Alarm clock" @ shell, followed by an immediate quit of the vm launch. working on that too ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=469210 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c18 --- Comment #18 from pgnet _ 2009-02-03 17:14:41 MST --- it seems that the pae=1 stdvga=1 settings get one into the Win7/beta installer as well! currently installing, via graphical display in VNC window (no problems like OS 11.1, above), and no complaints about 32-bitness. progress ... any further issues, i'll take to the list. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.