Hello, in the last days I''ve built Xenclient and successfully created a Windows VM according to Takas mail here: http://lists.xensource.com/archives/html/xen-users/2009-06/msg00276.html 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@lists.xensource.com http://lists.xensource.com/xen-devel
Hello, in the last days I''ve built Xenclient and successfully created a Windows VM according to Takas mail here: http://lists.xensource.com/archives/html/xen-users/2009-06/msg00276.html 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@lists.xensource.com http://lists.xensource.com/xen-devel
Hello, in the last days I''ve built Xenclient and successfully created a Windows VM according to Takas mail here: http://lists.xensource.com/archives/html/xen-users/2009-06/msg00276.html 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@lists.xensource.com http://lists.xensource.com/xen-devel
2009/7/30 Kornelius Prell <kornelius.prell@googlemail.com>:> Hello, > > in the last days I''ve built Xenclient and successfully created a Windows VM > according to > Takas mail here: > http://lists.xensource.com/archives/html/xen-users/2009-06/msg00276.html > > 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? >Hi, You need to start xenconsoled -i &, then reboot your guest and you should be able to get to the console using /usr/lib/xen/bin/xenconsole <domid> Jean _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Kornelius Prell wrote:> Hello, > > in the last days I''ve built Xenclient and successfully created a > Windows VM according to > Takas mail here: > http://lists.xensource.com/archives/html/xen-users/2009-06/msg00276.html > ... > 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=xenbr0Hi Kornelius, try setting in your config file: vnc = -1 Your log seems to indicate that the toolstack is waiting for vncterm-wrapper to do something with a timeout of 1200 seconds, but probably never does it. -- Vincent _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jean Guyader wrote:> Hi, > > You need to start xenconsoled -i &, then reboot your guest and you > should be able to get to the console using /usr/lib/xen/bin/xenconsole > <domid> > > Jean >Vincent Hanquez:> Hi Kornelius, > > try setting in your config file: > vnc = -1 > > Your log seems to indicate that the toolstack is waiting for > vncterm-wrapper to do something with a timeout of 1200 seconds, but probably > never does it. > > -- > Vincent >Sorry for the triple post, it seems my messages took a really long route. The vnc = -1 parameter helped to get the VM directly into running state and xenconsole worked quite well. I''ve got a paravirtualized VM running. Thanks for the help. Kornelius _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel