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.