search for: xvdc

...astrophic data corruption of the filessytem itself. Manual fsck was needed to fixup the filesystem & there were many very bad errors needing fixing. With this patch applied the DomU sees the I/O failures and kernel logs messages Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 722127 Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 730327 Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 738527 Dec 1 11:02:53 dhcp-5-203 kernel: end_request: I/O error, dev xvdc, sector 746727 Dec 1 11:02:53 dhcp-5-203 kernel:...

...st_boot -L 100M /dev/VG01 lvcreate -n guest_swap -L 512M /dev/VG01 lvcreate -n guest_root -L 4G /dev/VG01 Then in the Dom U configuration file I added disk=[''phy:/dev/VG01/guest_boot,xvda,w'',''phy:/dev/VG01/guest_swap,xvdb,w'',''phy:/dev/VG01/guest_root,xvdc,w''] Then I set up the Dom U so (hd0) /dev/xvda --------> mounts @ "/boot" (hd1) /dev/xvdb --------> mounts @ "swap" (hd2) /dev/xvdc --------> mounts @ "/" So with this the Dom U gets started OK. In the guest I see df -H Filesystem...

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

...d where xvdN is the device I create/use here for dom0 initialization. Do I need to do a "xenctl physical grant" for either the virtual block device or the partition on which the virtual disks reside? Moving on: xen_refresh_dev /dev/xvda xen_refresh_dev /dev/xvdb xen_refresh_dev /dev/xvdc I read in the mailing list archive that this refresh is needed... Now I run "fdisk -l" on each of them and get: Disk /dev/xvda: 255 heads, 63 sectors, 16 cylinders Disk /dev/xvdb: 255 heads, 63 sectors, 32 cylinders Disk /dev/xvdc: 255 heads, 63 sectors, 48 cylinders Note the ever i...

...otloader = "pygrub" memory = 512 extra = "debian-installer/exit/always_halt=true -- console=hvc0" # device_model_override = "/usr/lib64/xen/bin/qemu-dm" vif = [''bridge=br0'',] # disk = [''file:/xen/livecd/ubuntu-12.04-server-amd64.iso,xvdc:cdrom,r'', ''phy:/dev/vg/precise_root,xvda,w'', ''phy:/dev/vg/precise_swap,xvdb,w''] disk = [''phy:/dev/vg/precise_root,xvda,w'', ''phy:/dev/vg/precise_swap,xvdb,w''] # root = "/dev/xvdc" vfb = [''ty...

Hi, I could not find this anywhere else reported, so here we go: creating a new btrfs filesystem (btrfs-progs-unstable from git) and mounting it succeeds, unmounting however fails with the kernel messages attached to this mail. After that, I can still read and write to the btrfs mount, but e.g. /bin/sync never finishes, sysrq-s never reports "Sync complete". I''m using a

...on 172 > [ 0.510452] Initialising Xen virtual ethernet driver. > [ 0.526964] blkfront: xvda: barrier: enabled > [ 0.528495] xvda: > [ 0.528633] Setting capacity to 10485760 > [ 0.528637] xvda: detected capacity change from 0 to 5368709120 > [ 0.529412] blkfront: xvdc: barrier: enabled > [ 0.558774] xvdc: unknown partition table > [ 0.559489] Setting capacity to 1048576 > [ 0.559502] xvdc: detected capacity change from 0 to 536870912 > [ 0.973128] PM: Starting manual resume from disk > [ 0.973131] PM: Hibernation image partition 20...

...#39;'/usr/lib/xen/boot/hvmloader'' builder = ''hvm'' memory = ''512'' device_model=''/usr/lib/xen/bin/qemu-dm'' # Laufwerke disk = [ ''file=/200GIG/vm_images/windisk.img,ioemu:xvda,w'',''file:/200GIG/xpg.iso,ioemu:xvdc:cdrom,r'' ] #disk = [ ''phy:/dev/hda,hda,r'' ] # Hostname name = ''WindowsXP'' # Networking #dhcp = dhcp vif = [''type=ioemu, bridge=xenbr0''] # Behaviour boot=''d'' vnc=0 vncviewer=0 sdl=1 DOM0:~# _________________...

...low, but it can be annoying. -- Cheers, Neil Neil French Collier, PhD Faculty of Sustainability Leuphana University L?neburg Rotenbleicher Weg 67 21335 Lueneburg Germany Twitter: @foodsecbio email: collier at leuphana.de Google Scholar <https://scholar.google.com.au/citations?hl=en&user=xVdc-dsAAAAJ&view_op=list_works&sortby=pubdate> Ideas for Sustainability <https://ideas4sustainability.wordpress.com> [[alternative HTML version deleted]]

...lity > > Leuphana University L?neburg > > Rotenbleicher Weg 67 > > 21335 Lueneburg > > Germany > > > > Twitter: @foodsecbio > > email: collier at leuphana.de > > Google Scholar > > < > https://scholar.google.com.au/citations?hl=en&user=xVdc-dsAAAAJ&view_op=list_works&sortby=pubdate > > > > Ideas for Sustainability <https://ideas4sustainability.wordpress.com> > > > > [[alternative HTML version deleted]] > > > > ______________________________________________ > > R-devel at r-...

...bootable 0) (driver paravirtualised) (dev xvdb) (uname phy:/dev/disk/by-id/scsi-SATA_SAMSUNG_blah) (mode w) ) ) (device (vbd (uuid blah) (bootable 0) (driver paravirtualised) (dev xvdc) (uname phy:/dev/disk/by-id/scsi-SATA_SAMSUNG_blah) (mode w) ) ) (device (vbd (uuid blah) (bootable 0) (driver paravirtualised) (dev xvdd) (uname phy:/dev/disk/by-id/scsi-SATA_SAMSUNG_blah)...

...ut any attempts to access it (such as through fdisk to partition it) result in I/O errors being printed to dmesg on both the frontend and backend domains. The process that I used to get the intended node to even appear is to run the xm block-attach command (xm block-attach 4 phy:/dev/xvdb /dev/xvdc w 6), where 4 is the frontend ID, xvdb is the backend device (which I had previously attached to the backend, and can access with no issue), xvdc is the device node that I wish to represent this device in the frontend, and 6 is the backend ID. Before this command times out with the standard &q...

...o the guest to run ZFS RAID operations on them. Before XCP I would add a line like this to the guest config file to expose a local drive. disk = [ ''phy:/dev/vg0/filesrversystem,xvda1,w'', ''phy:/dev/sda,xvda2,w'' ] or xm block-attach myhost phy://dev/sda /dev/xvdc w _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvda2 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvdb 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvdc 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 xvdd 0.00 271.00 0.00 179.00 0.00 1800.00 20.11 1.99 11.11 5.59 100.00 dm-0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00...

[This email is either empty or too large to be displayed at this time]

...guestfs_launch () from /lib64/libguestfs.so.0 #11 0x00000000004117ca in main () Log: 2016-Aug-29 15:02:07 main:1385 Entering main() 2016-Aug-29 15:02:07 main:1393 guestfs_create succeeded 2016-Aug-29 15:02:07 main:1398 guestfs_set_network ok 2016-Aug-29 15:02:07 main:1406 Trying to add drive /dev/xvdc libguestfs: trace: add_drive "/dev/xvdc" "format:raw" libguestfs: trace: add_drive = 0 2016-Aug-29 15:02:07 main:1413 guestfs_add_drive_opts succeeded for drive: /dev/xvdc libguestfs: trace: launch libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" li...

...grq-sz avgqu-sz await r_await w_await svctm %util xvda 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdb 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdc 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdd 0,00 0,00 0,00 26,00 0,00 2336,00 179,69 69,31 1060,62 0,00 1060,62 38,46 100,00 xvde 0,00 0,00 0,00 0,00 0,00...

Is it possible to convert Solaris 10 DomU from hvm to pv?? Dom0 is Opensolaris b132. Possibly any Documentation about this? Here is config of Solaris DomU: <domain type=''xen'' id=''1''> <name>Solaris-10</name> <uuid>c505f6c3-b37b-8268-fe46-f10b3277238b</uuid> <memory>2097152</memory>

Hi all, I have a Sun x2200 named Adra running OpenSolaris 2008.11 set up as a Dom0 per Levon''s instructions on this site. It hosts some production services and has been running nice and stable for a number of months now (with NetWare DomUs running GroupWise, believe it or not). The machine is pretty nicely speced out and there''s room for more virtualisation, so I was

...Reason I ask is that booting into -220 (and I think also into -131 as well) results in a kernel panic for me. Some digging around and the new kernel seems to be enumerating the drives with the wrong minors An m1.large instance-store instance has root at /dev/xvda1, and 2 ephemeral drives xvdb and xvdc. On reboot into 2.6.32-220.7.1 this is what the kernel reports this: dracut: dracut-004-256.el6 device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.22.6-ioctl (2011-10-19) initialised: dm-devel at redhat.com udev: starting version 147 dracut: Starting plymouth daemon %Gxlblk_init: registe...