[Xen-bugs] [Bug 151] New: domU won't boot with CONFIG_XEN_PHYSDEV_ACCESS

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=151

           Summary: domU won't boot with CONFIG_XEN_PHYSDEV_ACCESS
           Product: Xen
           Version: 2.0
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: cuall@xxxxxx


i used the default domU config and enabled CONFIG_XEN_PHYSDEV_ACCESS , for 
serial  
ports network card and isdn. But the kernel won't boot, with this enabled 
option.   
   
Look here: 
http://lists.xensource.com/archives/html/xen-users/2005-08/msg00273.html   
  
i found several Users which have this problem. The only workaround is, to 
enable  
CONFIG_XEN_PRIVILEGED_GUEST, so the kernel boots. But the behave is very 
strange,  
cause, you don't see the boot messages and nothing starts. That means, you can 
login (via  
console, but not ssh), but you have to start every deamon. It seems, that init 
does not work.  
"init 2" does nothing.  
  
If i remove CONFIG_XEN_PHYSDEV_ACCESS and CONFIG_XEN_PRIVILEGED_GUEST, the  
system boots fine.  
  
Version xen-2.0.7 , Debian sarge (guest/host)

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs