Bug 436256

Created attachment 246088 [details]
pm-suspend log

ERROR: no resume parameter on kernel commandline, can not suspend

It looks like either
- you have no swap partition, or
- YaST did, for some reason, not put the correct resume= parameter into the boot loader config.

And when you continue testing, don't forget to check
http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.1_dev#Suspend ;-)

(In reply to comment #2 from Stefan Seyfried)
> ERROR: no resume parameter on kernel commandline, can not suspend
> 
> It looks like either
> - you have no swap partition, or
> - YaST did, for some reason, not put the correct resume= parameter into the
> boot loader config.
> 

i have swap. it was created automatically during installation and i did not change any options for swap.

(In reply to comment #3 from Stefan Seyfried)
> And when you continue testing, don't forget to check
> http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.1_dev#Suspend ;-)
> 

i´m sorry to create probably duplicate. i did not look through most annyoings bugs (my fault).
if it would be fixed, i´ll wait on Beta3 and i´ll give you a feedback.

if you don´t need next info, i´m removing status needinfo.

(In reply to comment #4 from Rastislav Krupansky)
> (In reply to comment #2 from Stefan Seyfried)
> > ERROR: no resume parameter on kernel commandline, can not suspend
> > 
> > It looks like either
> > - you have no swap partition, or
> > - YaST did, for some reason, not put the correct resume= parameter into the
> > boot loader config.
> > 
> 
> i have swap. it was created automatically during installation and i did not
> change any options for swap.

Then it is a YaST bug, to not add a "resume=/your/swap/partition" argument to the boot command line.

You can now do that by yourself by editing /boot/grub/menu.lst and rebooting, but make sure to add

splash = n

to /etc/suspend.conf, otherwise it will still not suspend (because of the most annoying bug ;-)

Reassigning to YaST team.

Please, attach YaST2 logs.

Created attachment 246352 [details]
yast2 logs

logs were provided

From logs I see that resume argument is added, only possible problem can be that bootloader set it as  resume=/dev/disk/by-id/ata-VBOX_HARDDISK_VB323632bc-772f3278-part1 .

Does VirtualBox support resume? It fail when I test it even with kernel device in resume.

I assume you're trying hibernate in virtualbox to test hibernate in openSUSE. I agree it would be useful for testing.

I tried suspend to disk with OS11.1b3 (host) and OS11.1b3 (hosted). Leave -> Suspend to disk worked. After starting the machine again, it was resuming and at the end of resuming it crashed. The (end of the) vbox log says:

00:00:48.943 
00:00:48.943 !!Assertion Failed!!
00:00:48.943 Expression: <NULL>
00:00:48.943 Location  : /usr/src/packages/BUILD/VirtualBox-2.0.2/src/recompiler/VBoxRecompiler.c(4260) cpu_abort
00:00:48.943 fatal error in recompiler cpu: Trying to execute code with memory type addr_code=00000000f99ea020 addend=fffffffffed00000 at 00000000f99ea428. (iHandlerMemType=0x70 iMMIOMemType=0x60)
00:00:48.943 

looks like the final stage of restoration - execution of the data loaded into memory is a problem for virtualbox.

OK, so now I must find why log says that resume isn't attached even if my log says that it is. 
Can you please provide your bootloader configuration file (if you use grub then /boot/grub/menu.lst)?

Created attachment 249462 [details]
menu.lst

OK, I see that resume parameters to kernel is correctly set, so it must be problem in VirtualBox or kernel.

It is a problem in virtualbox, but I think this is a feature. Virtualbox tries to maintain some level of security by not allowing to execute arbitrary memory.
Fixing this bug is far beyond packages capabilities. I reported this bug upstream as an enhancement. 
http://www.virtualbox.org/ticket/2633