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 1612] x86-64 : Can't start VM when vif set

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1612] x86-64 : Can't start VM when vif set
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 26 May 2010 09:39:15 -0700
Delivery-date: Wed, 26 May 2010 09:39:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1612-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
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/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/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=1612





------- Comment #11 from joseph.deming@xxxxxxxxxxxxxx  2010-05-26 09:39 -------
aye, can confirm on xen-4.0.1-rc1.gz downloaded using
http://wiki.xensource.com/xenwiki/Xen4.0 info yesterday.

xm info
=======
host                   : kraid.matrix.msu.edu
release                : 2.6.32-5-xen-amd64
version                : #1 SMP Mon May 3 12:36:28 UTC 2010
machine                : x86_64
nr_cpus                : 12
nr_nodes               : 2
cores_per_socket       : 6
threads_per_core       : 1
cpu_mhz                : 2400
hw_caps                :
178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000
virt_caps              : hvm
total_memory           : 32762
free_memory            : 1859
node_to_cpu            : node0:0,2,4,6,8,10
                         node1:1,3,5,7,9,11
node_to_memory         : node0:65
                         node1:1793
node_to_dma32_mem      : node0:65
                         node1:0
max_node_id            : 1
xen_major              : 4
xen_minor              : 0
xen_extra              : .1-rc1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Sat May 22 07:18:16 2010 +0100 21162:370fd9f97c70
xen_commandline        : 
cc_compiler            : gcc version 4.4.4 (Debian 4.4.4-2) 
cc_compile_by          : Rjmd
cc_compile_domain      : matrix.msu.edu
cc_compile_date        : Wed May 26 12:10:32 EDT 2010
xend_config_format     : 4

xen domU config


# BOOT WITH STANDARD KERNEL
kernel      = '/boot/vmlinuz-2.6.32-5-amd64'
ramdisk     = '/boot/initrd.img-2.6.32-5-amd64'
memory      = '2048'
root        = '/dev/xvda1'

# NEW SYSTEM NAME/DRIVES/NETWORK
name        = 'wario'

disk        = [
                'phy:/dev/xendisks/wario-root,xvda1,w',
                'phy:/dev/xendisks/wario-swap,xvda2,w'
              ]

vif         = [
                'ip=35.9.18.249, mac=00:16:3e:09:12:F9, bridge=eth0',
                'ip=10.0.0.249,  mac=00:16:3E:00:00:F9, bridge=eth1'
              ]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'
(tried -xen and -vserver kernel versions in 3.4 with same results so can assume
the same if i try those under xen 3.4, ask and i can confirm absolute, don't
think domU is the issue though, the kernel oops is in dom0 env)

going to try to attach some files to this instead of pasting long info here.


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