similar to: Error when loading some modules

Hi, Duncan Elliot wrote: > As far as I can see, this essentially trims off the first 3 bytes of the > custom isohybrid MBR image before applying it to the ISO. You probably mean this line: memcpy(mbr, &isohdpfx[hd0 + 3 * partok], MBRSIZE); The indize do not apply to bytes but to byte arrays of size MBRSIZE. extern unsigned char isohdpfx[][MBRSIZE]; (hd0 + 3 * partok)

On 04/22/16 08:19, Leon Fauster wrote: <<>> > check it with: > > blockdev --getalignoff /dev/sd > > (if a '0' is returned, the partition is aligned) > ===> Leon, thank you for reply. ]$ sudo blockdev --getalignoff /dev/sdc1 0 ]$ sudo blockdev --getalignoff /dev/sdc2 0 ]$ sudo blockdev --getalignoff /dev/sdc5 2560 ]$ sudo blockdev --report /dev/sdc1 RO

greetings. centos 6.7 [current] 'disk utility' has started showing message; WARNING: The partition is misaligned by 2560 bytes. This may result in very poor performance. Repartitioning is suggested. for sdc5 - /home partition. /dev/sdc5 302243312 156348604 130534968 55% /home /dev/sdc7 80854912 57088 76683952 1% /hdd/c/07 other than time involved to backup

Hi. Which is the preferable method for booting multiple logical partions via syslinux ? 1. Create seperate logical (fat 32) partitons for 'each' Live CD, extracted and prepared identically via syslinux/syslinux.cfg (sdc5, sdc6,sdc7 etc.) 2. Use Grub2 to attempt to boot seperate logical partitions with the same extracted Live CD plan as above. 3. Use the chain.c32 module that

I''m getting a VFS kernel panic when trying to booting to FC3 from Xen. Its the one that says I must supply a valid "root=" option. (sorry I don''t have it verbatim.) I''m using the xen-2.0 binary installer, kernel 2.6.9. I am using ext3fs, but I am fairly certain that I have compiled support into the kernel. (I''ve tired compile xen from the 2.0

I shot myself in the foot today. I had a centos 5.11 install running fine. Doing a backup, I overwrote the /bin directory by mistake. I couldn't get my machine to recognize a centos 6.5 or 6.6 install dvd, so I put in the original centos 5.10 install disc and re-installed. No problem. During the text installer, I told it to install grub on /dev/sdc1, which is /boot. My raid arrays with lots

We have test latest xen on VT platform with Intel 915 chipset and Here is the test summary: IA32: Build&Boot SMP xen0 without problem Can startup unmodified 2.4/2.6 linux on VMX domain Can startup VMX & Xen with different configuration Part of LTP runs well in VMX domain(2.6) IA32E: Build&Boot SMP xen0 without problem Can startup unmodified 2.6 linux on

This happens randomly, more often than not the next xm create will succeed. Don''t think kernel config is related as I use almost identical setup on my UP machine, but I use the work around for dev designations on all the vm configs. With that setup I get 100% success on creation of domU''s with changeset: 7353:29db5bded574, this changeset would not boot dom0 on the SMP machine.

changeset: 7144:fe401301929e tag: tip user: emellor@ewan date: Fri Sep 30 08:59:28 2005 +0100 summary: Change rebooting specification so that we can have domains crash and stay make dist failed with above changset on FC4. make[3]: Entering directory `/media/sdb2/usr/src/redhat/SOURCES/xen-unstable.hg/linux-2.6.12-xen0'' CHK include/linux/version.h

We have test latest xen (ChangeSet 7608) on VT platform with Intel 915 chipset and Here is the test summary: IA32: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32 issues contain: VMX can not be created IA32E: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32E issues

Hello, I read in the announce of Xen 3.2.0 released that it has "preliminary support for a wider range of bootloaders in fully virtualised (HVM) guests, using full emulation of x86 ''real mode''" . I''d like to know what is the level of the emulation of x86 ''real mode''? I ask that because I tried to install OpenSuse 10.3 (I used the iso file

i just ran install.sh from the xen 3.0.2 pre-built distribution. in /boot it put vmlinuz-2.6.16-xen vmlinuz-2.6-xen -> vmlinuz-2.6.16-xen what happened to the xen0 and xenU kernels? also in /boot from xen 3.0.1 is vmlinuz-2.6-xen0 -> vmlinuz-2.6.12.6-xen0 vmlinuz-2.6-xenU -> vmlinuz-2.6.12.6-xenU which is what i expected from xen 3.0.2. don

Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > "Daniel P. Berrange" <berrange@redhat.com> a écrit : >> If you have new enough libvirt and Xen >= 4.2 then libvirt will >> automatically >> use the libxl APIs instead of XenD. I have compiled a version 1.1.2 (with xapi and xl support) and installed it in /usr/local. I started the

Hi Stefan, The problem is cause by the VBD/VNIF PCI device in DM checked in changeset 11160: PCI Device ID: 5853(Xen),class:ff80 (unknown) ACPI Window does not understand this device and can not find device driver associate with it. To verify this just revert the patches of changset 11161/11160 We are working on the fix now, revert patch is not the solution anyway... Thanks, Winston

Running a heavily modified xen-unstable changset 19590:f80cf52a4fb6 with debugger_attached set, I was seeing the debug traps getting lost from the EXCEPTION_BITMAP in vmx_update_guest_cr() when transitioning from real to protected mode. In my codebase, I could fix this trivially by clearing the debug_state_latch and letting vmx_do_resume() reapply the setting. However, while it looks like a valid

On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote: > Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > > >According to [1] it seems that libvirt is using Xend daemon to communicate. > > After reading more documentation it seems that Xend is mandatory. As > everything is not up to date I'd like to know if it is still the > case or

Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) :

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo

I have been playing with Xen 3.0.1 for some days now, using debian sarge for dom0 and domU''s, and it works like a charm. But, I have a problem with rebooting domU''s. Here is the output from /var/log/xend.log [2006-03-30 13:44:58 xend.XendDomainInfo] INFO (XendDomainInfo:823) Domain has shutdown: name=vmintraweb1 id=5 reason=reboot . [2006-03-30 13:44:58 xend.XendDomainInfo]

Which disk is it? /dev/sda6 or /dev/sdb8 or /dev/sdc6? >From my log: Jun 10 21:25:39 postamt1 kernel: attempt to access beyond end of device Jun 10 21:25:39 postamt1 kernel: 08:06: rw=0, want=1680353324, limit=59954548 Jun 10 21:25:39 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_readdir: directory #3473659 contains a hole at offset 1852399616 $ mount /dev/sdb6 on / type auto (rw)