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

[Xen-devel] [XCI] set up a paravirtualized VM

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [XCI] set up a paravirtualized VM
From: Kornelius Prell <kornelius.prell@xxxxxxxxxxxxxx>
Date: Thu, 30 Jul 2009 08:11:28 +0100
Delivery-date: Thu, 30 Jul 2009 07:00:05 -0700
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=KMqAnu9XQR1TG+8fmkPJyVAla2MLpcKf9MnkRAwJY4U=; b=rAXmLNKMgchytuo0WzJ2wVM10zReMAOiFQUC4+86GP1j9MDJcrBFUbGbl/PO2lCp3l eXBvxEOW7vWSBr8kmirg9sKhJrETW8yiJZljXfHq8HXXv8OsQnSIvRGVtItXsXBHnGcO uUoi4VWnLtAOvjdBxVgcU+RIpoorBopYY5HE4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dzDp21MRou22NJF7olNuedPBgvj5ANcfEI9uNvoqnhl9GxkoSAGWZv1r2FbKCHDVkC BeqRq1dLX3i2O3v/YfhvpvGROG6i5mIhYxrMrK28qKk9AfjmERHe3CXAgPJM8wp87TUX jmhF4o3K7KlG725f9ay6Ju+iEAWrfZE2mKGAw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello,
 
in the last days I've built Xenclient and successfully created a Windows VM according to
 
Now I was wondering what it takes to set up a paravirtualized VM in Xenclient.
I tried to boot my Debian Lenny system (with Xen [2.6.26-1-xen-686] kernel / initrd and Xenclient kernel / initramfs) as a pv VM without much success.
It is initalised in paused state and unpausing it won't help (it gets into running state but top shows completly idle CPU).
 
I cannot find any error in the /tmp/xenvm-debug logfile so far:
[20090729 06:27:40.956|info|xenvm] stale socket left by previous xenvm. removing
[20090729 06:27:40.957|info|vmact] sending notification ping
[20090729 06:27:40.957|debug|xenops] Regenerating the xenstored tree under: [/local/domain/5]
[20090729 06:27:40.962|debug|xenops] Created domain with id: 5
[20090729 06:27:40.962|info|vmact] sending notification vm:state:created
[20090729 06:27:40.980|debug|xenops] build_pre domid=5; mem=1048576 KiB; shadow=0 KiB (0 MiB); video=0 KiB
[20090729 06:27:40.980|debug|xenguesthelper] connect: args = [ -mode linux_build -domid 5 -memsize 1024 -image /boot/vmlinuz -ramdisk /boot/initramfs.gz -cmdline root=/dev/sda1 ro -features  -flags 0 -store_port 1 -console_port 2 -fork true ]
[20090729 06:27:41.276|debug|xenops] Read [910778 910777 ]
[20090729 06:27:41.280|debug|xenops] Device.Vbd.add (virtpath=hda | physpath=/dev/sda | phystype=phys)
[20090729 06:27:41.280|debug|xenops] adding device  B0[/local/domain/0/backend/vbd/5/768]  F5[/local/domain/5/device/vbd/768]  H[/xapi/5/hotplug/vbd/768]
[20090729 06:27:41.290|debug|hotplug] Hotplug.wait_for_plug: frontend (domid=5 | kind=vbd | devid=768); backend (domid=0 | kind=vbd | devid=768)
[20090729 06:27:41.290|debug|xenops] watch: watching xenstore paths: [ /xapi/5/hotplug/vbd/768/hotplug ] with timeout 1200.000000 seconds
[20090729 06:27:41.291|debug|xenops] watch: fired on /xapi/5/hotplug/vbd/768/hotplug
[20090729 06:27:41.401|debug|xenops] watch: fired on /xapi/5/hotplug/vbd/768/hotplug
[20090729 06:27:41.401|debug|xenops] watch: value has appeared: /xapi/5/hotplug/vbd/768/hotplug = online
[20090729 06:27:41.401|debug|xenops] watch: Successfully finished watching xenstore after 0.110453 seconds
[20090729 06:27:41.401|debug|hotplug] Synchronised ok with hotplug script: frontend (domid=5 | kind=vbd | devid=768); backend (domid=0 | kind=vbd | devid=768)
[20090729 06:27:41.401|debug|xenops] Device.Vif.add domid=5 devid=-1 mac=22:7f:83:17:25:db rate=none
[20090729 06:27:41.401|debug|xenops] adding device  B0[/local/domain/0/backend/vif/5/-1]  F5[/local/domain/5/device/vif/-1]  H[/xapi/5/hotplug/vif/-1]
[20090729 06:27:41.407|debug|hotplug] Hotplug.wait_for_plug: frontend (domid=5 | kind=vif | devid=-1); backend (domid=0 | kind=vif | devid=-1)
[20090729 06:27:41.408|debug|xenops] watch: watching xenstore paths: [ /xapi/5/hotplug/vif/-1/hotplug ] with timeout 1200.000000 seconds
[20090729 06:27:41.408|debug|xenops] watch: fired on /xapi/5/hotplug/vif/-1/hotplug
[20090729 06:27:41.551|debug|xenops] watch: fired on /xapi/5/hotplug/vif/-1/hotplug
[20090729 06:27:41.552|debug|xenops] watch: value has appeared: /xapi/5/hotplug/vif/-1/hotplug = online
[20090729 06:27:41.552|debug|xenops] watch: Successfully finished watching xenstore after 0.144395 seconds
[20090729 06:27:41.552|debug|hotplug] Synchronised ok with hotplug script: frontend (domid=5 | kind=vif | devid=-1); backend (domid=0 | kind=vif | devid=-1)
[20090729 06:27:41.552|debug|netman] Adding vif5.429496729 to bridge xenbr0
[20090729 06:27:41.556|debug|xenops] Executing [ /opt/xensource/libexec/closeandexec -- /opt/xensource/libexec/vncterm-wrapper 5 -x /local/domain/5/serial/0 ]
[20090729 06:27:41.558|debug|xenops] watch: watching xenstore paths: [ /local/domain/5/serial/0/vnc-port ] with timeout 1200.000000 seconds
[20090729 06:27:41.559|debug|xenops] watch: fired on /local/domain/5/serial/0/vnc-port
 
Here is the VM config file:
uuid = 01000000-0000-0000-0000-102130000014
hvm = false
memory = 1024
debug = true
kernel = /boot/vmlinuz
initrd = /boot/initramfs.gz
disk = /dev/sda:phy:hda:w:disk
cmdline = root=/dev/sda1 ro
boot = c
vif = bridge=xenbr0
 
Is there a possibility to fetch the log of the boot process of a paravirtualised guest VM?
 
Thanks
Kornelius
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>