|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-users
RE: [Xen-users] Building from Source
 
Are you using this config file for your domu?
name = "lb1"
builder = "hvm"
memory = "512"
device_model = "/usr/lib/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
#disk = ['phy:/dev/loop0,hda,w']
boot="c"
acpi="0"
serial = "pty"
vncpasswd = "test"
 I found this in one of your previous emails to the list. I used this  
to see if I could replicate your problem. Using the config file for  
domu that you supplied I get the exact same results on a working  
xen3.3 box.
 You are trying to use the loop device for a disk for a hvm machine.  
You are using 'boot="c"' when there is nothing on the "disk". You need  
a line like this:
disk=['phy:/dev/rootvg/nathan,hda,w','file:/home/jonr/nevaeh-i386.iso,hdc:cdrom,r']
 I am using your config file and booting just fine. Your problem is  
your "disk=" line in your config file. I am using LVM's in this  
example but you could also use file based "disks".
 When I use the config file you supplied on the list I get the exact  
same errors in /var/log/xen/qemu-dm-lb1.log.
You do not want to use /dev/loop0 as a disk.
Jon
Quoting Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>:
 
Jon,
I guess I didn't explain clearly...
 I cannot get a DomU to stay in a running state.  It doesn't matter   
if there is a disk attached or not, the DomU dies almost instantly.
Thank You,
Nathan Eisenberg
Sr. Systems Administrator
Atlas Networks, LLC
-----Original Message-----
 From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx   
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of   
jonr@xxxxxxxxxx
Sent: Friday, October 24, 2008 12:13 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Building from Source
Quoting Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>:
 
Jon,
As I mentioned - the disk line seems to have no effect on whether or
 not the DomU boots.  Even with no disk line, I get the same
results.   The loop device was just a temporary contrivance for
testing, but  is definitely not the cause of the issue.
 
 
Nathan,
Using your config file I can get the same results on a known working
dom0. Whether I have the disk line in or not, when I boot the domu
this is what I see:
root@xenproof:/etc/xen# xm create nathan
Using config file "./nathan".
Started domain lb1
root@xenproof:/etc/xen# xm list
Name                                        ID   Mem VCPUs      State
  Time(s)
 Domain-0                                     0  2367     2       
r-----   2073.1
domutest                                    12   512     1       
r-----   3662.0
Is this what you are seeing as well?
What OS is on loop0? Did you already install an OS onto that device? I
went back through the archives and couldn't find the email that said
you had already done that. I may have missed it though.
Jon
_______________________________________________
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
 
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 
 |   
 
 | 
    | 
  
  
    |   | 
    |