Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480

[Flavio <fbcyborg@xxxxxxxxx>]

On 7 December 2011 07:15, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> Ok -  I got curious about your pv install method, and tried it myself. It
> actually did work, but you may not be aware of it.
>
> First, given your config, it looks like all you did was an 'xl create ...' to
> start your install.
Yes, I actually did xl create opensuse11.cfg && xl vncviewer `xl domid
OpenSuse11`
Then in the vnc viewer at a certain point, a message appears and it
says to enter the
domU via ssh. So performing the following command, the graphical setup starts:
ssh -X root@<domU_IP> and then start yast (see screenshots below).

At this point, I proceed with the graphical setup up to the end, where
a reboot is
required. Actually it says: "The system will reboot now. After reboot, reconnect
and run the following: /usr/lib/YaST2/startup/YaST2.ssh"

Here's a screenshot: http://goo.gl/8DKSF

At this point I tried to boot as you said, using pygrub, and it actually worked!
I don't know why it didn't work for me before!

I tried to xl create with the following config file:
name="OpenSuse11"
memory=1024
disk = ['file:/mnt/xen/vmstore/opensuse11/opensuse11.img,xvda,w' ]
vif = [ 'type=ioemu, mac=00:16:3e:00:00:21, bridge=xenbr0' ]
vfb = [ "type=vnc,vncunused=1,vnclisten=0.0.0.0,keymap=it" ]
stdvga=1
videoram=16
bootloader = "/usr/bin/pygrub"
vcpus=1
on_reboot = 'restart'
on_crash = 'destroy'

xl create opensuse11.cfg -c
I see the pygrub with the following kernels:
openSUSE 11.4 - 2.6.37.1-1.2 (default)
Xen -- openSUSE 11.4 - 2.6.37.1-1.2

I try to hit on Xen and it finally started!
so xl vncviewer `xl domid OpenSuse11` gives me the vnc window that stops at
this screen: http://goo.gl/4qMaV

At this point I can ssh -X root@xxxxxxxxxxxxx and issue the following command:
/usr/lib/YaST2/startup/YaST2.ssh, because I am now in the new system.

Finally the Automatic Configuration starts and I can finish the
installation process.
After that, the boot continues in the vnc viewer and I can proceed
with the login.
Of course the boot process continues on the domU console too (where
the pygrub started).
In this case, the mouse doesn't work for me too! :(
Let's investigate if some option is missing in the configuration file.
The pointer doesn't move but click works.
See this: 
http://xen.1045712.n5.nabble.com/OpenSuse-11-PV-domU-installation-problem-the-mouse-pointer-doesn-t-move-but-click-works-td4998460.html

I had this problem in the installation process before. The strange fact is that
the mouse works with yast but not with vnc.
Something tells me that it is a OpenSuse 11.4 issue, so I'm going to
download the
12.1 version of the DVD and to try a new PV setup (now that I know how
to complete
the setup!!!).

> You (again) didn't use something like virt-install / virt-
> manager to control your install. If so, you are only using xen tools, and
> nothing specific to Gentoo, and this approach would work on any distro's dom0.
Yes, I'm pretty sure of that.

>
> Anyway, that's what I did, with this config patterned after the one you
> posted, with local differences, and hvm directives removed (and by the way,
> 'vcpus' was misspelled):
Was it misspelled? I've checked. I didn't notice that. Anyway...

> [...]
> (This is what I mean about details of
> the install dvd that only that distro's own install routines, like Yast, would
> know, and a generic install routine, like virt-manager, from some other distro
> might not.)
Yes, I've actually taken both the initrd and the kernel from the Suse DVD:
boot/x86_64/vmlinuz-xen
boot/x86_64/initrd-xen

> That kernel & initrd started the install, and then I had to pick
> one of the Network install methods, after clicking on 'Back' to get to a menu.
> (Yes - it is a *pain* not having the mouse work. Fortunately, each option on
> each screen in Yast has an underlined letter. That letter, held down with the
> Alt key, selects that option.)
Yes, but not in the first screen! http://goo.gl/6EymS in wich I don't
know how to
press close!
:P

> I tried un-commenting the install= line above,
> and it did not save me any time. I still had to enter info into the Network
> install screens every time.
Not for me. I really don't understand why this happens to you. The
network configuration
is quite automatic for me.

Now, coming back again on how to start the installation process:
here's again the script I am using to launch the setup:

name="OpenSuse11"
memory=1024
disk = ['file:/mnt/xen/vmstore/opensuse11/opensuse11.img,xvda,w' ]
vif = [ 'type=ioemu, mac=00:16:3e:00:00:21, bridge=xenbr0' ]
vfb = [ "type=vnc,vncunused=1,vnclisten=0.0.0.0,keymap=it" ]
stdvga=1
videoram=16
kernel = "/mnt/xen/kernel/opensuse/vmlinuz-xen"
ramdisk = "/mnt/xen/kernel/opensuse/initrd-xen"
vcpus=1
on_reboot = 'restart'
on_crash = 'destroy'
extra = 'noapic ssh=1 sshpassword=lolrofl addswap=/dev/xvda2
install=http://192.168.1.100/suse11/'

Then: xl create opensuse11.cfg && xl vncviewer `xl domid OpenSuse11`
When the boot has finished: ssh -X root@<domU_IP> and then start yast.
No problem with the mouse pointer here.
Maybe we did all things differently? Or maybe there is a misunderstanding.
Maybe I am talking about the setup process, and you are talking about the domU
once it is up and running. Anyway, I think it should be clear now that the
mouse pointer doesn't work at the end, when it is running, not during
the setup process with yast.

> Anyway, two hours later, the vnc window disappeared. (This is about the point
> in the install where you started having problems.)
In truth, I didn't have this problem. My vncviewer window didn't
disappear. I simply closed it
because it is useless, since it is like this during the setup:
http://goo.gl/tfF9l
As you can see, once you do as the message suggests, the yast
installer starts in another
window: http://goo.gl/glvtK

Instead, it is the yast window that is going to disappear because it
has a countdown for the
reboot, and if you don't get it on time at the end of the setup, you
may think that the window has disappeared without any
reason, or because of a crash for instance.

> After the install finished, I changed the config file - un-comment the
> bootloader= line, and comment out the kernel= & ramdisk= lines. I then did an
> 'xm create ... -c' to be sure that grub was setup right, and then exited the
> domu's console, and did an 'xm vncviewer ...', and I am now staring at the KDE
> desktop.
Well, thanks to your tip above, I was able to go ahead with the setup
where I was
blocked. Now, I've noticed that I could start KDE as root but not as a
normal user.
Maybe it is due to a permission issue, or a missing group membership. I have to
investigate also on it.

> This is the menu.lst it installed. Notice it has kernel-desktop, and
> kernel-xen installed, with the kernel-xen as the default menu item, so the 'xm
> create' with the '-c' option was not necessary. I could have gone straight
> into a vncviewer. (I don't think menu.lst will be setup until you are past the
> Automatic Configuration step, so I didn't switch comments on bootloader and
> kernel / ramdisk till after then.)
This is pretty good. Actually I think it detects that it is a PV domU
and it installs
also the kernel-xen setting it as the default kernel. Good!

> Unfortunately, the desktop I'm looking at is 800x600, so we are back to one of
> the original problems. I'll try putting 'vga=0x31a' in menu.lst, or Fajar's
> suggestions about setting resolution in a pv domu, in the next day or two, and
> tell you what I come up with.
So, no higher resolution than 800x600 with some xorg.conf trick? Bad... Anyway,
the first problem to solve now is the mouse pointer. This has the highest
priority now.

On 7 December 2011 11:08, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> Well, this is fairly useless. The mouse doesn't work at all, so the desktop is
> unusable. I have to 'xm console ...' in to give commands. I turned on sshd,
> and changed the SuSEfirewall rules so I can use ssh as well.
I really don't understand why the mouse doesn't work. I'm really frustrated.

>
> The resolution is unchangeable. The hvm tricks that worked - vga=0x31a, or
> defining an xorg.conf don't work.
:-(

> And Fajar's xen-fbfront.video=32,1280,1024
> option in menu.lst didn't either. I wouldn't be surprised if suse renamed the
> module, though, like it renamed xennet and xenblk. However, since
> XEN_FRAMEBUFFER is builtin, I can't find the name of the module to modify it's
> options.
Maybe one solution is to recompile the kernel and put it as module.
We should try. The problem is that it is a very long process if we use
the config
file provided by the distro.
Pheraps we could try an "external" domU kernel, and not using pygrub
but something
like the following line in the configuration file:
kernel = "/mnt/xen/kernel/vmlinuz-xen-3.1.0-domU"
I use that kernel to start a gentoo pv domU and it works.

Thanks!
-- 
Flavio

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users