[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] ALERT! /dev/xvda2 does not exist. Dropping to a shell! (Ignacio Alegre Alvarez)


  • To: xen-users@xxxxxxxxxxxxx
  • From: "Nacho Alegre Alvarez" <nacho@xxxxxxxxx>
  • Date: Mon, 27 May 2013 22:50:37 +0200
  • Delivery-date: Mon, 27 May 2013 20:53:36 +0000
  • Importance: Normal
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Dear All,

I think finally i find my problem with kernel 3.2.0-4-amd64 and problem
was this kernel not have loaded xen_blkfront.

Step to solve

1º) vi  /etc/initramfs-tools/module and add "xen_blkfront"
2º) Create new initrd adding module
    mkinitramfs $(uname -r) -o /tmp/initrd-$(uname -r)
3º) copy this new initrd to the virtual machina and your /boot
4º) change your virtualdomain.cfg and use this new initrd with driver
xen_blkfront built in to acces to the xvda disc configured into the
virtualdomain.cfg configuration.

I hope this few line can help anyone with the same problem.

Best Regards.

Nacho Alegre

> Send Xen-users mailing list submissions to
>       xen-users@xxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://lists.xen.org/cgi-bin/mailman/listinfo/xen-users
> or, via email, send a message with subject or body 'help' to
>       xen-users-request@xxxxxxxxxxxxx
>
> You can reach the person managing the list at
>       xen-users-owner@xxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xen-users digest..."
>
>
> Today's Topics:
>
>    1. Re: off topic (Ian Campbell)
>    2. Re: Xen does not find bridge device (Ian Campbell)
>    3. Re: [Xen-devel] xen forum (Ian Campbell)
>    4. Re: [Xen-devel]  xen forum (George Dunlap)
>    5. xen setup/config (Chris Vella)
>    6. Re: [Xen-devel]  xen forum (George Dunlap)
>    7. Re: off topic (Paul Stimpson)
>    8. Re: off topic (Ian Campbell)
>    9. ALERT! /dev/xvda2 does not exist. Dropping to a shell!
>       (Ignacio Alegre Alvarez)
>   10. Xen Test Day is today! (Dario Faggioli)
>   11. Re: [Xen-devel] FreeBSD PVHVM call for testing (Roger Pau Monn?)
>   12. Re: FreeBSD PVHVM call for testing (Roger Pau Monn?)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 22 May 2013 10:30:42 +0100
> From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> To: jacek burghardt <jaceksburghardt@xxxxxxxxx>
> Cc: xen-users <xen-users@xxxxxxxxxxxxx>
> Subject: Re: [Xen-users] off topic
> Message-ID: <1369215042.21246.143.camel@xxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="UTF-8"
>
> On Tue, 2013-05-21 at 14:44 -0600, jacek burghardt wrote:
>> I hope this off topic post is ok
>
> No, it's not, please refrain from spamming the list in the future.
>
>>  I just find out this new service that provides free internet and free
>> device[....]I hope you guys can signup for waiting list and use it as
>> backup
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 22 May 2013 10:43:55 +0100
> From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> To: Ole Johan V?ringstad <ole.johan.varingstad@xxxxxxxxx>
> Cc: xen-users@xxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen does not find bridge device
> Message-ID: <1369215835.21246.151.camel@xxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, 2013-05-22 at 05:10 +0200, Ole Johan V?ringstad wrote:
>> Xen 4.2.0-r1, xen-tools 4.2.0-r3 from portage
>> Kernel 3.8.13-gentoo
>>
>> /etc/conf.d/net:
>> config_eth0="null"
>> config_eth1="dhcp"
>> bridge_xenbr0="eth0"
>> config_xenbr0="dhcp"
>> brctl_xenbr0="setfd 0"
>> brctl_xenbr0="sethello 10"
>> brctl_xenbr0="stp on"
>> rc_net_xenbr0_need="net.eth0"
>> rc_net_xenbr0_provide="!net"
>> rc_net_xenbr0_provide="xenbridge"
>> carrier_timeout_xenbr0="0"
>>
>> # brctl show
>> bridge name     bridge id               STP        enabled interfaces
>> xenbr0          8000.902b34599a01       yes             eth0
>>
>> # ping -c 3 -I xenbr0 192.168.0.1
>> PING 192.168.0.1 (192.168.0.1) from 192.168.0.104 xenbr0: 56(84) bytes
>> of data.
>> 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.78 ms
>> 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.92 ms
>> 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.88 ms
>>
>> # xl create /etc/xen/ubuntu.cfg
>
> Can you try "xl -vvv ..." for more debugging. Also have a look
> under /var/log/xen for any relevant logs.
>
> Is /etc/xen/scripts/vif-bridge present? If so then a useful debug
> technique can be to add to the top
>       exec >>/tmp/hotplug.log 2>&1
> which will cause the script output to be logged to /tmp/hotplug.log
> which might give a clue.
>
> Ian.
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 22 May 2013 10:53:20 +0100
> From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> To: Gordan Bobic <gordan@xxxxxxxxxx>
> Cc: xen-users <xen-users@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx,
>       Bartek Krawczyk <bbartlomiej.mail@xxxxxxxxx>
> Subject: Re: [Xen-users] [Xen-devel] xen forum
> Message-ID: <1369216400.21246.158.camel@xxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, 2013-05-22 at 07:55 +0100, Gordan Bobic wrote:
>> Along with a wiki for documentation that is actually kept updated when
>> features are added/removed/changed and more importantly, that clearly
>> states if/when obvious features are unexpectedly and conspicuously
>> missing
>
> The beauty of a wiki is that anyone can edit or correct it.
>
> We have regular documentation days where we are all (users and devs
> alike) encouraged to work to improve the state of the wiki and other
> documentation.
>
> http://wiki.xen.org/wiki/Xen_Document_Days
>
> The state of the Xen documentation base has actually improved
> considerably over the last year due to this initiative.
>
>> (e.g. domU config file method of passing multiple USB devices to
>> domU).
>
> I'm not sure what you are referring to here, the config file syntax is
> documented in docs/man/xl.cfg.pod.5 which is installed as the xl.cfg(5)
> manpage. It is also available online
> http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html and referenced
> from the wiki e.g. http://wiki.xen.org/wiki/Xen_Man_Pages
>
> This manpage contains:
>         =item B<usbdevice=[ "DEVICE", "DEVICE", ...]>
>
>         Adds B<DEVICE>s to the emulated USB bus. The USB bus must also be
>         enabled using B<usb=1>. The most common use for this option is
>         B<usbdevice=['tablet']> which adds pointer device using absolute
>         coordinates. Such devices function better than relative coordinate
>         devices (such as a standard mouse) since many methods of exporting
>         guest graphics (such as VNC) work better in this mode. Note that
> this
>         is independent of the actual pointer device you are using on the
>         host/client side.
>
>         Host devices can also be passed through in this way, by specifying
>         host:USBID, where USBID is of the form xxxx:yyyy.  The USBID can
>         typically be found by using lsusb or usb-devices.
>
>         The form usbdevice=DEVICE is also accepted for backwards
> compatibility.
>
>         More valid options can be found in the "usbdevice" section of the
> qemu
>         documentation.
>
> Ian.
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 22 May 2013 10:58:30 +0100
> From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
> To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> Cc: xen-users <xen-users@xxxxxxxxxxxxx>, Gordan Bobic
>       <gordan@xxxxxxxxxx>,    Bartek Krawczyk <bbartlomiej.mail@xxxxxxxxx>,
>       "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
> Subject: Re: [Xen-users] [Xen-devel]  xen forum
> Message-ID:
>       <CAFLBxZZR3CGrKXmNyDQxwCfWir6KR_CLL0=b4G4zMQF8c9mJDw@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Wed, May 22, 2013 at 10:53 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> wrote:
>> On Wed, 2013-05-22 at 07:55 +0100, Gordan Bobic wrote:
>>> Along with a wiki for documentation that is actually kept updated when
>>> features are added/removed/changed and more importantly, that clearly
>>> states if/when obvious features are unexpectedly and conspicuously
>>> missing
>>
>> The beauty of a wiki is that anyone can edit or correct it.
>>
>> We have regular documentation days where we are all (users and devs
>> alike) encouraged to work to improve the state of the wiki and other
>> documentation.
>>
>> http://wiki.xen.org/wiki/Xen_Document_Days
>>
>> The state of the Xen documentation base has actually improved
>> considerably over the last year due to this initiative.
>>
>>> (e.g. domU config file method of passing multiple USB devices to
>>> domU).
>>
>> I'm not sure what you are referring to here, the config file syntax is
>> documented in docs/man/xl.cfg.pod.5 which is installed as the xl.cfg(5)
>> manpage. It is also available online
>> http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html and referenced
>> from the wiki e.g. http://wiki.xen.org/wiki/Xen_Man_Pages
>>
>> This manpage contains:
>>         =item B<usbdevice=[ "DEVICE", "DEVICE", ...]>
>
> This is a new feature for 4.3 -- 4.2 and earlier don't support
> multiple USB devices (including say, a host device and an emulated usb
> tablet).
>
>  -George
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 22 May 2013 20:04:11 +1000
> From: "Chris Vella" <chris@xxxxxxxxxxxx>
> To: <xen-users@xxxxxxxxxxxxx>
> Subject: [Xen-users] xen setup/config
> Message-ID: <017801ce56d3$b4ff6e10$1efe4a30$@com.au>
> Content-Type: text/plain;     charset="us-ascii"
>
> A little help please guys or a pointer in the right direction for a
> configuration/setup recommendation.
>
> Whilst I have been using the XEN hypervisor in our office/dev environments
> for some time, I am preparing to deploy the latest XCP/Xen build for our
> live/collocation installation.
>
> To date I haven't used any virtualisation at all in our live environment.
> Our setup is relatively straightforward with a physical three tier model:
>
> . Presentation tier (web servers, smtp, etc.)
> . Logic tier (business and operational servers)
> . Data tier (database and storage)
>
> I am going to leave the Data tier non virtualised and virtualise
> (compress)
> the logic and presentation tier onto the same physical hardware.
>
> So the example scenario is:
>
> . Both the Presentation and Logic tiers currently have 6 physical servers
> each (12 total) in a load balanced (shared nothing) arrangement. These
> will
> be replaced with 3-4 physical servers running at least two VM's on each.
> . How would you set up the XEN environment for dynamic workload
> structures?
> . If spikes come through via the presentation tier how do you prioritise
> CPU/bandwidth to these servers/VM's?
> . Likewise if the presentation tier is acquiescent then how do you control
> it such that if the logic tier gets busy it can consume idle
> CPU/bandwidth?
>
>
> Regards,
>
> Chris
>
>
>
>
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 22 May 2013 11:20:49 +0100
> From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
> To: Gordan Bobic <gordan@xxxxxxxxxx>
> Cc: xen-users <xen-users@xxxxxxxxxxxxx>,      "xen-devel@xxxxxxxxxxxxx"
>       <xen-devel@xxxxxxxxxxxxx>,      Bartek Krawczyk
>       <bbartlomiej.mail@xxxxxxxxx>
> Subject: Re: [Xen-users] [Xen-devel]  xen forum
> Message-ID:
>       <CAFLBxZZW0G=NkD0iPMAiHy9Z_rvbQvALKOUm4XLYW63UeDbHpQ@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Wed, May 22, 2013 at 7:55 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote:
>> On 05/22/2013 07:18 AM, Bartek Krawczyk wrote:
>>>
>>> On 21 May 2013 17:04, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>>>>
>>>> On Tue, 2013-05-21 at 15:57 +0100, Gordan Bobic wrote:
>>>>>
>>>>>   On Tue, 21 May 2013 10:29:17 -0400, Konrad Rzeszutek Wilk
>>>>>   <konrad.wilk@xxxxxxxxxx> wrote:
>>>>>>
>>>>>> On Sun, May 19, 2013 at 09:09:00AM -0600, jacek burghardt wrote:
>>>>>>>
>>>>>>> I believe both mailing lists are great but there are so may
>>>>>>> postings
>>>>>>> that
>>>>>>> many issues get missed. There are some bugs that hand never been
>>>>>>> resolved
>>>>>>> because developers are unaware of it. I just setup forum for xen
>>>>>>> users at
>>>>>>> sam.hebe.us/forums please be free to join
>>>>>>
>>>>>>
>>>>>> It would be easier for us if the bug reports and such were posted on
>>>>>> xen-devel.
>>>>>> Please consult http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
>>>>>> when
>>>>>> doing it.
>>>>>
>>>>>
>>>>>   Surely a bug-tracking system that emails all reports to xen-devel
>>>>>   automatically would cover the best of both worlds, would it not?
>>>>
>>>>
>>>> Not unless developers can reply to the bug by hitting reply in their
>>>> MUA.
>>>
>>>
>>> Please drop the forum idea. Xen should use a proper bug tracking
>>> system like Bugzilla (which allows replying to bugs by clicking
>>> "Reply" in MUA).
>>> Take a look at:
>>> http://www.bugzilla.org/docs/4.0/en/html/api/email_in.html
>>
>>
>> +1
>>
>> Along with a wiki for documentation that is actually kept updated when
>> features are added/removed/changed and more importantly, that clearly
>> states
>> if/when obvious features are unexpectedly and conspicuously missing
>> (e.g.
>> domU config file method of passing multiple USB devices to domU).
>
> So the thing here is that I don't think any of the active developers
> knew there was that limitation.  As soon as I discovered it, I just
> fixed it (which is why 4.3 will have support for passing multiple USB
> devices in the config file).
>
> If you find other obvious missing features like that, please mention
> them on the list, and/or suggest them in the xen.org uservoice page:
>  http://xenorg.uservoice.com
>
>  -George
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 22 May 2013 12:10:33 +0100
> From: Paul Stimpson <paul@xxxxxxxxxxxxxxxxxxxx>
> Cc: xen-users <xen-users@xxxxxxxxxxxxx>
> Subject: Re: [Xen-users] off topic
> Message-ID: <6346f0c8-8472-47d7-a20d-d11b95580537@xxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8
>
>
>
> Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>>On Tue, 2013-05-21 at 14:44 -0600, jacek burghardt wrote:
>>> I hope this off topic post is ok
>>
>>No, it's not, please refrain from spamming the list in the future.
>>
>>>  I just find out this new service that provides free internet and
>>free
>>> device[....]I hope you guys can signup for waiting list and use it as
>>> backup
>>
>>
>>
>
> +1 for Ian's comments.
>
> It also appears that the link you posted contains a unique identifier.
> This gives me the impression that it's probably some kind of affiliate
> code and that you would receive some financial incentive or gift of
> service from this company for every person who signs up after clicking it.
>
> That is spamming for gain and is seriously not cool.
>
> Bests,
> Paul.
>
>
> --
> Sent from Kaiten Mail on Android. Please excuse my brevity.
>
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 22 May 2013 12:27:18 +0100
> From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> To: Paul Stimpson <paul@xxxxxxxxxxxxxxxxxxxx>
> Cc: xen-users <xen-users@xxxxxxxxxxxxx>,      jacek burghardt
>       <jaceksburghardt@xxxxxxxxx>
> Subject: Re: [Xen-users] off topic
> Message-ID: <1369222038.21246.176.camel@xxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, 2013-05-22 at 12:10 +0100, Paul Stimpson wrote:
>>
>> Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>> >On Tue, 2013-05-21 at 14:44 -0600, jacek burghardt wrote:
>> >> I hope this off topic post is ok
>> >
>> >No, it's not, please refrain from spamming the list in the future.
>> >
>> >>  I just find out this new service that provides free internet and
>> >free
>> >> device[....]I hope you guys can signup for waiting list and use it as
>> >> backup
>> >
>> >
>> >
>>
>> +1 for Ian's comments.
>>
>> It also appears that the link you posted contains a unique identifier.
>> This gives me the impression that it's probably some kind of affiliate
>> code and that you would receive some financial incentive or gift of
>> service from this company for every person who signs up after clicking
>> it.
>>
>> That is spamming for gain and is seriously not cool.
>
> I hadn't noticed this and, yes, it is very uncool.
>
> Jacek, I have brought this to the listmaster's attention. If this
> happens again I will ask them to ban you from these lists.
>
> Ian.
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 22 May 2013 00:54:12 +0200
> From: "Ignacio Alegre Alvarez" <ignacio@xxxxxxxxx>
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] ALERT! /dev/xvda2 does not exist. Dropping to a
>       shell!
> Message-ID:
>       <ab2eef931993ed151bb417b2da2ae895.squirrel@xxxxxxxxxxxxxxxxx>
> Content-Type: text/plain;charset=iso-8859-1
>
> Dear All,
>
> Can't start system because kernel can't load file systems to and get the
> next error:
>
> modprobe: can't load module microcode
> (kernel/arch/x86/kernel/microcode.ko): No such device
> done.
> Begin: Running /scripts/init-premount ... Begin: Requesting microcode
> update using per-core interface ... done.
> done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
> [    1.493127] device-mapper: uevent: version 1.0.3
> [    1.493908] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19)
> initialised: dm-devel@xxxxxxxxxx
>   Volume group "disco-xen-server" not found
>   Skipping volume group disco-xen-server
> Unable to find LVM volume disco-xen-server/xen-server-swap
> done.
> Begin: Waiting for root file system ... done.
> Gave up waiting for root device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>    - Check rootdelay= (did the system wait long enough?)
>    - Check root= (did the system wait for the right device?)
>  - Missing modules (cat /proc/modules; ls /dev)
> ALERT!  /dev/xvda2 does not exist.  Dropping to a shell!
> modprobe: module ehci-hcd not found in modules.dep
> modprobe: module uhci-hcd not found in modules.dep
> modprobe: module ohci-hcd not found in modules.dep
> modprobe: module usbhid not found in modules.dep
>
>
> BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty; job control turned off
> (initramfs)
>
> Anyone can helpme because i'm lost with this matter i don't know if the
> configuration is grong or if the module to create xvda2 is not loaded i
> don't know follow can see some information about my system:
>
> root@xen-servidor:~# uname -r
> 3.2.0-4-amd64
> root@xen-servidor:~#
>
> root@xen-servidor:~# xm info test
> host                   : xen-servidor
> release                : 3.2.0-4-amd64
> version                : #1 SMP Debian 3.2.41-2+deb7u2
> machine                : x86_64
> nr_cpus                : 2
> nr_nodes               : 1
> cores_per_socket       : 2
> threads_per_core       : 1
> cpu_mhz                : 1297
> hw_caps                :
> 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:0008377f:00000000
> virt_caps              : hvm
> total_memory           : 895
> free_memory            : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 1
> xen_extra              : .4
> xen_caps               : 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
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : unavailable
> xen_commandline        : placeholder
> cc_compiler            : gcc version 4.7.2 (Debian 4.7.2-5)
> cc_compile_by          : carnil
> cc_compile_domain      : debian.org
> cc_compile_date        : Sun May  5 14:44:49 UTC 2013
> xend_config_format     : 4
> root@xen-servidor:~#
>
> root@xen-servidor:~# df -hT
> S.ficheros                                        Tipo     Tama?o Usados
> Disp Uso% Montado en
> rootfs                                            rootfs     4,6G   2,4G
> 2,3G  52% /
> udev                                              devtmpfs    10M      0
> 10M   0% /dev
> tmpfs                                             tmpfs       74M   280K
> 74M   1% /run
> /dev/mapper/disco--xen--server-xen--server--root  ext4       4,6G   2,4G
> 2,3G  52% /
> tmpfs                                             tmpfs      5,0M      0
> 5,0M   0% /run/lock
> tmpfs                                             tmpfs      148M      0
> 148M   0% /run/shm
> /dev/mapper/disco--xen--server-xen--server--disco ext4       223G    83G
> 141G  38% /disco
> root@xen-servidor:~#
>
> test.cfg
>
> #
> #  Kernel + memory size
> #
> kernel      = '/boot/vmlinuz-3.2.0-4-amd64'
> ramdisk     = '/boot/initrd.img-3.2.0-4-amd64'
>
> vcpus       = '1'
> memory      = '128'
>
> #
> #  Disk device(s).
> #
> root        = '/dev/xvda2 ro'
> disk        = [
>                   'file:/home/xen/domains/test/disk.img,xvda2,w',
>                   'file:/home/xen/domains/test/swap.img,xvda1,w',
>               ]
>
>
> #
> #  Physical volumes
> #
>
>
> #
> #  Hostname
> #
> name        = 'test'
>
> #
> #  Networking
> #
> vif         = [ 'ip=192.168.0.254 ,mac=00:16:3E:3A:FD:80' ]
>
> #
> #  Behaviour
> #
> on_poweroff = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
>
> Best Regards.
>
> Ignacio Alegre
>
>
>
>
>
>
> ------------------------------
>
> Message: 10
> Date: Wed, 22 May 2013 09:35:59 +0200
> From: Dario Faggioli <dario.faggioli@xxxxxxxxxx>
> To: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
> Cc: "xen-api@xxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxx>,  xen-devel
>       <xen-devel@xxxxxxxxxxxxx>
> Subject: [Xen-users] Xen Test Day is today!
> Message-ID: <1369208159.12423.152.camel@Solace>
> Content-Type: text/plain; charset="utf-8"
>
> Hi everybody,
>
> Allow me to remind you that Xen Test Day is today, so come and join us
> on #xentest on freenode!
>
> We will be testing Xen 4.3 RC2 (released yesterday). For more info, see:
>  - on Xen Test Days:
>     http://wiki.xen.org/wiki/Xen_Test_Days
>
>  - on getting and testing RC2:
>     http://wiki.xen.org/wiki/Xen_4.3_RC2_test_instructions
>
>  - for generic testing information:
>     http://wiki.xen.org/wiki/Testing_Xen
>
> If you're using Fedora 18, there is even an RPM available already
> (thanks Michael Young for the great work!) here:
>  http://koji.fedoraproject.org/koji/taskinfo?taskID=5407161
>
> See you all on freenode, channel #xentest.
>
> Regards
> Lars
>
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: This is a digitally signed message part
> URL:
> <http://lists.xen.org/archives/html/xen-users/attachments/20130522/91f6b672/attachment.pgp>
>
> ------------------------------
>
> Message: 11
> Date: Wed, 22 May 2013 13:41:02 +0200
> From: Roger Pau Monn? <roger.pau@xxxxxxxxxx>
> To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> Cc: "freebsd-xen@xxxxxxxxxxx" <freebsd-xen@xxxxxxxxxxx>,      xen-devel
>       <xen-devel@xxxxxxxxxxxxx>, "freebsd-virtualization@xxxxxxxxxxx"
>       <freebsd-virtualization@xxxxxxxxxxx>,   "xen-users@xxxxxxxxxxxxx"
>       <xen-users@xxxxxxxxxxxxx>
> Subject: Re: [Xen-users] [Xen-devel] FreeBSD PVHVM call for testing
> Message-ID: <519CAECE.9040706@xxxxxxxxxx>
> Content-Type: text/plain; charset="ISO-8859-1"
>
> On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote:
>> On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monn? wrote:
>>> Hello,
>>>
>>> Recently Justin T Gibbs, Will Andrews and myself have been working on
>>> improving the Xen support in FreeBSD. The main goal of this was to
>>> bring
>>> full PVHVM support to FreeBSD, right now FreeBSD is only using PV
>>> interfaces for disk and network interfaces when running as a HVM guest.
>>> The main benefits of this changes are that Xen virtual interrupts
>>> (event
>>> channels) are now delivered to the guest using a vector callback
>>> injection, that is a per-cpu mechanism that allows each vCPU to have
>>> different interrupts assigned, so for example network and disk
>>> interrupts are delivered to different vCPUs in order to improve
>>> performance. With this changes FreeBSD also uses PV timers when running
>>> as an HVM guest, which should provide better time keeping and reduce
>>> the
>>> virtualization overhead, since emulated timers are no longer used. PV
>>> IPIs can also be used inside a HVM guest, but this will be implemented
>>> later.
>>>
>>> Right now the code is in a state where it can be tested by users, so we
>>> would like to encourage FreeBSD and Xen users to test it and provide
>>> feedback.
>>>
>>> The code is available in the following git repository, under the branch
>>> pvhvm_v5:
>>>
>>> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary
>>>
>>> Also, I've created a wiki page that explains how to set up a FreeBSD
>>> PVHVM for testing:
>>>
>>> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
>>
>> I tried on my Linux box to do this:
>>
>>
>> HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces
>> konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel
>> KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM
>> Makefile:123: *** missing separator.  Stop.
>>
>>
>> As I thought it would compile the same way you can compile NetBSD - that
>> is
>> even on non-BSD distros. Is that not the case? Should I only do this
>> under
>> a FreeBSD guest?
>
> I have never tried to run the FreeBSD build system under something
> different than FreeBSD, also keep in mind that installkernel will place
> a bunch of FreeBSD files on your Linux box if you manage to run it. The
> error itself can probably be fixed by installing and using BSD make
> (bmake), but anyway you need a FreeBSD HVM DomU in order to test the
> kernel, so why not do the compilation on it?
>
>
>
>
> ------------------------------
>
> Message: 12
> Date: Wed, 22 May 2013 13:45:11 +0200
> From: Roger Pau Monn? <roger.pau@xxxxxxxxxx>
> To: Colin Percival <cperciva@xxxxxxxxxxx>
> Cc: "freebsd-xen@xxxxxxxxxxx" <freebsd-xen@xxxxxxxxxxx>,      xen-devel
>       <xen-devel@xxxxxxxxxxxxx>, "freebsd-virtualization@xxxxxxxxxxx"
>       <freebsd-virtualization@xxxxxxxxxxx>,   "xen-users@xxxxxxxxxxxxx"
>       <xen-users@xxxxxxxxxxxxx>
> Subject: Re: [Xen-users] FreeBSD PVHVM call for testing
> Message-ID: <519CAFC7.1070908@xxxxxxxxxx>
> Content-Type: text/plain; charset="ISO-8859-1"
>
> On 18/05/13 17:44, Colin Percival wrote:
>> On 05/18/13 02:50, Roger Pau Monn? wrote:
>>> On 17/05/13 05:07, Colin Percival wrote:
>>>> On 05/16/13 17:43, Roger Pau Monn? wrote:
>>>>> Thanks for testing this on EC2, could you post the full dmesg? So I
>>>>> can
>>>>> see the hypervisor version and if the PV timer is loaded or not.
>>>>
>>>> Here's what I get on a cc2.8xlarge with boot_verbose=YES:
>>>
>>> I've pushed a new branch to my repository, pvhvm_v7 that should work,
>>> there was a bug with PCI event channel interrupt set up. I've tested
>>> with 3.4 and seems OK, but of course it doesn't support the vector
>>> callback injection.
>>
>> That seems to work.  dmesg is attached.  Are there any particular tests
>> you'd like me to run?
>
> I have not tested ZFS, that might be a good one. If you are running this
> on Xen 3.4 the behaviour should be the same as without this patches, so
> there shouldn't be many differences.
>
> If you could try that on Xen 4.0 at least (if I remember correctly
> that's when the vector callback was introduced), you should see the PV
> timer getting attached, and a performance increase.
>
>> If anyone else wants to play with this, you can launch ami-e75c358e in
>> the
>> EC2 us-east-1 region.
>>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users
>
>
> End of Xen-users Digest, Vol 99, Issue 47
> *****************************************
>



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.