#disk=['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/loop1,sda,w'] (worked for installation, but not for boot)
********************************************************************
Looks ,you have been using "sda" for install, i would use "hda"
disk=['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/loop1,hda,w'] - install
boot="d"
disk=[ 'phy:/dev/loop1,hda,w'] - runtime
boot="c"
or
disk=[ 'phy:/var/xen/domains/hvmtest/disk.img,hda,w'] - runtime
boot="c"
That's a nice howto:-
http://deshantm.livejournal.com/29959.html
**************************************************************************
disk=['phy:/dev/loop0,hdc:cdrom,r','file:/var/xen/domains/hvmtest/disk.img,ioemu:hda,w']
--- On Thu, 2/26/09, Fabian Flägel <fabigant@xxxxxxxxxxxxxx> wrote:
From: Fabian Flägel <fabigant@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] HVM Linux DomU doesn't start
To: bderzhavets@xxxxxxxxx
Cc: "XEN Mailing List" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Thursday, February 26, 2009, 6:58 AM
Hi Boris, your suggestion worked. We were able to boot an installation CD and it saw the disk and installed. But then we stuck on the same problem again with using the disk-image. We tried the following lines:
#disk=['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/loop1,sda,w'] (worked for installation, but not for boot) disk=['phy:/dev/loop0,hdc:cdrom,r','file:/var/xen/domains/hvmtest/disk.img,ioemu:hda,w']
No we are stuck again. Tap:aio doesn't work, file: seems to be broken, at least in our installation, if not in ubuntu 8.04 completely. Any further ideas anyone? regards, Fabian
2009/2/25 Boris Derzhavets <bderzhavets@xxxxxxxxx>
--- On Wed, 2/25/09, Fabian Flägel <fabigant@xxxxxxxxxxxxxx> wrote:
From: Fabian Flägel <fabigant@xxxxxxxxxxxxxx>
Subject: [Xen-users] HVM Linux DomU doesn't start
To: "XEN Mailing List" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Wednesday, February 25, 2009, 11:55 AM
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.
********************************************************* # losetup -f /var/xen/ubuntu-6.06.2-server-i386.iso # losetup -a **********************************************************
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']
###################################### disk=[phy:/dev/loop0,hdc:cdrom,r',phy:/dev/sdaX,hda,w'] ######################################
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
|
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home