search for: xvda4

Hello, Sacha, le ven. 08 févr. 2019 18:00:22 +0100, a ecrit: > On  Debian GNU/Linux 9.7 (stretch) amd64, we have a bug on the last Xen > Hypervisor version: > > xen-hypervisor-4.8-amd64 4.8.5+shim4.10.2+xsa282 (Read: 4.8.5+shim4.10.2+xsa282-1+deb9u11) > The rollback on the previous package version corrected the problem: > > xen-hypervisor-4.8-amd64

On 2/11/19 2:37 AM, Dongli Zhang wrote: > > On 2/10/19 12:35 AM, Samuel Thibault wrote: >> >> Hans van Kranenburg, le sam. 09 févr. 2019 17:01:55 +0100, a ecrit: >>>> I have forwarded the original mail: all VM I/O get stuck, and thus the >>>> VM becomes unusable. >>> >>> These are in many cases the symptoms of running out of "grant

Hello, Hans van Kranenburg, le sam. 09 févr. 2019 17:01:55 +0100, a ecrit: > > I have forwarded the original mail: all VM I/O get stuck, and thus the > > VM becomes unusable. > > These are in many cases the symptoms of running out of "grant frames". Oh! That could be it indeed. I'm wondering what could be monopolizing them, though, and why +deb9u11 is affected

On 02/12/2019 06:10 AM, Samuel Thibault wrote: > Hans van Kranenburg, le lun. 11 févr. 2019 22:59:11 +0100, a ecrit: >> On 2/11/19 2:37 AM, Dongli Zhang wrote: >>> >>> On 2/10/19 12:35 AM, Samuel Thibault wrote: >>>> >>>> Hans van Kranenburg, le sam. 09 févr. 2019 17:01:55 +0100, a ecrit: >>>>>> I have forwarded the original

...['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/data/builder-var'], ['dev', 'xvda5'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:/dev/data/builder -usr'], ['dev', 'xvda4'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:/dev/data/builder-tmp'], ['dev', 'xvda3'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:/dev/data/builder-root'], ['dev...

...'/dev/xvda2 ro'' disk = [ ''phy:/dev/vg/test-home,xvda7,w'', ''phy:/dev/vg/test-data,xvda6,w'', ''phy:/dev/vg/test-tmp,xvda5,w'', ''phy:/dev/vg/test-usr,xvda4,w'', ''phy:/dev/vg/test-var,xvda3,w'', ''phy:/dev/vg/test-root,xvda2,w'', ''phy:/dev/vg/test-swap,xvda1,w'', ] What have I done wrong ? I have tried many things... DomU is a...

...domU.img" memory = "4096" name = "taquaral" disk = ['phy:/dev/volumes/taquaral-root,xvda1,w', 'phy:/dev/volumes/taquaral-home,xvda2,w', 'phy:/dev/volumes/taquaral-home-staff,xvda3,w', 'phy:/dev/volumes/taquaral-home-adm,xvda4,w', 'phy:/dev/volumes/taquaral-home-admsis,xvda5,w', 'phy:/dev/volumes/taquaral-home-phd,xvda6,w', 'phy:/dev/volumes/taquaral-home-spec,xvda9,w', 'phy:/dev/volumes/taquaral-swap,xvda7,w', 'phy:/dev/volumes/taquaral...

could we increase the size for dom guest online without rebooting or unmounting? pls kindly advise any methods. Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Back in January there was a mail thread on this subject ( http://lists.xensource.com/archives/html/xen-devel/2005-01/msg00659.html ), however I see that blkfront still does not include ioctl support for disk geometry. So, any application that uses "sfdisk -g" to get the geometry of a partition, or disk, will fail when run in DomU. Is this a deliberate omission? Nick Logan

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

Mats, Thanks for your trial; following your mail I tried it with hda; it is the same, it does not work - "fdisk -l" does not show hda. Regards, Ian On 4/2/07, Petersson, Mats <Mats.Petersson@amd.com> wrote: > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Brown