similar to: Ubuntu as DomU

Hello everyone, I have a corrupt .vdi file from a virtualbox installation (XP host, Mint 11 guest) which I recently broke. I wanted to allocate more space to it, so I ran this command:VBoxManage.exe modifyhd /path/to/YOUR_HARD_DISK.vdi --resize 17179869184 It only took a second to actually complete, so I think a header somewhere is broken. I need to get access to some files I had on there using

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Hello! I'm trying to install libguestfs on Ubuntu 10.04 I've installed packages from here: http://libguestfs.org/download/binaries/ubuntu1004-packages/ I get kernel panic on running libguestfs_test_tool, here is outptut: libguestfs: new guestfs handle 0xa596c0 ===== Test starts here ===== LIBGUESTFS_DEBUG=1 library version: 1.13.11 guestfs_get_append: (null) guestfs_get_attach_method:

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: important -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core) Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-amd64 depends on no

Hi all. I''m mostly experienced with Xen 3.0-3.4 so forgive my ignorance. I''m trying to launch FC16 in rescue mode, which works fine with FC14 and Xen 3.4-PAE (but not newer Fedoras because they stopped compiling them with PAE so I gather). When it boots and gets to the point where it loads Anaconda, nothing else happens on the console. I know console variables are at least

Hi, I am using libguestfs 1.12.0 and I am facing a problem with it . I am using guestfs python bindings to "launch" a vdi image file . It works fine except immediately after a VM is stopped(which uses the same vdi file) i.e in normal conditions launch command works but when a vm (which uses the same vdi file) is started - stopped , a call to "launch" command hangs the

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

I thought I'd chime in and say that I'm seeing the same kernel-plus boot failure that Shaun Reitan reported earlier. Is there likely to be another build 3.10 kernel build coming down the pipeline that might fix this issue? Here's the output of my failed PV domU boot: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000]

I have a physical SLES11SP2/OES11 system that I''ve converted to a domU. It''s boots ok as an HVM, but when I try to boot as a PV it gets stuck. I have the kernel-xen packages installed and confident the menu.lst is correct. If I look at xm console for the VM I get the output below: Any ideas? Thanks James [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]

> Just making sure.. you''re running Xen 4.1 ? > The userspace qemu blkback implementation is *only* in Xen 4.1 .. > And it should get used automatically if dom0 kernel blkback is not available. Attempt of DomU install env above :- # xl create -c f14.install Parsing config file f14.install Daemon running with PID 3411                             [    0.000000] Initializing

Broken! [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.0-693.11.6.el7.x86_64 (builder at kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Thu Jan 4 01:06:37 UTC 2018 [ 0.000000] Command line: root=/dev/xvda ro

Hi, I''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success. My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went

I'm trying to set-up a ContOS 7 DomU server. I have used the PXE set-up images like I normally would for earlier versions of CentOS. Here is my config file:- name      = "centos7" memory    = 2048 disk      = ['phy:/dev/xen6/centos7,xvda,w' ] vif = [ 'mac=xx:xx:xx:xx:xx:xx' ] kernel    = "/root/xen/centos7-64/vmlinuz" ramdisk   =

Hi Rich, I set LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 when calling virt-builder, and here is the log: [ 0.1] Downloading: file:///home/myan/work/libguestfs/builder/website/ubuntu-14.04.xz [ 1.4] Planning how to build this image [ 1.4] Uncompressing [ 4.4] Opening the new disk libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_tmpdir

use the virt-df to query vm disk usage like this: virt-df -a /home/centos7_mini.qcow2 then check: virsh list --all Id Name State 1 guestfs-p1km7lhfowv8o0q1running //virt-df will create a vm in temp filesystem but after a few minutes , still fails to get the vm disk usage , why ?? [root@bogon libguestfs-1.38.2]# uname -ar Linux bogon 3.10.0 #2 SMP Thu Nov 28 06:06:42 UTC 2019 x86_64 x86_64

Hello all, I tried unsuccessfully to run libguestfs on debian squeeze (with kernel from testing) using the packages you provide here: http://libguestfs.org/download/binaries/debian-packages/. The output I get from libguestfs-test tool is this: ===== Test starts here ===== LIBGUESTFS_DEBUG=1 TMPDIR=(not set) libguestfs: new guestfs handle 0x17f32c0 library version: 1.14.0 guestfs_get_append:

Hi， Rich， follow your advice， I have succeeded in compiling the “libguestfs-1.26.5” my ”libguestfs-test-tool is passed “ “ libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfs7jxKy0 ===== TEST FINISHED OK =====” But， When I run “virt-df `virsh domuuid 147`” the error show：（debug mode) “supermin helper [00000ms] host_cpu = x86_64 supermin helper [00000ms]