One more update. After working for a bit with 'cpu_type' unset, the
problem of hanging during boot recurred. However, setting
'cpu_type=host' seems to have provided a more permanent solution.
--jason
Jason Lawrence <mailto:[email protected]>
February 2, 2016 at 6:31 PM
I don't believe mine was memory related as there is plenty to spare.
Setting 'cpu_type=core2duo' allowed installation to proceed and the VM
runs fine after installation with the cpu_type override removed.
--jason
On Feb 2, 2016, at 5:13 PM, Eric <[email protected]
<mailto:[email protected]>> wrote:
*smartos-discuss* | Archives
<https://www.listbox.com/member/archive/184463/=now>
<https://www.listbox.com/member/archive/rss/184463/24824159-36a67e62>
| Modify
<https://www.listbox.com/member/?&;>
Your Subscription [Powered by Listbox] <http://www.listbox.com>
Eric <mailto:[email protected]>
February 2, 2016 at 5:13 PM
On Mon, Feb 1, 2016 at 5:46 PM Jason Lawrence <[email protected]
<mailto:[email protected]>> wrote:
I found a suggestion in
https://github.com/joyent/smartos-live/issues/456#issuecomment-112663295
to change the cpu_type, and the install continued after I
specified 'core2duo' (but not 'Nehalem').
Anyone have any experience with this approach?
Hey Jason. OP here. If you keep going after that comment you'll get a
post that solved it for me:
https://github.com/joyent/smartos-live/issues/456#issuecomment-113349256
Essentially, by default there's an additional amount of RAM that's
allocated from the amount given to the VM, which caused it to
immediately stop soon after starting.
*smartos-discuss* | Archives
<https://www.listbox.com/member/archive/184463/=now>
<https://www.listbox.com/member/archive/rss/184463/24824159-36a67e62>
| Modify
<https://www.listbox.com/member/?&;>
Your Subscription [Powered by Listbox] <http://www.listbox.com>
Jason Lawrence <mailto:[email protected]>
February 1, 2016 at 4:45 PM
I found a suggestion in
https://github.com/joyent/smartos-live/issues/456#issuecomment-112663295
to change the cpu_type, and the install continued after I specified
'core2duo' (but not 'Nehalem').
Anyone have any experience with this approach?
--jason
*smartos-discuss* | Archives
<https://www.listbox.com/member/archive/184463/=now>
<https://www.listbox.com/member/archive/rss/184463/24824159-36a67e62>
| Modify
<https://www.listbox.com/member/?&;>
Your Subscription [Powered by Listbox] <http://www.listbox.com>
Jason Lawrence <mailto:[email protected]>
February 1, 2016 at 1:10 PM
Watching it for several minutes, the only counters which have any
activity are equal counts of 'exits' and 'irqx' on the first of two vcpus:
pid vcpu | exits : haltx irqx irqwx iox mmiox | irqs
emul eptv
43656 0 | 263 : 0 263 0 0 0 |
0 0 0
43656 1 | 0 : 0 0 0 0 0 |
0 0 0
Average is ~250 every 10 seconds. Second vcpu never shows any
activity. This meaningful in any way?
--jason
*smartos-discuss* | Archives
<https://www.listbox.com/member/archive/184463/=now>
<https://www.listbox.com/member/archive/rss/184463/24824159-36a67e62>
| Modify
<https://www.listbox.com/member/?&;>
Your Subscription [Powered by Listbox] <http://www.listbox.com>
Robert Mustacchi <mailto:[email protected]>
February 1, 2016 at 12:09 AM
The first thing that I'd look at is the kvmstat output and see if the
guest is running and trying to do things or not.
Robert
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
