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

[Xen-users] HVM Linux DomU doesn't start

To: XEN Mailing List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] HVM Linux DomU doesn't start
From: Fabian Flägel <fabigant@xxxxxxxxxxxxxx>
Date: Wed, 25 Feb 2009 17:55:47 +0100
Delivery-date: Wed, 25 Feb 2009 08:56:30 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=URRVWk0ur++0giEmTbN/8nFifrLeYK9CxK5taywF750=; b=RkdMZbuz5qLL3FvblPw/P1co1MLFcQ2vK7Tz5r7+1eSmtPFzkzkpZnZrwTzMZm90G7 jNZu85z0PQbkmPu8/MnUlNN01hJxXGwwsyNb9IAcFTvShNl6XQDyXxsmDsuRy0ppqRG6 QEOXTcPsqI8icJ4uI0PGfBZF+HMA+S+6wSpJk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QEVXfONE8cnIQlou4av0ZT1phWJHSrZXYywYIbBKjixhzXGfez/HL2xzzV/Bp8OeSV rnIn1mXFTsdrBrGdG7kUkucLIAFZpJMEXWB0h9At6xlLP3upV/h6Rwx2UW6Er4bjmg94 olKIENKQGtxZ4gIutWINSrrNW5Mf83G3CtCd4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

we are running two servers with Ubuntu 8.04 LTS Server with Xen 3.2 and two dual-core CPUs:

processor    : {0-3}
vendor_id    : AuthenticAMD
cpu family    : 15
model        : 65
model name    : Dual-Core AMD Opteron(tm) Processor 2218 HE
stepping    : 3
cpu MHz        : 2613.394
cache size    : 1024 KB
physical id    : 0
siblings    : 1
core id        : 0
cpu cores    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 1
wp        : yes
flags        : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
bogomips    : 5227.99
TLB size    : 1024 4K pages
clflush size    : 64
cache_alignment    : 64
address sizes    : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

As we can see, svm is available and hvm should be possible. See also this:
# cat /sys/hypervisor/properties/capabilities
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

We are trying to build a HVM Linux with a handmade 2.6.16.5 Kernel which includes some unknown changes. This Kernel is a requirement and there are no xen PV-patches for a kernel that old. We try to boot a CD-ROM iso first, but even this doesn't work.

This is our Config:

name='hvmtest'
memory      = '1024'
vcpus       = 1
kernel= "/usr/lib/xen/boot/hvmloader"
builder = "hvm"
disk        = [   'file:/var/xen/ubuntu-6.06.2-server-i386.iso,hdc:cdrom,r']
device_model = "/usr/lib/xen/bin/qemu-dm"
boot='dc'
vnc=1
vnclisten='0.0.0.0'
vif  = [ 'type=ioemu,bridge=br-core-road','type=ioemu,bridge=br-mgnt' ]
> on_reboot   = 'restart'
on_crash    = 'preserve'

Hvmloader and qemu-dm exists, but xm create fails with:

Using config file "/var/xen/domains/hvmtest/hvmtest.cfg".
Error: Device 2080 (vbd) could not be connected. losetup -r /dev/loop1 /var/xen/ubuntu-6.06.2-server-i386.iso failed

but:
# losetup -a
/dev/loop0: [0901]:278531 (/var/xen/ubuntu-6.06.2-server-i386.iso)

I am a bit confused now. What are we doing wrong?

Best regards,
Fabian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>