WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 307] New: Create domain looping endlessly

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 307] New: Create domain looping endlessly
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 10 Oct 2005 18:13:02 +0000
Delivery-date: Mon, 10 Oct 2005 18:13: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=307

           Summary: Create domain looping endlessly
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx,pl@xxxxxxxxxx


The current build is broken. I am unable to start a guest domain on any
of my test boxes. I've tried several hg pulls, and all fail. This is the
last one I've picked up:


changeset:   7288:03d69dbea152
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Mon Oct 10 10:57:41 2005 +0100
summary:     Fire watch callbacks on their own workqueue. Mainly this is


x235:~ # xm create -c /tmp/xen/vm1.cfg
Using config file "/tmp/xen/vm1.cfg".
Started domain vm1
Linux version 2.6.12-xenU (root@x235) (gcc version 3.3.3 (SuSE Linux))
#1 SMP Mon Oct 10 11:18:16 CDT 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000008000000 (usable)
0MB HIGHMEM available.
128MB LOWMEM available.
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  root=/dev/sda9 ro
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Xen reported: 3192.996 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
vmalloc area: c8800000-fb7fe000, maxmem 34000000
Memory: 126336k/131072k available (1806k kernel code, 4488k reserved,
553k data, 140k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: L3 cache: 1024K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 05
Total of 1 processors activated (6356.99 BogoMIPS).
Brought up 1 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Grant table initialized
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda9" 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)


It subsequently seems to go into a loop, creating the same domain over
and over, and a Zombie domain as well (?).

lamb22:~ # xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       245    0      1  r-----     53.9
Zombie-vm1         1         0    1      1  ----cd      0.3
vm1               45       220    1      1  r-----      0.2
lamb22:~ # xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       245    0      1  r-----     55.6
Zombie-vm1         1         0    1      1  ----cd      0.3
vm1               49       220    1      1  r-----      0.1
lamb22:~ # xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       245    0      1  r-----     56.6
Zombie-vm1         1         0    1      1  ----cd      0.3
vm1               51       220    1      1  -b----      0.3

lamb22:~ # xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       245    0      1  r-----     96.7
Zombie-vm1         1         0    1      1  ----cd      0.3
vm1              147       220    1      1  r-----      0.2

-- 
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 307] New: Create domain looping endlessly, bugzilla-daemon <=