[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Timed out waiting for device dev-hvc0.device.




On 12.12.14 01:25, manish jaggi wrote:
> On 11 December 2014 at 02:23, Julien Grall <julien.grall@xxxxxxxxxx> wrote:
>> Hello,
>>
>>
>> On 11/12/2014 02:27, manish jaggi wrote:
>>>
>>> I am facing this issue when booting Xen Dom0 (OpenSuse Rootfs)
>>>
>>> ...
>>>
>>> [  OK  ] Reached target Host and Network Name Lookups.
>>> [  OK  ] Started OpenSSH Daemon.
>>> [ TIME ] Timed out waiting for device dev-hvc0.device.
>>> [DEPEND] Dependency failed for Serial Getty on hvc0.
>>> [  OK  ] Reached target Login Prompts.
>>>
>>>
>>> Any Idea? what could be wrong here
>>
>>
>> Please provide the full boot log. With only those 5 lines we can only guess
>> what could be the issue.
>>
> Added
>> Maybe the DOM0 kernel didn't detect that it's running on Xen or you forgot
>> to enable CONFIG_XEN_HVC in your config.
> That is already enabled.
> FYI with other rootfs I dont see any problem.
>>
>> Regards,
>>
>> --
>> Julien Grall
> 
> [... Std linux boot log .. ]
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs (sda2): using internal journal
> EXT3-fs (sda2): mounted filesystem with writeback data mode
> VFS: Mounted root (ext3 filesystem) on device 8:2.
> devtmpfs: mounted
> Freeing unused kernel memory: 236K (ffffffc000789000 - ffffffc0007c4000)
> random: systemd urandom read with 4 bits of entropy available
> systemd[1]: systemd 210 running in system mode. (+PAM -LIBWRAP +AUDIT
> +SELINUX -IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP
> +APPARMOR)
> systemd[1]: Detected virtualization 'xen'.
> systemd[1]: Detected architecture 'arm64'.
> 
> Welcome to openSUSE 13.2 (Harlequin) (aarch64)!
> 
> systemd[1]: Failed to insert module 'autofs4'
> systemd[1]: Failed to insert module 'ipv6'
> systemd[1]: Set hostname to <linux>.
> systemd[1]: Cannot add dependency job for unit
> display-manager.service, ignoring: Unit display-manager.service failed
> to load: No such file or directory.
> systemd[1]: Expecting device dev-hvc0.device...
>          Expecting device dev-hvc0.device...
> systemd[1]: Starting Remote File Systems (Pre).
> [  OK  ] Reached target Remote File Systems (Pre).
> systemd[1]: Reached target Remote File Systems (Pre).
> systemd[1]: Starting Remote File Systems.
> [  OK  ] Reached target Remote File Systems.
> systemd[1]: Reached target Remote File Systems.
> systemd[1]: Set up automount Arbitrary Executable File Formats File
> System Automount Point.
> systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
> systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
> systemd[1]: Starting Paths.
> [  OK  ] Reached target Paths.
> systemd[1]: Reached target Paths.
> systemd[1]: Starting Swap.
> [  OK  ] Reached target Swap.
> systemd[1]: Reached target Swap.
> systemd[1]: Starting Root Slice.
> [  OK  ] Created slice Root Slice.
> systemd[1]: Created slice Root Slice.
> systemd[1]: Starting udev Kernel Socket.
> [  OK  ] Listening on udev Kernel Socket.
> systemd[1]: Listening on udev Kernel Socket.
> systemd[1]: Starting Journal Socket.
> [  OK  ] Listening on Journal Socket.
> systemd[1]: Listening on Journal Socket.
> systemd[1]: Starting LVM2 metadata daemon socket.
> [  OK  ] Listening on LVM2 metadata daemon socket.
> systemd[1]: Listening on LVM2 metadata daemon socket.
> systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
> [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
> systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
> systemd[1]: Starting Delayed Shutdown Socket.
> [  OK  ] Listening on Delayed Shutdown Socket.
> systemd[1]: Listening on Delayed Shutdown Socket.
> systemd[1]: Starting Syslog Socket.
> [  OK  ] Listening on Syslog Socket.
> systemd[1]: Listening on Syslog Socket.
> systemd[1]: Starting User and Session Slice.
> [  OK  ] Created slice User and Session Slice.
> systemd[1]: Created slice User and Session Slice.
> systemd[1]: Starting System Slice.
> [  OK  ] Created slice System Slice.
> systemd[1]: Created slice System Slice.
> systemd[1]: Started Create list of required static device nodes for
> the current kernel.
> systemd[1]: Starting Create static device nodes in /dev...
>          Starting Create static device nodes in /dev...
> systemd[1]: Mounting POSIX Message Queue File System...
>          Mounting POSIX Message Queue File System...
> systemd[1]: Mounting Debug File System...
>          Mounting Debug File System...
> systemd[1]: Mounting Huge Pages File System...
>          Mounting Huge Pages File System...
> systemd[1]: Starting Journal Service...
>          Starting Journal Service...
> [  OK  ] Started Journal Service.
> systemd[1]: Started Journal Service.
> [  OK  ] Created slice system-serial\x2dgetty.slice.
> [  OK  ] Created slice system-getty.slice.
>          Starting LVM2 metadata daemon...
>          Starting Load Kernel Modules...
>          Starting Setup Virtual Console...
>          Starting Remount Root and Kernel File Systems...
>          Starting Create dynamic rule for /dev/root link...
> [  OK  ] Reached target Slices.
> [  OK  ] Listening on udev Control Socket.
> [  OK  ] Mounted Huge Pages File System.
> [  OK  ] Mounted Debug File System.
> [  OK  ] Mounted POSIX Message Queue File System.
> [  OK  ] Started Create static device nodes in /dev.
> [  OK  ] Started LVM2 metadata daemon.
> [FAILED] Failed to start Load Kernel Modules.
> See "systemctl status systemd-modules-load.service" for details.
> [  OK  ] Started Setup Virtual Console.
> [  OK  ] Started Remount Root and Kernel File Systems.
> [  OK  ] Started Create dynamic rule for /dev/root link.
>          Starting Load/Save Random Seed...
>          Starting udev Coldplug all Devices...
>          Starting Apply Kernel Variables...
>          Mounting FUSE Control File System...
>          Starting udev Kernel Device Manager...
> [  OK  ] Reached target Local File Systems (Pre).
>          Mounting Runtime Directory...
> [  OK  ] Mounted FUSE Control File System.
> [  OK  ] Mounted Runtime Directory.
> [  OK  ] Started udev Kernel Device Manager.
> [  OK  ] Started Load/Save Random Seed.
> [  OK  ] Started Apply Kernel Variables.
> [  OK  ] Started udev Coldplug all Devices.
> thunder-nicvf 0002:01:00.3 enP2p1s0f3: renamed from eth2
>          Starting udev Wait for Complete Device Initialization...
> thunder-nicvf 0002:01:00.1 enP2p1s0f1: renamed from eth0
> thunder-nicvf 0002:01:00.2 enP2p1s0f2: renamed from eth1
> thunder-nicvf 0002:01:00.4 enP2p1s0f4: renamed from eth3
> [  OK  ] Started udev Wait for Complete Device Initialization.
>          Starting Activation of LVM2 logical volumes...
> [  OK  ] Started Activation of LVM2 logical volumes.
> [  OK  ] Reached target Encrypted Volumes.
>          Starting Activation of LVM2 logical volumes...
> [  OK  ] Started Activation of LVM2 logical volumes.
> [  OK  ] Reached target Local File Systems.
>          Starting Trigger Flushing of Journal to Persistent Storage...
>          Starting Create Volatile Files and Directories...
> systemd-journald[884]: Received request to flush runtime journal from PID 1
> [  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
> [  OK  ] Started Create Volatile Files and Directories.
>          Starting Update UTMP about System Reboot/Shutdown...
> [  OK  ] Started Update UTMP about System Reboot/Shutdown.
> [  OK  ] Reached target System Initialization.
> [  OK  ] Listening on D-Bus System Message Bus Socket.
> [  OK  ] Reached target Sockets.
> [  OK  ] Reached target Timers.
>          Starting Restore Sound Card State...
> [  OK  ] Reached target Basic System.
>          Starting Permit User Sessions...
>          Starting /etc/init.d/boot.local Compatibility...
>          Starting System Logging Service...
>          Starting Purge old kernels...
>          Starting Login Service...
>          Starting D-Bus System Message Bus...
> [  OK  ] Started D-Bus System Message Bus.
>          Starting wicked DHCPv4 supplicant service...
>          Starting wicked AutoIPv4 supplicant service...
>          Starting wicked DHCPv6 supplicant service...
> [  OK  ] Started Restore Sound Card State.
> [  OK  ] Started Permit User Sessions.
> [  OK  ] Started /etc/init.d/boot.local Compatibility.
> [  OK  ] Started wicked AutoIPv4 supplicant service.
> [  OK  ] Started wicked DHCPv6 supplicant service.
> [  OK  ] Started wicked DHCPv4 supplicant service.
> [  OK  ] Started Login Service.
>          Starting wicked network management service daemon...
>          Starting Getty on tty1...
> [  OK  ] Started Getty on tty1.
> [  OK  ] Started System Logging Service.
> [  OK  ] Started wicked network management service daemon.
>          Starting wicked network nanny service...
> [  OK  ] Started wicked network nanny service.
>          Starting wicked managed network interfaces...
> [  OK  ] Started Purge old kernels.
> [  OK  ] Started wicked managed network interfaces.
> [  OK  ] Reached target Network.
>          Starting OpenSSH Daemon...
>          Starting NTP Server Daemon...
> [  OK  ] Started NTP Server Daemon.
> [  OK  ] Started OpenSSH Daemon.
> [ TIME ] Timed out waiting for device dev-hvc0.device.
> [DEPEND] Dependency failed for Serial Getty on hvc0.
> [  OK  ] Reached target Login Prompts.
>          Starting /etc/init.d/after.local Compatibility...
> [  OK  ] Started /etc/init.d/after.local Compatibility.
> [  OK  ] Reached target Multi-User System.
> [  OK  ] Reached target Graphical Interface.
> 
> 
> Alex,any idea how to look for what is causing timeout ?
> Grep -rn hcv0 in suse file system resulted nil.
> I am using https://wiki.linaro.org/LEG/Engineering/Xen_booting_on_Foundationv8

Hrm, does your kernel have devtmpfs support enabled? Apparently SSH did
come up, can you try to log in via ssh and see whether you can see an
hvc0 device node in /dev?


Alex

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.