Forwarded to ReactOS mailing list.
----- Message d'origine ----
> De : Anthony Liguori <anthony(a)codemonkey.ws>
> À : qemu-devel(a)nongnu.org
> Envoyé le : Jeudi, 29 Janvier 2009, 22h55mn 12s
> Objet : Re: [Qemu-devel] Virtio ballon device always loaded ?
>
> Sylvain Petreolle wrote:
> > Testing ReactOS in qemu made it always asking drivers for a RAM Controller.
> >
> > Looking at "info pci" output and hw/pc.c, I see that the Virtio balloon device
> is always loaded in an x86/64 target.
> > Is that a wanted feature ?
> >
>
> Sure, as I see no harm in not enabling it by default. ReactOS doesn't
> just ignore unknown PCI devices? That's strange because Windows seems to.
>
> Regards,
>
> Anthony Liguori
>
> > I also notice that hw/virtio-balloon.c header refers to the Virtio Block
> Device.
> >
> > Kind regards,
> > Sylvain Petreolle
> >
> >
> >
> >
Hallo,
I would running react-os on xen-hvm.
- on [1] written
must be mount image and change freeldr.ini
- on [2] written
a sample to mount image
- result:
# qemu-img convert ReactOS-0.3.7-QEMU/files/ReactOS.vmdk -f raw ros.raw
$ qemu -hda ros.raw
## running succeful
# losetup -o 32256 /dev/loop0 /mnt/backup/test/ros.raw
# mount /dev/loop0 /mnt/tmp
mount: you must specify the filesystem type
# losetup -d /dev/loop0
# fdisk -l ros.raw
Disk ros.raw: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk ros.raw doesn't contain a valid partition table
-> image has no partition-table
Whats going wrong?
Why to mount existing ROS-image?
regards heiko
[1] http://www.reactos.org/wiki/index.php/Xen_port
[2]http://www.reactos.org/forum/viewtopic.php?f=4&t=1968&p=15984&hilit=mount…
Dear donors, developers, testers and everyone from ReactOS and FOSS
community,
please take my best wishes of a happy new 2009 year!
Let the new year bring us success, stability and compatibility, a
switch to beta, and everything else we could wish for ReactOS to be
useful.
Happy new year!
WBR,
Aleksey Bragin.
