VirtualBox

Ticket #6436 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

3.1.6 on Solaris x64 5/08: System unstable upon install of package

Reported by: gbulfon Owned by:
Priority: major Component: installer
Version: VirtualBox 3.1.6 Keywords:
Cc: Guest type: Windows
Host type: Solaris

Description

Hello, Today I was going to a customer needing me to install an old win98 into a VM to run an old software. No better time to test this new 3.1.6 build of VBox! Got my hands on the HP Server running Solaris 10 5/08 x64, downloaded and pkgadded VBox 3.1.6...and...

  • noticed the install last phase (loading drivers and so on) was a little bit slow...then, while updating the boot archive, it was never returning to bash
  • I opened a new ssh session to the host...nor prstat nor top were responding...as if kernel was hang....
  • Pressed ctrl+c on the pkgadd "updating boot archive"...after some more ctrl+c it gave me back the bash prompt
  • now top and prstat was responding, back to normal

So, package was installed anyway, and I tried to use it:

  • created vm and all its necessary flags (tried both with virtex and no virtex), no apic, no pae, no paging, 1 ide disk, bridged network, 256Mb ram, 5Gb HD-VDI fixed.
  • ran win98 install from cd iso
  • after first installation reboot, the vm killed itself on "hardware plug&play discovery" of win98
  • restarted the VM, and install continued
  • now, again at "hardware plug&play discovery", complete host system hang (system console would not go to the text console login)
  • had to manually poweroff / poweron
  • so I restarted the VM
  • this time, it went on preparing last win98 stuff, and at once I got a complete host system reset...

I believe it's something about the Solaris host, probably won't have problems on a recent OpenSolaris. Maybe Solaris is going to be unsupported?

Attachments

VBox.log Download (33.7 KB) - added by gbulfon 4 years ago.
VBox.log.1 Download (57.6 KB) - added by gbulfon 4 years ago.
VBox.log.2 Download (52.4 KB) - added by gbulfon 4 years ago.
VBox.log.3 Download (38.0 KB) - added by gbulfon 4 years ago.

Change History

comment:1 Changed 4 years ago by ramshankar

Some essential information is missing in your report.

Could you please attach:

  1. VBox.log for the relevant VMs.
  2. Paste/attach output of "cat /var/adm/messages | grep -i vbox" from the host.
  3. Does this happen with 3.1.4?

If kernel was hanging/deadlocking in some lock when you updated the boot-archive that suggests there might be problems even before VirtualBox was installed.

Changed 4 years ago by gbulfon

Changed 4 years ago by gbulfon

Changed 4 years ago by gbulfon

Changed 4 years ago by gbulfon

comment:2 Changed 4 years ago by gbulfon

Hi, I attached all the VBox.log files found. I could not see anything interesting in messages, grepping vbox, only stuff like this:

Mar 26 11:39:44 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxdrv0
Mar 26 11:39:44 iserver genunix: [ID 936769 kern.info] vboxdrv0 is /pseudo/vboxdrv@0
Mar 26 11:41:00 iserver gld: [ID 944156 kern.info] vboxnet0: vboxnet: type "ether" mac address 08:00:27:4e:17:5a
Mar 26 11:41:00 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
Mar 26 11:41:00 iserver genunix: [ID 936769 kern.info] vboxnet0 is /pseudo/vboxnet@0
Mar 26 11:41:00 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
Mar 26 11:41:00 iserver genunix: [ID 936769 kern.info] vboxnet0 is /pseudo/vboxnet@0
Mar 26 11:41:38 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxflt0
Mar 26 11:41:38 iserver genunix: [ID 936769 kern.info] vboxflt0 is /pseudo/vboxflt@0
Mar 26 16:21:37 iserver gld: [ID 944156 kern.info] vboxnet0: vboxnet: type "ether" mac address 08:00:27:ee:b7:9c
Mar 26 16:21:37 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
Mar 26 16:21:37 iserver genunix: [ID 936769 kern.info] vboxnet0 is /pseudo/vboxnet@0
Mar 26 16:21:37 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
Mar 26 16:21:37 iserver genunix: [ID 936769 kern.info] vboxnet0 is /pseudo/vboxnet@0
Mar 26 16:21:40 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxdrv0
Mar 26 16:21:40 iserver genunix: [ID 936769 kern.info] vboxdrv0 is /pseudo/vboxdrv@0
Mar 26 16:21:40 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxflt0
Mar 26 16:21:40 iserver genunix: [ID 936769 kern.info] vboxflt0 is /pseudo/vboxflt@0
Mar 26 16:44:56 iserver gld: [ID 944156 kern.info] vboxnet0: vboxnet: type "ether" mac address 08:00:27:ab:4c:48
Mar 26 16:44:56 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
Mar 26 16:44:56 iserver genunix: [ID 936769 kern.info] vboxnet0 is /pseudo/vboxnet@0
Mar 26 16:44:56 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
Mar 26 16:44:56 iserver genunix: [ID 936769 kern.info] vboxnet0 is /pseudo/vboxnet@0
Mar 26 16:45:00 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxdrv0
Mar 26 16:45:00 iserver genunix: [ID 936769 kern.info] vboxdrv0 is /pseudo/vboxdrv@0
Mar 26 16:45:00 iserver pseudo: [ID 129642 kern.info] pseudo-device: vboxflt0
Mar 26 16:45:00 iserver genunix: [ID 936769 kern.info] vboxflt0 is /pseudo/vboxflt@0
bash-3.00# 

Instead, I have some log of the two crashing situations. Here is when the machine freezed (a very strange message I cannot understand...):

Mar 26 13:09:59 iserver named[26519]: [ID 873579 daemon.warning] em10072008.ZIP\221\272\251\277^C^T\376^L13072008.ZIP\221\275\251\277^C^T\376^L14072008.ZIP\221\276\251\277^C^T\37
6^L15072008.ZIP\221\277\251\277^C^T\376^L16072008.ZIP\221\300\251\277^C^T\376^L17072008.ZIP\221\301\251\277^C^T\376^L20072008.ZIP\222\272\251\277^C^T\376^L21072008.ZIP\222\273\25
1\277^C^T\376^L22072008.ZIP\222\274\251\277^C^T\376^L23072008.ZIP\222\275\251\277^C^T\376^L24072008.ZIP\222\276\251\277^C^T\376^L27072008.ZIP\222\301\251\277^C^T\376^L28072008.ZI
P\222\302\251\277^C^T\376^L29072008.ZIP\222\303\251\277^C^T\376^L30072008.ZIP\223\272\251\277^C^T\376^L31072008.ZIP\223\273\251\277^C^T\376^L03082008.ZIP\220\275\251\300^C^T\376^
L04082008.ZIP\220\276\251\300^C^T\376^L05082008.ZIP\220\277\251\300^C^T\376^L06082008.ZIP\220\300\251\300^C^T\376^L24082008.ZIP\222\276\251\300^C^T\376^L25082008.ZIP\222\277\251\
300^C^T\376^L26082008.ZIP\222\300\251\300^C^T\376^L27082008.ZIP\222\301\251\300^C^T\376^L28082008.ZIP\222\302\251\300^C^T\376^L31082008.ZIP\223\273\251\300^C^T\376^L01092008.ZIP\
220\273\251\301^C^T\376^L02092008.ZIP\220\274\251\301^C^T\376^L03092008.ZIP\220\275\251\301^C^T\376^L04092008.ZIP\220\276\251\301^C^T\376^L07092008.ZIP\220\301\251\301^C^T\376^L0
8092008.ZIP\220\302\251\301^C^T\376^L09092008.ZIP\220\303\251\301^C^T\376^L10092008.ZIP\221\272\251\301^C^T\376^L11092008.ZIP\221\273\251\301^C^T\376^L14092008.ZIP\221\276\251\30
1^C^T\376^L15092008.ZIP\221\277\251\301^C^T\376^L16092008.ZIP\221\300\251\301^C^T\376^L17092008.ZIP\221\301\251\301^C^T\376^L18092008.ZIP\221\302\251\301^C^T\376^L21092008.ZIP\22
2\273\251\301^C^T\376^L22092008.ZIP\222\274\251\301^C^T\376^L23092008.ZIP\222\275\251\301^C^T\376^L24092008.ZIP\222\276\251\301^C^T\376^L25092008.ZIP\222\277\251\301^C^T\376^L280
92008.ZIP\222\302\251\301^C^T\376^L29092008.ZIP\222\303\251\301^C^T\376^L30092008.ZIP\223\272\251\301^C^T\376^L01102008.ZIP\220\273\252\270^C^T\376^L02102008.ZIP\220\274\252\270^
C^T\376^L05102008.ZIP\220\277\252\270^C^T\376^L06102008.ZIP\220\300\252\270^C^T\376^L0Mar 26 16:21:18 iserver genunix: [ID 540533 kern.notice]

Then I had to power off and on manually.

Here is the messages I found of the kernel panic (apparently something went wrong with ipfilter):

Mar 26 16:42:15 iserver genunix: [ID 683410 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=fffffe80000cb9e0 addr=ffffffffc4d52d4f
Mar 26 16:42:15 iserver unix: [ID 100000 kern.notice]
Mar 26 16:42:15 iserver unix: [ID 839527 kern.notice] sched:
Mar 26 16:42:15 iserver unix: [ID 753105 kern.notice] #pf Page fault
Mar 26 16:42:15 iserver unix: [ID 532287 kern.notice] Bad kernel fault at addr=0xffffffffc4d52d4f
Mar 26 16:42:15 iserver unix: [ID 243837 kern.notice] pid=0, pc=0xfffffffffb82e4aa, sp=0xfffffe80000cbad8, eflags=0x10206
Mar 26 16:42:15 iserver unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6f8<xmme,fxsr,pge,mce,pae,pse,de>
Mar 26 16:42:15 iserver unix: [ID 354241 kern.notice] cr2: ffffffffc4d52d4f cr3: c52a000 cr8: c
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   rdi: ffffffffc0710200 rsi: ffffffffc4d52d4f rdx: fffffffffb9bd651
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   rcx: 1fffffffff737aca  r8: fffffe80000cba80  r9:                1
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   rax: ffffffffc07101b8 rbx: ffffffff86a036a8 rbp: fffffe80000cbb10
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   r10: ffffffff801c3740 r11: fffffffffbce1d60 r12: bfffffffffe6a408
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   r13:            1eac0 r14: ffffffff80247000 r15:            1eac0
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   fsb: fffffd7ffef67200 gsb: ffffffff8188a800  ds:               43
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]    es:               43  fs:              1bb  gs:                0
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]   trp:                e err:                0 rip: fffffffffb82e4aa
Mar 26 16:42:15 iserver unix: [ID 592667 kern.notice]    cs:               28 rfl:            10206 rsp: fffffe80000cbad8
Mar 26 16:42:15 iserver unix: [ID 266532 kern.notice]    ss:               30
Mar 26 16:42:15 iserver unix: [ID 100000 kern.notice]
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cb8f0 unix:real_mode_end+71e1 ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cb9d0 unix:trap+5e6 ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cb9e0 unix:cmntrap+140 ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbb10 unix:bcopy+a ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbb40 ipf:nat_delete+3f ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbb80 ipf:fr_natexpire+79 ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbba0 ipf:fr_slowtimer+8f ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbbe0 genunix:callout_execute+d6 ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbc60 genunix:taskq_thread+bc ()
Mar 26 16:42:15 iserver genunix: [ID 655072 kern.notice] fffffe80000cbc70 unix:thread_start+8 ()
Mar 26 16:42:15 iserver unix: [ID 100000 kern.notice]
Mar 26 16:42:15 iserver genunix: [ID 672855 kern.notice] syncing file systems...
Mar 26 16:42:15 iserver genunix: [ID 733762 kern.notice]  20
Mar 26 16:42:16 iserver genunix: [ID 733762 kern.notice]  14
Mar 26 16:42:17 iserver genunix: [ID 733762 kern.notice]  13
Mar 26 16:42:37 iserver last message repeated 20 times
Mar 26 16:42:38 iserver genunix: [ID 622722 kern.notice]  done (not all i/o completed)
Mar 26 16:42:39 iserver genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c1t0d0s1, offset 110231552, content: kernel
Mar 26 16:42:54 iserver genunix: [ID 409368 kern.notice] ^M100% done: 66696 pages dumped, compression ratio 3.30,
Mar 26 16:42:54 iserver genunix: [ID 851671 kern.notice] dump succeeded

And then normal boot messages.

Please keep in mind this system never had problems before I pkgadded VBox. It was running for a couple of years with no panic at all. It's just one of the many systems we installed with a clean Solaris 5/08 and just added our own software bundle (nothing to interfere with kernel). I have VBox 3.1.4 running on other 3 systems, and had no problems during install.

Now, for safety (becasue it's a production system) I had to remove all the vbox package from that system, and I could not try it with 3.1.4.

Just ask for any other info ;) Gabriele.

comment:3 Changed 4 years ago by ramshankar

Sorry for getting back to this late, I've not been able to reproduce this error or heard anyone else with such problems with upgrading to VBox 3.1.6. When you exited the "updating boot-archive" stage of the installer, how long did you wait? Sometimes this may take upto a minute and generally aborting this is a bad idea. Also the crash you reported doesn't seem to be VirtualBox's dirty work. Or could be VirtualBox managed to trigger a memory access pattern or alter the networking setup to produce an already faulty installation/hardware issue. Too many parameters here.

Did you encounter this on any other system? If not perhaps we can close this ticket as unrelated to VirtualBox.

comment:4 Changed 4 years ago by gbulfon

Hi :) No I had no chance to update any other machine. What I can tell you is that I waited 5-10 minutes before deciding to break, after watching system activities almost 0%. I will install this new package on some machine soon, so I will tell you if I encounter any problems (but this time it will be OpenSolaris, so maybe it's totally different). Thanks again, Gabriele.

comment:5 Changed 4 years ago by ramshankar

  • Status changed from new to closed
  • Resolution set to invalid

Closing this, please feel free to reopen if required. Thank you for the report.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use