http://bugzilla.novell.com/show_bug.cgi?id=620205
http://bugzilla.novell.com/show_bug.cgi?id=620205#c10
Carlos Costa e Silva changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|carlos@keysoft.pt |
--- Comment #10 from Carlos Costa e Silva 2010-07-20 02:07:25 WEST ---
Just for posterity, the parameter usage is "dom0_mem=512M".
Now, to answer the last message...
As 11.3 went final, downloaded and installed it new. Also recreated the windows
vm so that no cruft was left from the rc.
Both with and without the the dom0 memory/ballon restrictions, the vm still
starts the first time and fails to restart. All the logs and tests in this
message have been done with dom0_mem=512M and balloning off.
The symptoms and the error are now different[1]: after the second "xm start",
"xm list" shows the vm in the 'p' state for some time [with rc2 "xm list"
didn't show the vm as started]. After a while, "xm start" fails with the
message "Error: Device 0 (vif) could not be connected. Hotplug scripts not
working."
[1] Since installing 11.3 final, the error about not having enough memory to
(re)start the vm only happened once in well more than a dozen restart tests.
Now the logs:
config.sxp: the domU config file.
qemu-dm-rpspc.log.1: first domU start.
qemu-dm-rpspc.log: domU failed restart.
xend.log: from dom0 start to domU failed restart.
messages: excerpt from /var/log/messages from domU start to failed restart.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.