xen-bugs

[Top] [All Lists]

[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64

from [bugzilla-daemon]

[Permanent Link][Original]

To:	xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64
From:	bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date:	Wed, 23 Nov 2005 14:45:47 +0000
Delivery-date:	Wed, 23 Nov 2005 14:45:56 +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=368





------- Additional Comments From ping.y.yu@xxxxxxxxx  2005-11-23 14:45 -------
(In reply to comment #1)
> Whatever this is, it's not a tools bug -- the tools have created and 
unpaused 
> the domain correctly, according to the logs provided.
> I think that more information is going to be needed before anyone can get a 
> handle on this one.

sorry for confusion. 
The problem is the following:
(1)when set cpus=2 or above in "xm create" script, the domU will fail boot at 
"Event-channel device installed.
xen_net: Initialising virtual ethernet driver.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
"
But when I set cpus=1, it will boot successfully.

(2) "xm list" can show the new created domain well, and maybe this is the 
reason that the xend.log seems to be OK

(3)There is no other information when creating the domU

(4) "xm dmesg" will show: hope it helpful

(XEN) Xen-ELF header 
found: 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=
0xffffffff80000000,LOADER=generic'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000002800000->0000000003000000 (30720 pages to be 
allo
cated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80100000->ffffffff80635086
(XEN)  Init. ramdisk: ffffffff80636000->ffffffff80636000
(XEN)  Phys-Mach map: ffffffff80636000->ffffffff80676000
(XEN)  Start info:    ffffffff80676000->ffffffff80677000
(XEN)  Page tables:   ffffffff80677000->ffffffff8067e000
(XEN)  Boot stack:    ffffffff8067e000->ffffffff8067f000
(XEN)  TOTAL:         ffffffff80000000->ffffffff80800000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
Xen
).
(XEN) microcode: No suitable data for CPU1
(XEN) microcode: No suitable data for CPU0



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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon [Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon <= [Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon

Previous by Date:	[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon
Next by Date:	[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon
Previous by Thread:	[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon
Next by Thread:	[Xen-bugs] [Bug 368] "vcpus" not supported in x86-64, bugzilla-daemon
Indexes:	[Date] [Thread] [Top] [All Lists]