Hello,
i tried to install openSUSE 13.1 64b in VB 4.3.6
this crashes often with different messsages.
'Kernel tainted' and differenet reason, COM, CPU,...
Network is not working every time.
Host ist openSUSE 12.2 with grub 1.97 and systemd.
VB is 4.3.6 PUEL, GuestAdditions from Oracle
I tried to use the GuestAdditions from openSUSE, which are 4.2.18
per default. (virtualboxguest-kmp-default, virtualboxguest-tools, virtualboxguest-x11)
I tried to use the GuestAdditions from Oracle, which are 4.3.6
per default.
But is seems not to be getting better.
Which settings must i make to make it work?
Best regards.
GuestAdditions don't work with openSUSE 13.1
-
oelk0
- Posts: 9
- Joined: 19. Nov 2012, 00:33
- Primary OS: Other
- VBox Version: OSE other
- Guest OSses: opensuse
GuestAdditions don't work with openSUSE 13.1
Last edited by oelk0 on 18. Feb 2014, 21:46, edited 3 times in total.
-
oelk0
- Posts: 9
- Joined: 19. Nov 2012, 00:33
- Primary OS: Other
- VBox Version: OSE other
- Guest OSses: opensuse
Re: GuestAdditions don't work with openSUSE 13.1
My solution:
- only use Intel network cards in the VM, don't use AMD PCNet devices.
- select the following packages during installation process for the guest:
kernel-default-devel, kernel-syms, gcc, make, virtualboxguest-kmp-default,
virtualboxguest-tools, virtualboxguest-x11
(user manual, Page 67)
update the installation with:
and reboot.
remove the virtualbox-guest- packages and install the VirtualboxGuestAdditions.
The crashes are less.
Best regards
- only use Intel network cards in the VM, don't use AMD PCNet devices.
- select the following packages during installation process for the guest:
kernel-default-devel, kernel-syms, gcc, make, virtualboxguest-kmp-default,
virtualboxguest-tools, virtualboxguest-x11
(user manual, Page 67)
update the installation with:
Code: Select all
zypper up
remove the virtualbox-guest- packages and install the VirtualboxGuestAdditions.
The crashes are less.
Best regards
-
oelk0
- Posts: 9
- Joined: 19. Nov 2012, 00:33
- Primary OS: Other
- VBox Version: OSE other
- Guest OSses: opensuse
Re: GuestAdditions don't work with openSUSE 13.1
So, it is not solved:
if i define two NICs the crashes will happen. one is NAT, one is internal:
2014-02-18T20:36:21.843276+01:00 linux131 kernel: [ 44.072022] BUG: soft lockup - CPU#1 stuck for 23s! [systemd:1]
2014-02-18T20:36:21.843294+01:00 linux131 kernel: [ 44.072022] Modules linked in: af_packet vboxsf(O) sr_mod cdrom ata_generic ppdev joydev serio_raw parport_pc parport i2c_piix4 pcspkr ata_piix e1000 mperf ac vboxguest(O) button sg dm_mod autofs4 hid_generic usbhid ohci_pci ohci_hcd ehci_pci vboxvideo(O) ehci_hcd usbcore usb_common drm processor thermal_sys scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_dh_hp_sw scsi_dh
2014-02-18T20:36:21.843298+01:00 linux131 kernel: [ 44.072022] CPU: 1 PID: 1 Comm: systemd Tainted: G O 3.11.10-7-default #1
2014-02-18T20:36:21.843300+01:00 linux131 kernel: [ 44.072022] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
2014-02-18T20:36:21.843302+01:00 linux131 kernel: [ 44.072022] task: ffff880119e8e040 ti: ffff880119e90000 task.ti: ffff880119e90000
2014-02-18T20:36:21.843304+01:00 linux131 kernel: [ 44.072022] RIP: 0010:[<ffffffff8155d6cd>] [<ffffffff8155d6cd>] _raw_spin_lock+0x1d/0x30
2014-02-18T20:36:21.843306+01:00 linux131 kernel: [ 44.072022] RSP: 0018:ffff880119e91c78 EFLAGS: 00000202
2014-02-18T20:36:21.843309+01:00 linux131 kernel: [ 44.072022] RAX: 0000000000000005 RBX: ffff880119f74b48 RCX: 0000000000000004
2014-02-18T20:36:21.843311+01:00 linux131 kernel: [ 44.072022] RDX: 0000000000000004 RSI: ffffffff817fb2cd RDI: ffff880119558128
2014-02-18T20:36:21.843313+01:00 linux131 kernel: [ 44.072022] RBP: ffff880119b51c00 R08: 0000000000000014 R09: ffff880119b51c00
2014-02-18T20:36:21.843315+01:00 linux131 kernel: [ 44.072022] R10: 0000000000000004 R11: 0000000000000010 R12: 0000000000000000
2014-02-18T20:36:21.843317+01:00 linux131 kernel: [ 44.072022] R13: 0000000000000000 R14: ffff880119f74b40 R15: 0000000000000000
2014-02-18T20:36:21.843319+01:00 linux131 kernel: [ 44.072022] FS: 00007fd0a0d0e880(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
2014-02-18T20:36:21.843321+01:00 linux131 kernel: [ 44.072022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2014-02-18T20:36:21.843323+01:00 linux131 kernel: [ 44.072022] CR2: 00007fb8bd787fd8 CR3: 0000000118470000 CR4: 00000000000006e0
2014-02-18T20:36:21.843325+01:00 linux131 kernel: [ 44.072022] Stack:
2014-02-18T20:36:21.843327+01:00 linux131 kernel: [ 44.072022] ffffffff811c4186 ffff880119359ad0 ffff880119558128 0000000000008000
2014-02-18T20:36:21.843329+01:00 linux131 kernel: [ 44.072022] ffff880119e491a0 ffffffff00000000 0000000000000000 0000000000000000
2014-02-18T20:36:21.843331+01:00 linux131 kernel: [ 44.072022] 0000000000000000 ffff880119359ac0 ffff8801195580a0 ffff880118192300
2014-02-18T20:36:21.843333+01:00 linux131 kernel: [ 44.072022] Call Trace:
2014-02-18T20:36:21.843335+01:00 linux131 kernel: [ 44.072022] [<ffffffff811c4186>] __break_lease+0x46/0x360
2014-02-18T20:36:21.843337+01:00 linux131 kernel: [ 44.072022] [<ffffffff81179316>] do_dentry_open+0x126/0x270
2014-02-18T20:36:21.843339+01:00 linux131 kernel: [ 44.072022] [<ffffffff81187b93>] do_last+0x1c3/0xec0
2014-02-18T20:36:21.843368+01:00 linux131 kernel: [ 44.072022] [<ffffffff811898e6>] path_openat+0xb6/0x6a0
2014-02-18T20:36:21.843370+01:00 linux131 kernel: [ 44.072022] [<ffffffff8118ac55>] do_filp_open+0x35/0x80
2014-02-18T20:36:21.843372+01:00 linux131 kernel: [ 44.072022] [<ffffffff8117a759>] do_sys_open+0x129/0x210
2014-02-18T20:36:21.843374+01:00 linux131 kernel: [ 44.072022] [<ffffffff815652ed>] system_call_fastpath+0x1a/0x1f
2014-02-18T20:36:21.843376+01:00 linux131 kernel: [ 44.072022] [<00007fd09f13a770>] 0x7fd09f13a76f
2014-02-18T20:36:21.843378+01:00 linux131 kernel: [ 44.072022] Code: 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 b8 00 00 01 00 f0 0f c1 07 89 c1 c1 e9 10 66 39 c1 89 ca 74 0d 0f 1f 00 f3 90 0f b7 07 <66> 39 d0 75 f6 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 53 48
2014-02-18T20:36:29.581269+01:00 linux131 login: pam_systemd(login:session): Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2014-02-18T20:36:29.582371+01:00 linux131 systemd-logind[379]: Failed to start unit user-0.slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2014-02-18T20:36:29.583048+01:00 linux131 systemd-logind[379]: Failed to start user slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
The internal NIC does not have a partner to link with at this time.
This is also found in the logs:
2014-02-17T22:45:30.860546+01:00 linux131 systemd[1820]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
Any hints?
Best regards.
if i define two NICs the crashes will happen. one is NAT, one is internal:
2014-02-18T20:36:21.843276+01:00 linux131 kernel: [ 44.072022] BUG: soft lockup - CPU#1 stuck for 23s! [systemd:1]
2014-02-18T20:36:21.843294+01:00 linux131 kernel: [ 44.072022] Modules linked in: af_packet vboxsf(O) sr_mod cdrom ata_generic ppdev joydev serio_raw parport_pc parport i2c_piix4 pcspkr ata_piix e1000 mperf ac vboxguest(O) button sg dm_mod autofs4 hid_generic usbhid ohci_pci ohci_hcd ehci_pci vboxvideo(O) ehci_hcd usbcore usb_common drm processor thermal_sys scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_dh_hp_sw scsi_dh
2014-02-18T20:36:21.843298+01:00 linux131 kernel: [ 44.072022] CPU: 1 PID: 1 Comm: systemd Tainted: G O 3.11.10-7-default #1
2014-02-18T20:36:21.843300+01:00 linux131 kernel: [ 44.072022] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
2014-02-18T20:36:21.843302+01:00 linux131 kernel: [ 44.072022] task: ffff880119e8e040 ti: ffff880119e90000 task.ti: ffff880119e90000
2014-02-18T20:36:21.843304+01:00 linux131 kernel: [ 44.072022] RIP: 0010:[<ffffffff8155d6cd>] [<ffffffff8155d6cd>] _raw_spin_lock+0x1d/0x30
2014-02-18T20:36:21.843306+01:00 linux131 kernel: [ 44.072022] RSP: 0018:ffff880119e91c78 EFLAGS: 00000202
2014-02-18T20:36:21.843309+01:00 linux131 kernel: [ 44.072022] RAX: 0000000000000005 RBX: ffff880119f74b48 RCX: 0000000000000004
2014-02-18T20:36:21.843311+01:00 linux131 kernel: [ 44.072022] RDX: 0000000000000004 RSI: ffffffff817fb2cd RDI: ffff880119558128
2014-02-18T20:36:21.843313+01:00 linux131 kernel: [ 44.072022] RBP: ffff880119b51c00 R08: 0000000000000014 R09: ffff880119b51c00
2014-02-18T20:36:21.843315+01:00 linux131 kernel: [ 44.072022] R10: 0000000000000004 R11: 0000000000000010 R12: 0000000000000000
2014-02-18T20:36:21.843317+01:00 linux131 kernel: [ 44.072022] R13: 0000000000000000 R14: ffff880119f74b40 R15: 0000000000000000
2014-02-18T20:36:21.843319+01:00 linux131 kernel: [ 44.072022] FS: 00007fd0a0d0e880(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
2014-02-18T20:36:21.843321+01:00 linux131 kernel: [ 44.072022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2014-02-18T20:36:21.843323+01:00 linux131 kernel: [ 44.072022] CR2: 00007fb8bd787fd8 CR3: 0000000118470000 CR4: 00000000000006e0
2014-02-18T20:36:21.843325+01:00 linux131 kernel: [ 44.072022] Stack:
2014-02-18T20:36:21.843327+01:00 linux131 kernel: [ 44.072022] ffffffff811c4186 ffff880119359ad0 ffff880119558128 0000000000008000
2014-02-18T20:36:21.843329+01:00 linux131 kernel: [ 44.072022] ffff880119e491a0 ffffffff00000000 0000000000000000 0000000000000000
2014-02-18T20:36:21.843331+01:00 linux131 kernel: [ 44.072022] 0000000000000000 ffff880119359ac0 ffff8801195580a0 ffff880118192300
2014-02-18T20:36:21.843333+01:00 linux131 kernel: [ 44.072022] Call Trace:
2014-02-18T20:36:21.843335+01:00 linux131 kernel: [ 44.072022] [<ffffffff811c4186>] __break_lease+0x46/0x360
2014-02-18T20:36:21.843337+01:00 linux131 kernel: [ 44.072022] [<ffffffff81179316>] do_dentry_open+0x126/0x270
2014-02-18T20:36:21.843339+01:00 linux131 kernel: [ 44.072022] [<ffffffff81187b93>] do_last+0x1c3/0xec0
2014-02-18T20:36:21.843368+01:00 linux131 kernel: [ 44.072022] [<ffffffff811898e6>] path_openat+0xb6/0x6a0
2014-02-18T20:36:21.843370+01:00 linux131 kernel: [ 44.072022] [<ffffffff8118ac55>] do_filp_open+0x35/0x80
2014-02-18T20:36:21.843372+01:00 linux131 kernel: [ 44.072022] [<ffffffff8117a759>] do_sys_open+0x129/0x210
2014-02-18T20:36:21.843374+01:00 linux131 kernel: [ 44.072022] [<ffffffff815652ed>] system_call_fastpath+0x1a/0x1f
2014-02-18T20:36:21.843376+01:00 linux131 kernel: [ 44.072022] [<00007fd09f13a770>] 0x7fd09f13a76f
2014-02-18T20:36:21.843378+01:00 linux131 kernel: [ 44.072022] Code: 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 b8 00 00 01 00 f0 0f c1 07 89 c1 c1 e9 10 66 39 c1 89 ca 74 0d 0f 1f 00 f3 90 0f b7 07 <66> 39 d0 75 f6 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 53 48
2014-02-18T20:36:29.581269+01:00 linux131 login: pam_systemd(login:session): Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2014-02-18T20:36:29.582371+01:00 linux131 systemd-logind[379]: Failed to start unit user-0.slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2014-02-18T20:36:29.583048+01:00 linux131 systemd-logind[379]: Failed to start user slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
The internal NIC does not have a partner to link with at this time.
This is also found in the logs:
2014-02-17T22:45:30.860546+01:00 linux131 systemd[1820]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
Any hints?
Best regards.
-
oelk0
- Posts: 9
- Joined: 19. Nov 2012, 00:33
- Primary OS: Other
- VBox Version: OSE other
- Guest OSses: opensuse
Re: GuestAdditions don't work with openSUSE 13.1
Hello,
i did another test:
Host is CentOS 6.4 with VB 4.3.6, guest is openSUSE 13.1
I had the same errors.
If define only one CPU as kernel-parameter in the guest (maxcpus=0),
then the Installation is stable.
It seems that somethings wrong with IO-APIC?
Best regards.
i did another test:
Host is CentOS 6.4 with VB 4.3.6, guest is openSUSE 13.1
I had the same errors.
If define only one CPU as kernel-parameter in the guest (maxcpus=0),
then the Installation is stable.
It seems that somethings wrong with IO-APIC?
Best regards.
-
oelk0
- Posts: 9
- Joined: 19. Nov 2012, 00:33
- Primary OS: Other
- VBox Version: OSE other
- Guest OSses: opensuse
no 64bit linux guest is running with VB 4.3.8
Was: GuestAdditions don't work with openSUSE 13.1
No 64bit linux guest is running, if the init-system is systemd
respectively the kernel of the guest is 3.7 or newer.
Host is openSUSE 12.2 with systemd-44, but i tried also CentOS 6.4
VB is 4.3.8, GuestAdditions 4.3.8
Any solutions?
Best regards
No 64bit linux guest is running, if the init-system is systemd
respectively the kernel of the guest is 3.7 or newer.
Host is openSUSE 12.2 with systemd-44, but i tried also CentOS 6.4
VB is 4.3.8, GuestAdditions 4.3.8
Any solutions?
Best regards
- Attachments
-
VBox.txt- openSUSE 13.1 64b, 4GB RAM, kernel 3.11, systemd
- (96.22 KiB) Downloaded 12 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: GuestAdditions don't work with openSUSE 13.1
Don't hijack your own thread. If this is a different issue, open a different thread. It's going to be easier for people that are searching for solutions in the internet...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.