[Bug 469210] New: 64-bit HVM DomU installs fail @ incorrect ID of 64-bit CPU as 32-bit
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 Summary: 64-bit HVM DomU installs fail @ incorrect ID of 64-bit CPU as 32-bit Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: pgnet.trash@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Summary: I've a 64-bit AMD motherboard/cpu combo that supports AMD-V (smv) extension. The extensions are reported as available in kernel-default (/proc/cpuinfo) and by Xen Dom0 (xm dmesg). 64-bit PV DomU install's are no problem. But, 64-bit HVM DomU installs fail @ "Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode" for Windows 64-bit, and, "Cool software but, This is a 32-bit computer. You cannot use 64-bit software on it." for OS 11.1/64. I've been told (1) @Xen & (2) @Novell (https://bugzilla.novell.com/show_bug.cgi?id=467177) that it's likely a BIOS problem ("Masking"?), but initial checks with MSI & AMD both state that's NOT the case, and, as show below the extensions *are* seen ... Bottom line, 64-bit HVM's incorrectly ID the 64-bit CPU as 32-bit CPU, and fail to install. Details: I'm running, lsb_release -r Release: 11.1 uname -a Linux server 2.6.27.7-9-xen #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux motherboard is an MSI AM2-socket based, http://www.msicomputer.com/product/p_spec.asp?model=K9NBPM2-FID&class=mb CPU is an AMD 64 X2, Brisbane core @ 2.1GHz. cat /proc/cpuinfo | egrep "model name|cpu MHz" model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ cpu MHz : 2109.660 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ cpu MHz : 2109.660 http://products.amd.com/en-us/DesktopCPUDetail.aspx?id=60&f1=&f2=&f3=&f4=&f5=&f6=&f7=&f8=&f9=&f10= according to, http://en.wikipedia.org/wiki/Athlon_64_X2#Brisbane_.2865_nm_SOI.29 "MMX, Extended 3DNow!, SSE, SSE2, SSE3, AMD64, Cool'n'Quiet, NX Bit, AMD-V" and, http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors "HVM works with all CPUs featuring the AMD-V (SVM) extension. On a running system look for svm in the output of Linux' /proc/cpuinfo. ... it's certainly an AMD-V compatible CPU. further, comms from AMD support referred to this document, http://www.amd.com/us-en/assets/content_type/DownloadableAssets/35458_AMD_AV... wherein it specifically states, " WHAT ARE THE KEY ATTRIBUTES OF AVS PLATFORMS? ... AMD Virtualization (AMD-V) ... " and, specifically identifies, in the table titled "AVS MOTHERBOARD FEATURES & SPECIFICATIONS", this motherboard (MSI K9NBPM2-FID) as one of the AVS-compliant motherboards. also, a response from MSI tech support re: BIOS confirms, "The mb bios will auto enable the feature when a processor that supports AMD Live/V technology has been installed and used. There is no setting in the bios setup which is hidden." checking, under non-xen, kernel-default, cat /proc/cpuinfo | grep -i svm flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch 'svm' extension is "there". under kernel-xen, xen "says" svm is enabled/available, xm dmesg | grep -i svm (XEN) AMD SVM: ASIDs enabled. (XEN) HVM: SVM enabled (XEN) AMD SVM: ASIDs enabled. but, oddly, cat /proc/cpuinfo | grep -i svm (empty) On this X86_64 hardware, I can use/install in the following scenarios, with no problems: 64-bit OS Windows7 (beta) OK 64-bit OS 11.1, 64-bit kernel-default OK 64-bit OS 11.1, 64-bit kernel-xen/Dom0 OK 64-bit OS 11.1, 64-bit kernel-xen/Dom0 + 64-bit Linux/PV DomU OK but, 64-bit Xen HVM (pae=0) DomU installs fail @, (1) 64-bit OS 11.1, 64-bit Dom0 + 64-bit Windows7/HVM(pae=0) DomU (2) 64-bit OS 11.1, 64-bit Dom0 + 64-bit WinVista/HVM(pae=0) DomU Virtual Machine Console Windows Boot Manager File: \windows\system32\boot\winload.exe Status: 0xc000035a Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode and, (3) 64-bit OS 11.1, 64-bit Dom0 + 64-bit Opensuse 11.1/HVM(pae=0) DomU OpenSuse installer "Cool software but, This is a 32-bit computer. You cannot use 64-bit software on it." finally, checking in latest xen hg source, cd xen-3.3.1-testing find . | grep svm ./tools/ioemu-remote/target-i386/svm.h ./xen/include/asm-x86/hvm/svm ./xen/include/asm-x86/hvm/svm/amd-iommu-acpi.h ./xen/include/asm-x86/hvm/svm/emulate.h ./xen/include/asm-x86/hvm/svm/svm.h ./xen/include/asm-x86/hvm/svm/amd-iommu-defs.h ./xen/include/asm-x86/hvm/svm/asid.h ./xen/include/asm-x86/hvm/svm/vmcb.h ./xen/include/asm-x86/hvm/svm/amd-iommu-proto.h ./xen/include/asm-x86/hvm/svm/intr.h ./xen/arch/x86/hvm/svm ./xen/arch/x86/hvm/svm/svm.c ./xen/arch/x86/hvm/svm/Makefile ./xen/arch/x86/hvm/svm/entry.S ./xen/arch/x86/hvm/svm/vmcb.c ./xen/arch/x86/hvm/svm/asid.c ./xen/arch/x86/hvm/svm/intr.c ./xen/arch/x86/hvm/svm/emulate.c and, in opensuse's linux src, cd /usr/src/linux-2.6.27.7-9/arch/x86 grep -rlni svm . ./kvm/svm.h ./kvm/svm.c ./kvm/kvm_svm.h ./kvm/Kconfig ./kvm/Makefile ./mm/hugetlbpage.c ./kernel/cpu/feature_names.c ./kdb/x86_64-dis.c ./kdb/i386-dis.c note there's svm-related source files under ./kvm, but nothing under ./xen, grep -rlni svm xen/ (empty). is the fact that svm-related cource files are missing from there relevant? Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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#c1 --- Comment #1 from pgnet _ <pgnet.trash@gmail.com> 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 jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c2 Jason Douglas <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jdouglas@novell.com Info Provider| |pgnet.trash@gmail.com --- Comment #2 from Jason Douglas <jdouglas@novell.com> 2009-01-26 08:57:49 MST --- Based on this line in the description, (3) 64-bit OS 11.1, 64-bit Dom0 + 64-bit Opensuse 11.1/HVM(pae=0) DomU you are disabling "pae" in the VM config file. As soon as you do that, long mode (64-bit) is disabled as well. Please try setting pae=1 and report back on your findings. Thanks. -- 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 _ <pgnet.trash@gmail.com> 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 pgnet _ <pgnet.trash@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|pgnet.trash@gmail.com |jdouglas@novell.com -- 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 <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbeulich@novell.com, | |lbendixs@novell.com --- Comment #4 from Jason Douglas <jdouglas@novell.com> 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 jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c5 Jason Douglas <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jdouglas@novell.com | --- Comment #5 from Jason Douglas <jdouglas@novell.com> 2009-01-26 15:12:06 MST --- Sorry, inadvertently hit enter when focus was outside of this field ... Anyway, the flags in the VM config file tell xen which hardware features to present to the guest. In this case, pae=0 turns off not only 36-bit physical address extensions, but also disables 64-bit, effectively presenting the VM with 32-bit (emulated) hardware. That is the reason that you are getting the "Cool software, but ..." messages when you attempt to install a 64-bit operating system onto your VM. -- 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 _ <pgnet.trash@gmail.com> 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 pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c7 --- Comment #7 from pgnet _ <pgnet.trash@gmail.com> 2009-01-26 17:25:08 MST --- (having some technical difficulties running virt-manager as non-root ...) per advice, i changed to pae=1. for OS 11.1 x86_64 DomU, the installer no longer complains about a 32-bit cpu, and, after config, the installer starts. so we've made it past _that_. unfortunately, it's hung @56% complete, for the second time. i'll figure this out, and give Win7 a try ... -- 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 <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #8 from Jason Douglas <jdouglas@novell.com> 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 pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c9 pgnet _ <pgnet.trash@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #9 from pgnet _ <pgnet.trash@gmail.com> 2009-02-03 11:38:45 MST --- 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 ... -- 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 <lbendixs@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #10 from Lynn Bendixsen <lbendixs@novell.com> 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 pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c11 --- Comment #11 from pgnet _ <pgnet.trash@gmail.com> 2009-02-03 13:45:45 MST --- could someone please make that referenced bug visible? @ https://bugzilla.novell.com/show_bug.cgi?id=468233 "You are not authorized to access bug #468233" -- 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 <lbendixs@novell.com> 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 pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469210#c13 --- Comment #13 from pgnet _ <pgnet.trash@gmail.com> 2009-02-03 14:42:44 MST ---
... I cannot disclose the whole of it ...
ok
Have you tried rebooting the host yet?
countless times ...
Disabling or completely enabling the pv drivers in the Domu's may also help resolve the new issues.
specifically, how? my current state of affairs is: I've slimmed down my Dom0 to a nominal install, with no X11 -- having a full WM (KDE) installed just to view local virt-manager displays made no sense. installing Windows7/beta in HVM DomU: pae = 0 vif = [ 'type=ioemu,bridge=brINT' ] sdl = 0 stdvga = 0 vnc = 1 vncviewer = 1 vncconsole = 0 vncunused = 1 vncpasswd = '' acpi = 1 apic = 1 vnclisten = "192.168.1.2" @ xm create, virsh vncdisplay win7 192.168.1.2:0 connect @ VNC= 192.168.1.2:5900 displays Windows boot screen, dies @ 1st screen, Windows is loading files ... Attempting to load a 64-bit application, however this CPU in not compatible with 64-bit mode changing, - pae = 0 + pae = 1 connect @ VNC= 192.168.1.2:5900 displays Windows boot screen, passes 1st screen, Windows is loading files ... no longer 'complaining' about the 32-bitness of the CPU, then simply stalls @ 2nd screen, Starting WIndows & gets no further. 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. -- 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 <lbendixs@novell.com> 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.
may be something we need to look at and try to duplicate. We're still hoping
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#c15 --- Comment #15 from pgnet _ <pgnet.trash@gmail.com> 2009-02-03 15:13:46 MST --- Created an attachment (id=269800) --> (https://bugzilla.novell.com/attachment.cgi?id=269800) logs @ OS 11.1 HVM install, where no VNC access that your configuration has something to do with it ;) but once we have tried it more we'll have a better idea. below i've included the latest/current iteration ...
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.
yes, that's where i'd started awhile ago. admittedly, i've monkeyed around a lot. that said, i'll try it again, and report back. for now, the above mentioned 'details': Dom0, uname -a Linux server 2.6.27.7-9-xen #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux cat win7_init.cfg --------- name = "win7" builder = "hvm" device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" memory = 1024 maxmem = 1024 vcpus = 2 disk = [ 'phy:/dev/VG_DomU/win7,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ] boot = "dc" vif = [ 'type=ioemu,bridge=brINT' ] sdl = 0 stdvga = 0 pae = 1 vnc = 1 vncviewer = 1 vncconsole = 0 vncunused = 1 vncpasswd = '' acpi = 1 apic = 1 vnclisten = "172.30.11.2" extid = 1 localtime = 1 serial = "pty" usb = 1 usbdevice = 'tablet' on_poweroff = "destroy" on_reboot = "destroy" on_crash = "destroy" --------- for Opensuse 11.1 HVM in DomU, @ xm create win7_init.cfg Using config file "/home/xen/vm/win7/win7_init.cfg". VNC= 1 /tmp/launch-afI1hD/: unknown host. (nodename nor servname provided, or not known) Started domain win7 /tmp/launch-afI1hD/: unknown host. (nodename nor servname provided, or not known) log output attached for: /var/log/messages /var/log/xen/*log also, in the attachement, verbose logs from the local VNC client. @ VNC connect attempt to 172.30.11.2:5900, where, virsh vncdisplay win7 172.30.11.2:0 and the aformentioned config. -- 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 _ <pgnet.trash@gmail.com> 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#c17 --- Comment #17 from pgnet _ <pgnet.trash@gmail.com> 2009-02-03 16:57:16 MST --- time to move on. in summary, for OS 11.1 64-bit HVM DomU on X86_64, ignore info & examples that: -- `cat /proc/cpuinfo` should contain 'svm' (under kernel-xen) -- pae=1 is only for 32-bit domains -- stdvga=0 is default for HVM installs instead, set: pae=1 stdvga=1 for Win7-64/beta HVM DomU on X86_64 ... doesn't work yet. thanks for the help. -- 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 _ <pgnet.trash@gmail.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com