Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-bugs

[Xen-bugs] [Bug 544] New: domU won't boot when vcpus=1 with domu scsi co

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 544] New: domU won't boot when vcpus=1 with domu scsi compiled-in kernel
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 23 Feb 2006 19:47:03 +0000
Delivery-date: Thu, 23 Feb 2006 23:38:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=544

           Summary: domU won't boot when vcpus=1 with domu scsi compiled-in
                    kernel
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: wenshengwang@xxxxxxxxx


After I changed scsi snd sd from module to compiled-in, the resulted kernel
won't boot when vcpus set to 1, when it set to 2, it boot OK.
I use XFS for domu file system.

When I try to boot domu with vcpus=1, it couldn't find root device.
--------------
...
NET: Registered protocol family 17
Using IPI No-Shortcut mode
IP-Config: Complete:
      device=eth0, addr=192.168.1.212, mask=255.255.255.0, gw=192.168.1.1,
     host=centos42-01, domain=, nis-domain=(none),
     bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath=
Looking up port of RPC 100003/2 on 1.2.3.4
portmap: server 1.2.3.4 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 1.2.3.4
portmap: server 1.2.3.4 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 1.2.3.4 not responding, timed out
Root-NFS: Server returned error -5 while mounting /tftpboot/centos42-01
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda1" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
...
----------------

-- 
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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 544] New: domU won't boot when vcpus=1 with domu scsi compiled-in kernel, bugzilla-daemon <=